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 05:25:20 +0100 [thread overview]
Message-ID: <87halkn6bz.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87fw153vsd.fsf@gnu.org> (Roland Winkler's message of "Sat, 09 Feb 2013 17:35:46 -0600")
Hi Roland,
"Roland Winkler" <winkler@gnu.org> writes:
> visit the following org file with emacs -Q
>
> cat > foo.org <<EOF
> * foo
> bar (+.2 to .5)
> baz (+.2 to .5)
>
> bar (+.2 to .5)
> baz +.2 to .5)
> EOF
>
> Why are part of the second and third line striked through?
Because "+" tries to add fontification.
> According to the org info pages there is some regexp-based feature
> of that kind.
Yes, see `org-emphasis-regexp-components'.
> But it appears to me that this feature could use a
> more sophisticated regexp matcher. Note that the 5th and 6th line
> are not striked through.
Because the space isn't allowed within +...+ fontified constructs.
> Also, as an occassional org mode user without a need for very fancy
> things, I am wondering whether I can simply switch off such
> structural markup elements.
(setq org-fontify-emphasized-text nil)
> 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.
> I would prefer if, as a
> general strategy, the default values for such features were less
> aggressive.
We try to not make them agressive. But the text you quoted above
looks like an example that could be in fixed-with block like this :
: bar (+.2 to .5)
: baz (+.2 to .5)
: bar (+.2 to .5)
: baz +.2 to .5)
or in another block where *...* constructs are not fontified.
Thanks,
--
Bastien
next parent reply other threads:[~2013-02-10 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fw153vsd.fsf@gnu.org>
2013-02-10 4:25 ` Bastien [this message]
2013-02-10 13:00 ` bug#13668: 24.2.93; strike-through in org mode Roland Winkler
[not found] ` <20759.39415.151607.366601@gargle.gargle.HOWL>
2013-02-10 16:27 ` Bastien
[not found] ` <87zjzc2kxx.fsf@bzg.ath.cx>
2013-02-10 17:08 ` Roland Winkler
[not found] ` <20759.54259.751629.173184__25253.7636356012$1360516174$gmane$org@gargle.gargle.HOWL>
2013-02-10 17:12 ` Bastien
[not found] ` <87d2w82ivf.fsf@bzg.ath.cx>
2013-02-10 17:33 ` Roland Winkler
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87halkn6bz.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/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).