From: Matt Price <moptop99@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>, Alain.Cochard@unistra.fr
Subject: Re: "COMMENT" keyword not properly documented in the manual
Date: Tue, 10 Jan 2017 15:10:13 -0500 [thread overview]
Message-ID: <CAN_Dec-FG8i9xT0L6OqpSsbNeRv+2yWSjp+Afv=+wAcSwMZDaQ@mail.gmail.com> (raw)
In-Reply-To: <87d1fxyusv.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
On Sun, Jan 8, 2017 at 6:51 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Alain.Cochard@unistra.fr writes:
>
> > Unaware that "COMMENT" was a specific org string,
>
> It is special only at the beginning of a headline (but past TODO keyword
> and priority cookie, if any).
>
> > I had used it at the beginning of a headline, resulting in biased tag
> > and string searches ('C-c a m' or 'C-c a s'). (I was unlucky: the
> > color of the headline was the same as the COMMENT's, so I did not
> > notice anything strange.) I think I finally understood, and found
> > about the org-agenda-skip-comment-trees variable, but...
>
> [...]
>
> > So it seems to me that something about "COMMENT" should be said at
> > some place(s) in the "Agenda views" section.
>
> Considering COMMENT is primarily export related, one option would be to
> make `org-agenda-skip-comment-trees' to nil as a default. In this case,
> it might not even be necessary to document this variable in the manual.
>
> WDYT?
>
I'll just say that once I learned about COMMENT -- from the list, not from
the manual -- I started using it pretty extensively. Also, the Github
org-->html renderer hides COMMENT trees by default. For these reasons, I
think the current default is sensible. But yeah, it should be
documented.
[-- Attachment #2: Type: text/html, Size: 1923 bytes --]
next prev parent reply other threads:[~2017-01-10 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:31 "COMMENT" keyword not properly documented in the manual Alain.Cochard
2017-01-08 23:51 ` Nicolas Goaziou
2017-01-10 7:36 ` Alain.Cochard
2017-01-10 18:05 ` Samuel Wales
2017-01-13 23:28 ` Nicolas Goaziou
2017-01-10 20:10 ` Matt Price [this message]
2017-06-06 15:19 ` multiple agenda views -- sticky agendas?, buffer renaming? Alain.Cochard
2017-07-03 5:09 ` Bastien
2017-08-22 13:25 ` Alain.Cochard
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='CAN_Dec-FG8i9xT0L6OqpSsbNeRv+2yWSjp+Afv=+wAcSwMZDaQ@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=Alain.Cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).