From: Bastien <bzg@altern.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 13668@debbugs.gnu.org
Subject: bug#13668: 24.2.93; strike-through in org mode
Date: Sun, 10 Feb 2013 17:27:38 +0100 [thread overview]
Message-ID: <87zjzc2kxx.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20759.39415.151607.366601@gargle.gargle.HOWL> (Roland Winkler's message of "Sun, 10 Feb 2013 07:00:39 -0600")
Hi Roland,
"Roland Winkler" <winkler@gnu.org> writes:
> There are spaces both between the 2nd and 3rd line, and between the
> 5th and 6th line. -- Possibly, the regexp matcher could distinguish
> in a smarter way between word constituents and no word constituents.
Sorry I wasn't clear: by default, space is not allowed after the first
"*" and before the second "*".
But yes, `org-emphasis-regexp-components' is perhaps too complex and
we have been thinking of implementing this another way. Stay tuned.
>> (setq org-fontify-emphasized-text nil)
>
> Thanks, I'll use that.
>
>> > The org info node on structural markup
>> > elements does not mention such a possibility.
>>
>> Mhh.. yes, I'll perhaps update the manual, or just add a Worg
>> FAQ for this.
>
> Why put this in a separate FAQ? Aren't the info pages the first
> source of information for such things?
Depends. We try to keep the info manual readable, and it's already
quite long. If you can find a good place in the manual, please send
a patch.
Thanks,
--
Bastien
next prev parent reply other threads:[~2013-02-10 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 23:35 bug#13668: 24.2.93; strike-through in org mode Roland Winkler
2013-02-10 4:25 ` Bastien
[not found] ` <87halkn6bz.fsf@bzg.ath.cx>
2013-02-10 13:00 ` Roland Winkler
2013-02-10 16:27 ` Bastien [this message]
2013-02-10 17:08 ` Roland Winkler
2013-02-10 17:12 ` Bastien
2013-02-10 17:33 ` Roland Winkler
[not found] ` <20759.55782.687925.263736@gargle.gargle.HOWL>
2013-02-11 14:04 ` 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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjzc2kxx.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=13668@debbugs.gnu.org \
--cc=winkler@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.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).