From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Date: Sat, 22 Mar 2014 16:30:31 +0100 [thread overview]
Message-ID: <87eh1umeso.fsf@gmail.com> (raw)
In-Reply-To: <87txaqmhzd.fsf@bzg.ath.cx> (Bastien's message of "Sat, 22 Mar 2014 15:21:42 +0100")
Bastien <bzg@gnu.org> writes:
> What I'm after is a bit different:
Is it?
> - keep single character markup;
>
> - simplify `org-emphasis-regexp-components' (getting it of it is the
> extreme version of simplifying it);
You call it extreme, I label it ambitious.
Also, "getting rid of it" really means "no need to change it anymore".
I'd rather have a static complex regexp than a simple customizable one
for the sake of syntax consistency. Of course, a fixed simple regexp is
better (and no regexp at all is even better).
> - allow a more liberal multiline markup fontification where the user
> does not have to tweak `org-emphasis-regexp-components'.
Which is basically "getting rid of it". See above.
> Midword markup is not a priority to me, but I understand how it could
> be useful, this would certainly be a plus.
I agree. This is not a priority, I wasn't clear on this point.
> Also, there is no "backward-compatibility squad", only users who care
> about what they like.
That is what they want us to believe! :)
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-03-22 15:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 13:11 [RFC] Creole-style / Support for **emphasis**__within__**a word** Jambunathan K
2014-03-04 14:55 ` Jambunathan K
2014-03-22 14:05 ` Nicolas Goaziou
2014-03-22 14:21 ` Bastien
2014-03-22 14:54 ` Andreas Leha
2014-03-22 15:22 ` Bastien
2014-03-22 15:30 ` Nicolas Goaziou [this message]
2014-03-22 15:37 ` Bastien
2014-03-23 0:53 ` Samuel Wales
2014-03-23 0:06 ` Marcin Borkowski
2014-03-23 11:32 ` Suvayu Ali
2014-03-23 11:39 ` Marcin Borkowski
2014-03-23 2:59 ` Jambunathan K
2022-01-24 10:50 ` [O] " Vincent Belaïche
2022-01-24 11:54 ` Nicolas Goaziou
2022-01-24 12:09 ` [O] " Juan Manuel Macías
2022-01-24 12:32 ` Vincent Belaïche
2022-01-25 10:55 ` Nicolas Goaziou
2022-01-25 17:18 ` Vincent Belaïche
2022-01-25 17:30 ` Juan Manuel Macías
2022-01-25 18:45 ` Vincent Belaïche
2022-01-25 17:52 ` Nicolas Goaziou
2022-01-25 18:20 ` Vincent Belaïche
2022-01-25 16:27 ` Max Nikulin
-- strict thread matches above, loose matches on Subject: below --
2014-03-04 13:00 Jambunathan K
2014-03-04 12:56 Jambunathan K
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=87eh1umeso.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).