From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jorge Morais Neto <jorge13515@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Bug: second batch of small documentation problems [9.0 (9.0-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20161102/)]
Date: Sun, 13 Nov 2016 18:22:41 +0100 [thread overview]
Message-ID: <87d1hzqopq.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJR3Qne-08gfC53=nRZQ44H5xBExQqS=9f0C5iEmjaQ+gfoung@mail.gmail.com> (Jorge Morais Neto's message of "Sat, 12 Nov 2016 17:56:56 -0200")
Hello,
Jorge Morais Neto <jorge13515@gmail.com> writes:
> On 11 November 2016 at 22:47, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> `org-tag-persistent-alist' is about "characters". I think it is clear
>> that characters are case-sensitive already.
> Currently, the docstring of org-tag-alist says "SELECT is a case-sensitive
> letter" and the docstring of org-tag-persistent-alist says "SELECT is a
> character". I thought I should point this out, but it is your call whether this
> inconsistency needs to be fixed.
Fixed.
>> AFAICT any character is allow, but how could we formulate this?.
> Any Emacs character is allowed? If so, perhaps we could just say "SELECT is an
> Emacs character (this includes all Unicode characters)". But beware that I
> know little Org and very little Elisp, so please take my suggestion with a
> grain of salt.
I was speaking about Org manual. In any case, I worked around this.
Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2016-11-13 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 12:55 Bug: second batch of small documentation problems [9.0 (9.0-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20161102/)] Jorge Morais Neto
2016-11-07 0:20 ` Nicolas Goaziou
2016-11-07 10:57 ` Jorge Morais Neto
2016-11-12 0:47 ` Nicolas Goaziou
2016-11-12 19:56 ` Jorge Morais Neto
2016-11-13 17: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=87d1hzqopq.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jorge13515@gmail.com \
/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).