emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Baptiste Fouques <baptiste.fouques@m4tp.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Latex export format control - emphasis and radio link
Date: Thu, 24 Dec 2009 17:25:14 +0100	[thread overview]
Message-ID: <32832d030912240825v5dbcf5baxef990eb47bdc265d@mail.gmail.com> (raw)
In-Reply-To: <AF8ADF65-C5DD-4D2E-8B9E-5BBE3748A439@gmail.com>

Hi,

thank you for having answered quickly my questions

On Thu, Dec 24, 2009 at 9:31 AM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
> first of all, why don't you just use not-a-lint instead of not_a_link?
> Using underscore sort-of asks for problems in this context.

Guess that I am not really looking for problems (I am not this type of
guy ;) ), but where I work, symbol names are defined with underscores
as word separators, and I need a tool that handle it ... And I prefer
facing the the problems when they come (well,  first trying to find
the correct way,  before asking for help).


> Also, why do you want the links to be in typewriter font?
still, it is about symbol names ... so the typewriter font, Then they
are defined once, then any reference should link to the definition ...

>  This is unusual.
>  Maybe instead of modifying org-emph-alist, you'd want to add to it and
> create a new emphasis with is texttt but not verbatim?
It do work, thanks for the advice. Also now I have to handle to prefix
for word that are radio-linked and those who are not ...

>> <<<other_radio_link>>>
>
> it is indeed a bug that this is not exported with escaped underscores.
> I have fixed this issue.

Thank you. Got it and confirm that it works.

Have a good Christmas

--- Bat

      reply	other threads:[~2009-12-24 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 14:27 Latex export format control - emphasis and radio link Baptiste Fouques
2009-12-24  8:31 ` Carsten Dominik
2009-12-24 16:25   ` Baptiste Fouques [this message]

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=32832d030912240825v5dbcf5baxef990eb47bdc265d@mail.gmail.com \
    --to=baptiste.fouques@m4tp.org \
    --cc=carsten.dominik@gmail.com \
    --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).