From: Richard G Riley <rileyrgdev@googlemail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: switching between todo groups
Date: Fri, 02 Nov 2007 16:05:25 +0100 [thread overview]
Message-ID: <eczlxwr8lm.fsf@home.net> (raw)
In-Reply-To: <874pg4bqah.fsf@bzg.ath.cx> (Bastien's message of "Fri\, 02 Nov 2007 15\:49\:58 +0000")
Bastien <bzg@altern.org> writes:
> Richard G Riley <rileyrgdev@googlemail.com> writes:
>
>>> Seq1: k1 k2 k3 | k0
>>> Seq2: ka k1 kb kc | k0
>>>
>>> If a headline starts with k1, how Org would know what should be the next
>>> logical keyword? k2 or kb? For now, it uses k2, ignoring Seq2.
>>
>> Occam's razor. Simplest solution. The first one unless the user selects
>> the second group and this is "remembered" in memory for the duration of
>> the session or the user changes it again. Certainly better than showing
>> two groups but only allowing selection of first group.
>
> Mh... how do you "remember" what set you're using for en entry?
I don't know the details of the elisp but I assume that for one open
file there is a "current sequence" variable? It is initialised to the
first.
It is only to be remembered for the life of the session.
>
> Even if we imagine some internal mechanism to keep track of sets
> changes, how do the user knows what is the current set in use for
> a headline, if its TODO keyword belongs to several sets?
He knows because he set it. If he is unsure he can just loop around back
with the status showing which is the current sequence group-
>
> Should this be "remembered" between emacs sessions as well??
>
I am not suggesting anything is remembered between sessions.
next prev parent reply other threads:[~2007-11-02 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 0:51 switching between todo groups Richard G Riley
2007-11-02 14:53 ` Bastien
2007-11-02 14:16 ` Richard G Riley
2007-11-02 15:49 ` Bastien
2007-11-02 15:05 ` Richard G Riley [this message]
2007-11-02 17:38 ` Bastien
2007-11-03 13:10 ` Richard G Riley
2007-11-03 14:23 ` Bastien
2007-11-03 13:43 ` Richard G Riley
2007-11-03 14:59 ` Bastien
2007-11-03 14:06 ` Richard G Riley
2007-11-03 15:40 ` Bastien
2007-11-03 15:15 ` Richard G Riley
2007-11-04 7:22 ` Carsten Dominik
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=eczlxwr8lm.fsf@home.net \
--to=rileyrgdev@googlemail.com \
--cc=bzg@altern.org \
--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).