From: Jesse Johnson <bbuknight@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: inherit priority
Date: Thu, 26 Apr 2018 18:34:18 -0700 [thread overview]
Message-ID: <7e082452-7450-c2fa-ac53-40d75b348b3c@gmail.com> (raw)
In-Reply-To: <87bme5pmnf.fsf@bzg.fr>
On 04/26/2018 04:34 PM, Bastien wrote:
>> There have been several requests for priority inheritance over the
>> years. If it can't currently be done, I am willing to take a look at
>> implementing it.
> Did you make progress on this?
Crazy timing! I've been testing my implementation for a few months, made
some big adjustments a couple weeks ago and plan to submit a patch this
weekend.
> FWIW I'm not convinced it is worth implementing priority inheritance,
> and like Nicolas, I don't remember any request for this (but my memory
> can be wrong here).
Well, I asked for it, so there's at least one person asked for it! Very
tedious busy-body work setting priority on dozens of subtasks when they
all share the same priority as their parent task. Will save me hours of
effort over the course of a year. I'm surprised it wasn't already
implemented.
FWIW, I found a few requests for this feature while searching for a
solution. However I implemented it because it's useful to me, not
because anyone asked me to.
Jesse
next prev parent reply other threads:[~2018-04-27 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 18:14 inherit priority Jesse Johnson
2018-01-03 21:41 ` Nicolas Goaziou
2018-01-04 4:04 ` Jesse Johnson
2018-01-04 8:15 ` Nicolas Goaziou
2018-01-05 4:00 ` Jesse Johnson
2018-01-05 7:24 ` Nicolas Goaziou
2018-01-07 22:47 ` Jesse Johnson
2018-01-08 13:16 ` Nicolas Goaziou
2018-04-26 23:34 ` Bastien
2018-04-27 1:34 ` Jesse Johnson [this message]
2018-04-27 1:59 ` Bastien
2018-07-08 1:55 ` Jesse Johnson
2018-07-09 8:22 ` Nicolas Goaziou
2018-07-10 5:03 ` Jesse Johnson
2018-07-18 12:54 ` Nicolas Goaziou
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=7e082452-7450-c2fa-ac53-40d75b348b3c@gmail.com \
--to=bbuknight@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).