emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Problem with org-entities-user
Date: Sun, 23 Sep 2012 08:18:31 -1000	[thread overview]
Message-ID: <m1k3vkob60.fsf@tsdye.com> (raw)
In-Reply-To: <0FD2FC08-F999-4CE7-A5D4-E86CD2CF9436@gmail.com> (Carsten Dominik's message of "Sun, 23 Sep 2012 12:01:53 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On 23.9.2012, at 10:30, Nicolas Goaziou wrote:
>> Hello,
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>> On 22.9.2012, at 10:52, Nicolas Goaziou wrote:
>>>> If the LaTeX command doesn't require an argument, you can always add it
>>>> to `org-entities-user'.
>>> Yes, even though this is not very clean by itself.
>> This is debatable. Entities are perfectly integrated into Org and are,
>> by essence, multiple-back-end friendly.
> I only mean in the sense that entities are made to insert symbols and
> characters, not to execute commands. It certainly can be used to that,
> but this is not the intention of this mechanism.

Yes, this is the essence of the mismatch.  The mechanism is designed to
work with entities, but the regular expression catches all LaTeX
commands, whose names don't distinguish entities from other constructs

>>>> Anyway this is a minor point. I guess it will be swept under the rug of
>>>> historical reasons, after all.
>>> Maybe not. I can go along with your arguments for cleanness. Would you
>>> object to keeping this feature in as an option, turned off be default,
>>> so that it is at least easy to keep lengthy files working?
>> I'd rather leave it as it is, then. This option would require to
>> maintain two versions of the parser: one without LaTeX commands and
>> another one with them. That would defeat the whole point of removing
>> them.
>>> The way I understand it, the new exporter will be default in 8.0, so
>>> this is the time to make some incompatible changes.
>> Indeed. I will preserve my quota of backward-incompatible changes for
>> other things.
> OK.
Two versions of the parser!  Yikes, that doesn't sound good.

Links still provide a path to handle arbitrary LaTeX commands and have
them send sensible output to the different backends.  They don't look so
great in the Org buffer, but that is an aesthetic issue, not functional.

Thanks, Nicolas, for the new LaTeX exporter.

All the best,

Thomas S. Dye

      reply	other threads:[~2012-09-23 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17  2:32 Problem with org-entities-user Thomas S. Dye
2012-09-17  6:41 ` Nicolas Goaziou
2012-09-17 16:37   ` Thomas S. Dye
2012-09-19 13:15     ` Nicolas Goaziou
2012-09-19 14:55       ` Carsten Dominik
2012-09-19 15:55         ` Nicolas Goaziou
2012-09-19 17:00           ` Bastien
2012-09-19 19:23             ` Thomas S. Dye
2012-09-20  7:33           ` Carsten Dominik
2012-09-20 11:57             ` Nicolas Goaziou
2012-09-20 13:36               ` Carsten Dominik
2012-09-22  8:52                 ` Nicolas Goaziou
2012-09-22 14:57                   ` Carsten Dominik
2012-09-22 16:52                     ` Thomas S. Dye
2012-09-23  8:30                     ` Nicolas Goaziou
2012-09-23 10:01                       ` Carsten Dominik
2012-09-23 18:18                         ` Thomas S. Dye [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:

  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=m1k3vkob60.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* 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


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