emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas S. Dye <tsd@tsdye.com>
To: Eduardo Mercovich <eduardo@mercovich.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-tufte-latex
Date: Fri, 12 Feb 2016 09:02:35 -1000	[thread overview]
Message-ID: <m28u2pzr90.fsf@tsdye.com> (raw)
In-Reply-To: <877fi9u6jo.fsf@mercovich.net>

Aloha Eduardo,

Eduardo Mercovich writes:

> However, I would appreciate some help with little details that I'm not
> getting clear, mostly sure because of my ignorance.
>
> + 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.

>
> + 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]]}.

> + 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. 

Expanding link functionality is something that has been discussed on the
mailing list every once in a while for the last several years, but this
is an idea that fails to find traction with the Org mode developers.  I
reckon they know best.

In practice, I mouse over the link to see the link type in the minibuffer.

hth,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2016-02-12 19:03 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   ` Thomas S. Dye [this message]
2016-02-18 18:43     ` ox-tufte-latex Eduardo Mercovich
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m28u2pzr90.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=eduardo@mercovich.net \
    --cc=emacs-orgmode@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).