emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] 2 questions
Date: Sun, 24 Feb 2013 10:09:39 +0100	[thread overview]
Message-ID: <87vc9iyt64.fsf@gmail.com> (raw)
In-Reply-To: <87ppzqvpq5.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 23 Feb 2013 19:40:02 +0100")

Achim Gratz <Stromeko@nexgo.de> writes:

> Nicolas Goaziou writes:
>> True, that's why there's also inline \[...\]. But you have to accept
>> paragraph limitations (no empty line, do not start a line with list
>> markers...).
>
> Now, given that difference and the fact that these things can span
> over multiple lines and thus include the beginning of line (which
> creates the contention between different tiers of org-element's
> parsing hierarchy),

Note that filling/auto-filling will never put you in this situation,
since Org has a protection mechanism. IOW, if you end up with a list
marker at the beginning of a line, it's your fault.

> let me ask one more time if it would be possible to escape the beginning
> of line (most likely and the obvious choices given Org's history would
> be ":" or ",") in a general fashion

Be careful here. ": " at a beginning of a line defines a fixed-width
area. It is an element and, therefore, would have precedence over your
math snippet. In this case, fontification will warn you.

Adding comma escaping in an object would be complicated because of
filling. It would also add even more problems. So, no, there needn't be
a protection mechanism in inline math snippets.

Also, let me remind you that, LaTeX-wise, "-2" is equivalent to "- 2".
So, you can avoid that list marker problem pretty easily.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-02-24  9:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 18:06 [new exporter] 2 questions henry atting
2013-02-22 19:04 ` Nicolas Goaziou
2013-02-22 19:38   ` henry atting
2013-02-22 19:42     ` Nicolas Goaziou
2013-02-22 20:13       ` henry atting
2013-02-22 20:19         ` Nicolas Goaziou
2013-02-22 20:31           ` henry atting
2013-02-22 20:33             ` Nicolas Goaziou
2013-02-22 20:39               ` henry atting
2013-02-22 21:39       ` Achim Gratz
2013-02-23  8:21         ` Bastien
2013-02-23 10:52           ` Nicolas Goaziou
2013-02-23 12:14             ` Achim Gratz
2013-02-23 12:36               ` Nicolas Goaziou
2013-02-23 13:04                 ` Achim Gratz
2013-02-23 13:35                   ` Nicolas Goaziou
2013-02-23 15:21                     ` Achim Gratz
2013-02-23 15:31                       ` Nicolas Goaziou
2013-02-23 16:35                     ` Achim Gratz
2013-02-23 17:39                       ` Nicolas Goaziou
2013-02-23 18:40                         ` Achim Gratz
2013-02-24  9:09                           ` Nicolas Goaziou [this message]
2013-02-24 10:31                             ` Achim Gratz

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=87vc9iyt64.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --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).