From: Colin Baxter <m43cap@yandex.com>
To: emacs-orgmode@gnu.org
Subject: Re: Spurious comma after C-c '
Date: Mon, 06 Jul 2020 12:53:11 +0100 [thread overview]
Message-ID: <87k0zgg8rc.fsf@yandex.com> (raw)
In-Reply-To: 87k0zg7wa9.fsf@nicolasgoaziou.fr
>>>>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello, Colin Baxter <m43cap@yandex.com> writes:
>> 1. Use `emacs -q' and open a new org file. 2. Enter
>>
>> #+begin_example
>>
>> #+end_example
>>
>> 3. Place cursor in the empty line of the example block and hit
>> C-c ' 4. Enter #+STARTUP in the edit buffer and hit C-c ' to exit
>> 5. A spurious comma appears at the beginning of #+STARTUP 6. The
>> comma appears to form only when + is entered after #, so #STARTUP
>> produces no comma. The STARTUP entry is unimportant and #+ alone
>> also gives a comma. 7. I'm using Org mode version 9.3.7
>> (release_9.3.7-669-g3327fb)
> This is an escape character. See (info "(org) Literal Examples").
Well, yes. But should it really be in an "example" source block? If this
is then exported and the author hasn't caught and deleted it, then it is
likely to cause confusion in the mind of the final reader - who may
know nothing about org-mode.
Best wishes,
Colin Baxter
URL: http://www.Colin-Baxter.com
---------------------------------------------------------------------
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8
---------------------------------------------------------------------
The sole cause of all human misery is the inability of people to sit
quietly in their rooms. Blaise Pascal, 1670
---------------------------------------------------------------------
Since mathematicians have invaded the theory of relativity, I do not
understand it myself. A. Einstein
next prev parent reply other threads:[~2020-07-06 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:00 Spurious comma after C-c ' Colin Baxter
2020-07-06 10:49 ` Nicolas Goaziou
2020-07-06 11:53 ` Colin Baxter [this message]
2020-07-06 13:59 ` Nicolas Goaziou
2020-07-06 14:24 ` Colin Baxter
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=87k0zgg8rc.fsf@yandex.com \
--to=m43cap@yandex.com \
--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).