From: Colin Baxter <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Cc: "Дмитрий Логвиненко" <email@example.com>, firstname.lastname@example.org
Subject: Re: [POLL] Will it be ok to allow HABIT property inheritance? (optionally)
Date: Thu, 18 May 2023 17:32:41 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <87cz2xmwsf.fsf@localhost> (Ihor Radchenko's message of "Thu, 18 May 2023 16:25:36 +0000")
>>>>> Ihor Radchenko <firstname.lastname@example.org> writes:
> Colin Baxter <email@example.com> writes:
>> > No objections have been raised.
>> Well, you have not really given much time to respond.
> 2 weeks. I could have waited one month, but this is relatively
> safe breaking change.
>> Does this mean that all sub-heading with their TODOs will now
>> become habits? I would like much more information on the effects
>> of this proposal.
> Sorry if I was not clear in my original message.
> 1. STYLE will _not_ be inherited by default after the proposed
> change. 2. HABIT will be inherited if user customized
> `org-use-property-inheritance' to value of t (aka inherit all
> properties) 3. STYLE will be inherited if user explicitly added
> "STYLE" to `org-use-property-inheritance' when it is a list.
> Only (2) can be breaking.
Ok, that's good.
>> We have had `habits' for zillions of years which have worked
>> well. So why the change?
> To be able to dedicate a separate subtree or file to habits,
> automatically making all the sub-tasks habits without spamming
> property drawers setting :STYLE: habit.
Thank you very much. I understand.
next prev parent reply other threads:[~2023-05-18 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 13:03 [BUG] org-habit does not respect STYLE property inheritance Дмитрий Логвиненко
2023-05-04 9:53 ` [POLL] Will it be ok to allow HABIT property inheritance? (optionally) (was: [BUG] org-habit does not respect STYLE property inheritance) Ihor Radchenko
2023-05-18 10:38 ` Ihor Radchenko
2023-05-18 16:10 ` [POLL] Will it be ok to allow HABIT property inheritance? (optionally) Colin Baxter
2023-05-18 16:25 ` Ihor Radchenko
2023-05-18 16:32 ` Colin Baxter [this message]
2023-06-15 17:11 ` [POLL] Will it be ok to allow HABIT property inheritance? (optionally) (was: [BUG] org-habit does not respect STYLE property inheritance) Dmitry Logvinenko
2023-06-16 9:45 ` Ihor Radchenko
2023-06-22 17:08 ` Dmitry Logvinenko
2023-06-23 10:51 ` Ihor Radchenko
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 \
* 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).