emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Daniel J. Sinder" <djsinder@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Setting org-log-into-drawer in a property
Date: Tue, 19 May 2009 23:04:58 -0700	[thread overview]
Message-ID: <4A139D8A.9000001@gmail.com> (raw)
In-Reply-To: <7C5F99B5-9EF2-4578-8BB6-A20E59071848@gmail.com>

As Carsten Dominik so eloquently wrote on 5/19/2009 1:38 AM:
> On May 19, 2009, at 7:54 AM, Daniel J. Sinder wrote:
>> Most of my tasks have only one state change (TODO->DONE), so I like 
>> to be able to quickly see my log notes by fully expanding all 
>> headings in a sub-tree.  Thus, I do NOT use the LOGBOOK property.
>> However, for repeating items the list of log entries can get quite 
>> long.  If I fully expand a sub-tree with a repeating task, the log 
>> notes push the rest of the tree off the screen.  I'd rather if *only* 
>> repeating tasks (and perhaps select other tasks) used the LOGBOOK 
>> property to keep the log notes hidden in a drawer.
>> This brings me to my question and possible feature request.  The 
>> LOGGING property allows us to set logging preference on a sub-tree 
>> basis.  Is it possible to set the value of org-log-into-drawer on a 
>> sub-tree basis, either via the LOGGING property or some other 
>> property?  If not, would it be possible to add this capability?
> That does make sense.
> Please use the new LOG_INTO_DRAWER property for this purpose.
> - Carsten

(Being more precise (see *emphasis*) to avoid claiming credit for 
something I had nothing to do with....)


I subscribed to this list in April '06, and I remember suggesting the
*note* logging feature later that year
(http://article.gmane.org/gmane.emacs.orgmode/612).  The next release
(version 4.50) included *note* logging.  Incredibly, three years later, 
the explosive growth of orgmode and its community of users & developers,
you still implemented my feature request (coincidentally related to
logging) within a day!

Three years ago, I eagerly absorbed each new feature.  Now, although I'm
still an avid user of orgmode, the growth in my personal use lags behind
the pace of development, and there are many new features that I have not
even touched.  In fact, I often can't even keep up with the volume of
this list.  Yet, the new features have little or no impact on the
features I do use, even though I keep my version nearly at the bleeding
edge via git.  This is just great software design and management!

Anyway, this is my way of saying a profound "thank you" for a great tool
and superb support.


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

      parent reply	other threads:[~2009-05-20  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  5:54 Setting org-log-into-drawer in a property Daniel J. Sinder
2009-05-19  8:38 ` Carsten Dominik
2009-05-20  5:56   ` Daniel J. Sinder
2009-05-20  7:46     ` Carsten Dominik
2009-05-20  6:04   ` Daniel J. Sinder [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:

  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=4A139D8A.9000001@gmail.com \
    --to=djsinder@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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