From: Bernt Hansen <firstname.lastname@example.org> To: "François Pinard" <email@example.com> Cc: firstname.lastname@example.org Subject: Re: LOGBOOK opening Date: Sun, 15 Jan 2012 09:03:43 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (=?utf-8?Q?=22Fran=C3=A7ois?= Pinard"'s message of "Sun, 15 Jan 2012 06:49:24 -0500") email@example.com (François Pinard) writes: > Hello, Sebastien. The manual says, in (org) Drawers: > > Sometimes you want to keep information associated with an entry, but > you normally don't want to see it. For this, Org mode has _drawers_. > [...] In order to look inside the drawer, you need to move the cursor > to the drawer line and press <TAB> there. > > and I like what the manual says, I would like it to be true. The > /purpose/ of drawers is to keep the information out of sight, unless > explicit action is taken, as stated. I do not see why RET and SPC from > the Agenda would act differently from one another in that respect, nor > why one of them would contradict the definition and spirit of a drawer. > If for some reason it should be an exception, this should be documented > and justified within (org) Agenda commands, which it is currently not. > > François Hi, It behaves this way in the org file when you change folding views with TAB. From the agenda it's useful (at least for me) to be able to see the first few lines of the drawer data for LOGBOOK entries. When I mark a task WAITING I normally record the reason for WHY it is waiting in the LOGBOOK as a note. SPC in the agenda on the task displays the extra detail and I like this current feature. Regards, Bernt
next prev parent reply other threads:[~2012-01-15 14:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-11 16:04 François Pinard 2012-01-11 17:59 ` Sebastien Vauban 2012-01-15 11:49 ` François Pinard 2012-01-15 14:03 ` Bernt Hansen [this message] 2012-01-16 1:59 ` François Pinard 2012-01-24 16:04 ` Bastien 2012-01-24 18:23 ` François Pinard 2012-01-24 23:24 ` Bernt Hansen 2012-01-25 6:13 ` Bastien 2012-01-25 11:49 ` Bernt Hansen
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: LOGBOOK opening' \ /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 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).