From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Reuben Thomas <rrt@sc3d.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Please make org-emphasis-regexp-components respect all whitespace [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]
Date: Fri, 15 Sep 2017 00:22:56 +0200 [thread overview]
Message-ID: <87ingkex8f.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87lglh9hmi.fsf@sc3d.org> (Reuben Thomas's message of "Thu, 14 Sep 2017 20:59:01 +0100")
Hello,
Reuben Thomas <rrt@sc3d.org> writes:
> I currently have in my Emacs init:
>
> (setq org-emphasis-regexp-components ;; define before loading org
> '("[:space:]('\"{" "-[:space:].,:!?;'\")}\\[" "[:space:]\r\n" "." 1))
>
> In other words, I added [:space:] to the BORDER pattern too.
>
> It would seem reasonable to have something like this be the default. In
> particular, worg/dev/org-syntax.org already talks about “whitespace”,
> not specifically “spaces, tabs etc.”.
>
> But, I wonder, is it a problem that [:space:] contains vertical
> whitespace characters too? (I left “\r\n” in the BORDER pattern as a
> reminder that they are there on purpose, whereas PRE and POST previously
> contained only space and tab, i.e. horizontal whitespace.) On the other
> hand, since PRE and POST are anchored to the start and end of a line,
> and the number of newlines is by default limited to 1, perhaps it’s not
> a problem?
I don't think it is a problem with vertical spaces.
IIRC, that change was request by someone else some months ago, but the
request probably felt through the cracks.
Anyway, I made that change to master branch. We'll see what happens.
Thank you.
--
Nicolas Goaziou
prev parent reply other threads:[~2017-09-14 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:59 Bug: Please make org-emphasis-regexp-components respect all whitespace [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)] Reuben Thomas
2017-09-14 22:22 ` Nicolas Goaziou [this message]
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=87ingkex8f.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rrt@sc3d.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).