From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Problem with org-entities-user
Date: Thu, 20 Sep 2012 15:36:59 +0200 [thread overview]
Message-ID: <8AE329E8-EE0F-45CB-B8FE-96A98EDEBE9E@gmail.com> (raw)
In-Reply-To: <87zk4kdi0e.fsf@gmail.com>
On 20 sep. 2012, at 13:57, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> maybe first have to get clear what you mean by "not accepting raw commands".
>> Would that mean that if I write \vspace in the buffer, the LaTeX exporter
>> would then give me \textbackslash{}vspace, for example, because i thinks that
>> I want that text to appear in the output?
>
> Correct. This is the same when you type <p>something</p> in an Org
> buffer and call the HTML back-end.
Yes, I see what you mean and it is indeed consistent.
The only thing is: I do use Org to draft documents intended to
be later fine-tuned as LaTeX documents, while I don't usually
do this for other backends. So the ability to put in naked
LaTeX formatting commands does have value and convenience for
me personally.
If the consent will be to remove this for cleanness and exporter
speed, maybe we could leave the code that does the protection
in an allow users to opt-in?
- Carsten
next prev parent reply other threads:[~2012-09-20 13:37 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 [this message]
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
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=8AE329E8-EE0F-45CB-B8FE-96A98EDEBE9E@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--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 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).