emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug in org-log-into-drawer
Date: Mon, 29 Oct 2012 17:07:23 +0100	[thread overview]
Message-ID: <80objljm84.fsf@somewhere.org> (raw)
In-Reply-To: 87wqy96zyi.wl%egh@e6h.org

Hello Erik and Bastien,

Erik Hetzner wrote:
> Bastien wrote:
>> Erik Hetzner <egh-r1v5srsr4wc@public.gmane.org> writes:
>> 
>>> The function org-log-into-drawer called the function org-entry-get with
>>> the inherit argument before I got there. (Maybe it needs to be added to
>>> that list?)
>> 
>> I don't have time to look deeper in this issue. Can one of you have a
>> closer look at the manual and see if there is any inconsistency?
>
> Hi Bastien,
>
> org mode manual says:
>
>   You can also overrule the setting of this variable for a subtree by
>   setting a `LOG_INTO_DRAWER' property.
>
> This sounds to me that LOG_INTO_DRAWER inheritance is intended. Even if it
> is not, I would argue that LOG_INTO_DRAWER *should* apply to subtrees,
> because otherwise one would have to set that property on every TODO item.

I share your point...

But do we all agree that your original example had to fail when
LOG_INTO_DRAWER is not inherited?[1]

Or do I miss some point?

Seb

[1] If yes, is your patch still OK?

-- 
Sebastien Vauban

  reply	other threads:[~2012-10-29 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27  6:09 Bug in org-log-into-drawer Erik Hetzner
2012-10-27  7:38 ` Bastien
2012-10-27  9:00 ` Sebastien Vauban
2012-10-28  2:52   ` Erik Hetzner
2012-10-29  5:41     ` Bastien
2012-10-29 15:49       ` Erik Hetzner
2012-10-29 16:07         ` Sebastien Vauban [this message]
2012-10-30  3:30           ` Erik Hetzner

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=80objljm84.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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
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).