emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Bastien <bzg@altern.org>
Cc: 13668@debbugs.gnu.org
Subject: bug#13668: 24.2.93; strike-through in org mode
Date: Sun, 10 Feb 2013 07:00:39 -0600	[thread overview]
Message-ID: <20759.39415.151607.366601__12821.143892552$1360502429$gmane$org@gargle.gargle.HOWL> (raw)
In-Reply-To: <87halkn6bz.fsf@bzg.ath.cx>

On Sun Feb 10 2013 Bastien wrote:
> > 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.

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.

> (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?

Roland

  reply	other threads:[~2013-02-10 13:01 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 ` bug#13668: 24.2.93; strike-through in org mode Bastien
2013-02-10 13:00   ` Roland Winkler [this message]
     [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='20759.39415.151607.366601__12821.143892552$1360502429$gmane$org@gargle.gargle.HOWL' \
    --to=winkler@gnu.org \
    --cc=13668@debbugs.gnu.org \
    --cc=bzg@altern.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).