emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Thibault Polge <thibault@thb.lt>
Cc: emacs-orgmode@gnu.org
Subject: Re: Discrepancy between documentation and implementation regarding comments
Date: Mon, 28 Oct 2019 17:16:55 +0100	[thread overview]
Message-ID: <87tv7s3kw8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87blu1xfjb.fsf@thb.lt> (Thibault Polge's message of "Mon, 28 Oct 2019 12:42:16 +0100")

Hello,

Thibault Polge <thibault@thb.lt> writes:

> Thanks Nicolas, just a small detail though: unless this is a planned
> (breaking) change, I believe the description you linked should read:
>
> A “comment line” starts with *zero or more whitespace characters,
> followed by* a hash sign, followed by a whitespace character or an end
> of line.

True. I fixed that.

> Another detail: it could be nice to have a small appendix somewhere
> mapping character names to codepoints, since Unicode has no less than
> three “number signs” (from Wikipedia):
>
>  - U+0023 # NUMBER SIGN (HTML &#35;). Other attested names in Unicode are: pound sign, hash, crosshatch, octothorpe.
>  - U+FF03 # FULLWIDTH NUMBER SIGN (HTML &#65283;)
>  - U+FE5F ﹟ SMALL NUMBER SIGN (HTML &#65119;)

This is left as an exercise to the reader. ;)

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-10-28 16:17 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
2019-10-28 11:05 ` Nicolas Goaziou
2019-10-28 11:42   ` Thibault Polge
2019-10-28 16:16     ` Nicolas Goaziou [this message]
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=87tv7s3kw8.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=thibault@thb.lt \
    /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).