From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: impossible to have footnote touching verbatim
Date: Mon, 23 Jun 2014 23:01:39 +0200 [thread overview]
Message-ID: <87pphz732k.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87pphzgypo.fsf@gmail.com> (Eric Schulte's message of "Mon, 23 Jun 2014 16:25:39 -0400")
Eric Schulte <schulte.eric@gmail.com> writes:
> Should this be done personally or in master?
I can't think of a case where it could lead to confusion, so I'd say it
can go in master, at least until someone complains, if ever.
BTW, as a reminder, I'm all for thinking again how emphasis/verbatim
markup is defined in Org but I doubt changing it by small touches will
do any good. IMO, it needs to be discussed as a whole.
I think a good markup should
- not need to be customizable,
- allow any number of (non-consecutive) newline characters,
- allow escaping markup in verbatim objects.
For example, much like radio links, bold object could be defined as
1. anything but an alphanumeric character (including nothing),
2. / character,
3. an alphanumeric character,
4. anything excepted 2 or more consecutive newline characters
(non-greedy),
5. an alphanumeric character,
6. / character,
7. anything but an alphanumeric character (including nothing).
For simplicity, I ignore the special case /a/ for the moment.
The verbatim would be the same, with a slight change in 4th element:
4. the same, with \= treated as =
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-06-23 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 20:04 impossible to have footnote touching verbatim Eric Schulte
2014-06-23 20:11 ` Nicolas Goaziou
2014-06-23 20:25 ` Eric Schulte
2014-06-23 21:01 ` Nicolas Goaziou [this message]
2014-06-23 21:46 ` Eric Schulte
2014-06-25 8:37 ` Bastien
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=87pphz732k.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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).