From: Eduardo Mercovich <eduardo@mercovich.net>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-tufte-latex
Date: Thu, 18 Feb 2016 15:43:34 -0300 [thread overview]
Message-ID: <87fuwpc10p.fsf@mercovich.net> (raw)
In-Reply-To: <m28u2pzr90.fsf@tsdye.com>
Aloha Thomas.
Sorry the late reply.
[...]
>> + what is the difference between using the :ignore: tag and add
>> "COMMENT" as the first characters in the line (the native Org mechanism
>> to prevent export)? I tried them and didn't saw the difference.
> With the :ignore: tag the headline is ignored, but the text below it is
> exported. This is useful for situations like the front matter of a
> book, which is mostly assembled by LaTeX. The :ignore: tag allows you
> to isolate the various LaTeX commands in your document so they are
> separate from the headings with text that you'll write, but still
> contribute to the export.
Ah, got it. Useful indeed, thanks. :)
>> + if I put a plain text link in a sidenote (like
>> "\sidenote{see http://AgileManifesto.org}"), it doesn't get
>> automagically converted to a link as it is in the text body. It appears
>> as normal text and without the \url{...}, so it doesn't look and doesn't
>> act as a link.
> IIUC, I think you need to tell Org mode that this is a link:
> \sidenote{see [[http://AgileManifesto.org]]}.
I tried it and still I have some issues...
I have Org-mode version 8.3.1 (8.3.1-95-g1dbb25-elpaplus) and GNU Emacs
24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10).
Using the same org document as source, if I use the standard latex
export everything seems fine (except this sidenote link that does not
get hiperlinked as URL), but if I use tufte-latex (with "require
'ox-tufte-latex" in my .emacs file) I have a "PDF file produced with
errors" message. However, I can't spot the difference between both files
with my eyes (they have the same size, but diff says they are
different).
In both cases -orglatex and tuftelatex- the sidenote linke gets rendered
with the double brackets around and not as clickable URL.
How can I give you more info to diagnose this case?
>> + using links as specific Latex markup seems a great idea. However, the
>> links face definition makes it specially visible, and impossible to
>> separate from any other URL since the properties are hidden. Can that be
>> tweaked (maybe not it your class, of course, but in the .emacs file or
>> similar), so as to keep the writing flow unperturbed?
>
> I agree that it would be useful to make the appearance of links in the
> Org mode buffer configurable on a per-link basis. Different colors for
> different kinds of link might go some way to resolving the visual
> ambiguities you describe. However, I don't think this is currently
> possible.
Pity, but completely understandable.
Is it possible to do that in org for latex fragments (like putting
f"\sidenote{" and the closing "}" in a lighter face)?
Sorry if this is obvious but I'm relatively new to the Emacs-verse.
> [...] In practice, I mouse over the link to see the link type in the
> minibuffer.
Great tip!
Again, thank you org-tufte-latex. I can be a heavy user of this system,
so I hope to be of help to make it even better. :)
Best...
--
eduardo mercovich
Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
next prev parent reply other threads:[~2016-02-18 18:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 0:26 ox-tufte-latex Thomas S. Dye
2016-02-02 1:10 ` ox-tufte-latex Titus von der Malsburg
2016-02-02 1:49 ` ox-tufte-latex Thomas S. Dye
2016-02-03 21:57 ` ox-tufte-latex Spencer Boucher
2016-02-02 8:52 ` ox-tufte-latex Eric S Fraga
2016-02-03 0:28 ` ox-tufte-latex Rasmus
2016-02-03 1:35 ` ox-tufte-latex Thomas S. Dye
2016-02-03 2:29 ` ox-tufte-latex Lawrence Bottorff
2016-02-03 11:05 ` ox-tufte-latex Rasmus
2016-02-03 11:26 ` ox-tufte-latex Marcin Borkowski
2016-02-03 11:41 ` ox-tufte-latex Rasmus
2016-02-03 13:33 ` ox-tufte-latex Marcin Borkowski
2016-02-03 16:07 ` ox-tufte-latex Thomas S. Dye
2016-02-03 15:41 ` ox-tufte-latex Thomas S. Dye
2016-02-03 16:42 ` ox-tufte-latex Rasmus
2016-02-03 17:15 ` ox-tufte-latex Thomas S. Dye
2016-02-12 18:28 ` ox-tufte-latex Eduardo Mercovich
2016-02-12 19:02 ` ox-tufte-latex Thomas S. Dye
2016-02-18 18:43 ` Eduardo Mercovich [this message]
2016-02-19 3:03 ` ox-tufte-latex Thomas S. Dye
2016-02-19 3:54 ` ox-tufte-latex Thomas S. Dye
2016-02-22 17:59 ` ox-tufte-latex Eduardo Mercovich
2016-02-22 18:52 ` ox-tufte-latex Thomas S. Dye
2016-02-22 19:35 ` ox-tufte-latex John Hendy
2016-02-23 0:00 ` ox-tufte-latex Thomas S. Dye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuwpc10p.fsf@mercovich.net \
--to=eduardo@mercovich.net \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.