From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alain.Cochard@unistra.fr Subject: "COMMENT" keyword not properly documented in the manual Date: Thu, 5 Jan 2017 17:31:07 +0100 Message-ID: <22638.29899.634767.904773@frac.u-strasbg.fr> Reply-To: alain.cochard@unistra.fr Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46254) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cPAwm-0005mV-6S for emacs-orgmode@gnu.org; Thu, 05 Jan 2017 11:31:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cPAwh-0002YM-2l for emacs-orgmode@gnu.org; Thu, 05 Jan 2017 11:31:24 -0500 Received: from mailhost.u-strasbg.fr ([130.79.222.211]:58729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cPAwg-0002X5-RF for emacs-orgmode@gnu.org; Thu, 05 Jan 2017 11:31:18 -0500 Received: from mailhost.u-strasbg.fr (localhost [127.0.0.1]) by antispam (Postfix) with ESMTP id ECD5D226F46 for ; Thu, 5 Jan 2017 17:31:11 +0100 (CET) Received: from mailhost.u-strasbg.fr (localhost [127.0.0.1]) by antivirus (Postfix) with ESMTP id DD3D5226F89 for ; Thu, 5 Jan 2017 17:31:11 +0100 (CET) Received: from local-mr.u-strasbg.fr (lmr2.u-strasbg.fr [172.30.21.2]) by mr1.u-strasbg.fr (Postfix) with ESMTP id CD405226F46 for ; Thu, 5 Jan 2017 17:31:10 +0100 (CET) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Cc: Alain Cochard 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. =20 Regards --=20 EOST (=C9cole et Observatoire des Sciences de la Terre)=20 IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr 5 rue Ren=E9 Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44=20 F-67084 Strasbourg Cedex, France | Fax: +33 (0)3 68 85 01 25 =20=