From: Colin Baxter <m43cap@yandex.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Дмитрий Логвиненко" <dmlogv@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [POLL] Will it be ok to allow HABIT property inheritance? (optionally)
Date: Thu, 18 May 2023 17:10:02 +0100 [thread overview]
Message-ID: <87ilcptycl.fsf@yandex.com> (raw)
In-Reply-To: <87cz2xzzyq.fsf@localhost> (Ihor Radchenko's message of "Thu, 18 May 2023 10:38:37 +0000")
>>>>> Ihor Radchenko <yantar92@posteo.net> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>> I am generally in favour of allowing STYLE to be inherited, but
>> it is technically a breaking change, as I described.
>>
>> Let's see if anyone voices against this change.
> No objections have been raised.
Well, you have not really given much time to respond.
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.
We have had `habits' for zillions of years which have worked well. So
why the change?
next prev parent reply other threads:[~2023-05-18 16:11 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 ` Colin Baxter [this message]
2023-05-18 16:25 ` [POLL] Will it be ok to allow HABIT property inheritance? (optionally) Ihor Radchenko
2023-05-18 16:32 ` Colin Baxter
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
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=87ilcptycl.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=dmlogv@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).