From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Anton Latukha <anton@latukha.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] org: org-get-priority: reduce `not`, deduplicate magic `(* 1000 ..)` operation
Date: Thu, 10 Oct 2019 14:47:18 +0200 [thread overview]
Message-ID: <875zkwepih.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <2458361570573406@sas8-93eeb7dac565.qloud-c.yandex.net> (Anton Latukha's message of "Wed, 09 Oct 2019 01:23:26 +0300")
Hello,
Anton Latukha <anton@latukha.com> writes:
> Well, after re-reading my letter - it obviously probably comes off as
> being very strong and ambitious. I am pretty cool-headed about
> everything. I am aware of that I need to gradual do ideally clean and
> 100% compatible changes, I looked at the code - and the changes needed
> are at the pretty simple level, it can be done. I just need to be very
> aware and understand all hardcode about default priorities, maybe just
> simply create the custom checks, as in org-get-priority for
> org-get-priority-function and `else` cases are default code.
[...]
>
> I can not use the current default priority system.
> I thought much about what system of priorities I feel great about using.
>
> I had a major idea. I become very driven by this idea.
>
> I want my priorities to be [00] -> [99] - which:
>
> 1) makes me mentally much more eager to set and work with them.
> 2) The main thing is with 00->99 it is impossible to stress about, currently every time it is a decision is it A or B, or maybe C. And then priority C - why do I do something mediocre.
> 3) 00 - 99 priorities have a natural scale, mentally you can feel their priority size, feeling easy setting and reviewing them, since setting them is intuitive and not a decision.
> 4) It is a priority as a percentage of a full priority.
> 5) It is a really scalable range, making all tasks be sorted much more granularly.
> 6) You can select to show diapasons, like show me 99-90 tasks, 89-60, or if you feel tired and playful, and just want to do something not critical, not current-work related - you can look at 60-40.
> 7) And you can move colliding priorities (like 80) to value +-1 -> which makes them automatically be sorted by your current planning more, and they would stay very close in the absolute picture, but
> definitely one after the other.
> 8) It works perfectly for GTD system. The next task comes to you naturally by itself.
>
> That's why I looked how to do it. And started working on this.
These are interesting ideas, and probably worth developing. However,
I don't think it would be a good default. As an user with simple
priority needs, I find A-B-C system very straightforward, and I don't
spend too much time thinking about the priority I should give to some
task. With your system, it would be very troublesome for me: "what is
the difference between a priority of 72 and 73?" or "yesterday, I gave
this task a 70, but maybe it should be 68 because I just tagged this
task at 69.". I.e., I would waste my time tweaking priorities.
OTOH, the idea behind `org-get-priority-function' is to let anyone to
plug-in a different priority system. Maybe the first improvement to the
current system would be to make shifting to any priority-system as easy
as possible, which is, IIUC, what you are suggesting. Once everything is
in place, your ideas could be integrated as an alternate priority system
within Org.
In any case, I cannot help much you with this, as the time I can devote
to Org is virtually non-existent these days. Hopefully, someone else can
guide you, if necessary. Do not worry much about breaking code: do write
tests!
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-10-10 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 0:34 [PATCH] org: org-get-priority: reduce `not`, deduplicate magic `(* 1000 ..)` operation Anton Latukha
2019-10-08 9:25 ` Nicolas Goaziou
2019-10-08 21:28 ` Anton Latukha
2019-10-08 22:23 ` Anton Latukha
2019-10-09 19:33 ` Adam Porter
2019-10-10 2:25 ` Samuel Wales
2019-10-10 12:47 ` Nicolas Goaziou [this message]
2019-10-10 14:24 ` Anton Latukha
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=875zkwepih.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=anton@latukha.com \
--cc=emacs-orgmode@gnu.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).