emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Alain.Cochard@unistra.fr
To: emacs-orgmode@gnu.org
Cc: Alain Cochard <Alain.Cochard@unistra.fr>
Subject: "COMMENT" keyword not properly documented in the manual
Date: Thu, 5 Jan 2017 17:31:07 +0100	[thread overview]
Message-ID: <22638.29899.634767.904773@frac.u-strasbg.fr> (raw)


Hello.  I am a relatively new org user; I am writing this email after
I spent all morning finding the origin of my problem and searching the
web for an explanation and a solution.

Unaware that "COMMENT" was a specific org string, 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...

But I don't see how I could have avoided the problem.  As far as I can
see, the "COMMENT" string only appears in the "Exporting > Comment
lines" subsection of the manual (plus a cryptic part in the "Hacking >
Using the mapping API" appendix).  So if one is not yet concerned with
exporting, one does not feel compelled to go into such details...
Besides, it isn't even specified that COMMENTing interferes with
agenda searches.

So it seems to me that something about "COMMENT" should be said at
some place(s) in the "Agenda views" section.  

Regards

-- 
EOST (École et Observatoire des Sciences de la Terre) 
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 106] | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France    | Fax:   +33 (0)3 68 85 01 25     

next             reply	other threads:[~2017-01-05 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 16:31 Alain.Cochard [this message]
2017-01-08 23:51 ` "COMMENT" keyword not properly documented in the manual 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
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=22638.29899.634767.904773@frac.u-strasbg.fr \
    --to=alain.cochard@unistra.fr \
    --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

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).