From: Samuel Wales <samologist@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Discrepancy between documentation and implementation regarding comments
Date: Sun, 27 Oct 2019 14:02:07 -0700 [thread overview]
Message-ID: <CAJcAo8sLExZGjzN_7GZG_C7LDaBRsV2Xx2BrCeVNBDfQd2QzDA@mail.gmail.com> (raw)
In-Reply-To: <877e4qq7aq.fsf@alphapapa.net>
beware # at eob with no newline.
On 10/27/19, Adam Porter <adam@alphapapa.net> wrote:
> I agree with Robert that "whitespace" includes newlines in "Emacsland."
> For example, with this document (the second "#" has a newline
> immediately after, no spaces or tabs):
>
> #+BEGIN_SRC org
> foo
>
> # comment
>
> bar
>
> #
>
> buzz
> #+END_SRC
>
> This code matches both lines that begin with "#":
>
> (re-search-forward (rx bol "#" (1+ space)))
>
> But this code only matches the first one, because "blank" only matches
> "horizontal whitespace":
>
> (re-search-forward (rx bol "#" (1+ blank)))
>
> So I think Pandoc is technically at fault here. However, outside of
> Emacs's own context, I can see how the the documentation could be
> misinterpreted in this case, so it's hard to fault them too much. :)
>
>
>
--
The Kafka Pandemic
What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.
next prev parent reply other threads:[~2019-10-27 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 10:07 Discrepancy between documentation and implementation regarding comments Thibault Polge
2019-10-27 16:13 ` Robert Pluim
2019-10-27 20:09 ` Adam Porter
2019-10-27 21:02 ` Samuel Wales [this message]
2019-10-28 11:05 ` Nicolas Goaziou
2019-10-28 11:42 ` Thibault Polge
2019-10-28 16:16 ` Nicolas Goaziou
2019-10-29 13:52 ` Robert Pluim
2019-10-29 14:14 ` Thibault Polge
2019-10-29 14:34 ` Robert Pluim
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=CAJcAo8sLExZGjzN_7GZG_C7LDaBRsV2Xx2BrCeVNBDfQd2QzDA@mail.gmail.com \
--to=samologist@gmail.com \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@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).