From: David Hedbor <david@hedbor.org>
Cc: david@hedbor.org
Subject: "incorrect" read order
Date: 19 Mar 1998 12:33:59 -0800 [thread overview]
Message-ID: <odvhtacte0.fsf@frisco.inside.sealabs.com> (raw)
There is one thing that has bothered me for months when using topics
(which is totally great :-) - the group read order. Now "n" and "p"
(when no unread in a group) moves you to the next/prev group,
priority-wise. This means that I don't read the groups in topic-order
(which in my case means weird order). This is how I set up my mail
groups:
level
[Topic 1] most important
Group 1.1 1
Group 1.2 2
Group 1.n 3
[Topic 2]
Group 2.1 1
Group 2.2 2
...
[Topic n] less important
Ie, I have the topics sorted on importance, most important first. Then
I sort the groups in the topics in with level 1 for important, level 2
for less important and level 3 for others.
I would like the read order to be 1.1, 1.2, 1.n, 2.1, 2.2 etc and not
1.1, 2.1 ...
Is this possible to fix? Impossible?
--
[ Below is a random fortune, which is unrelated to the above message. ]
Bus error -- driver executed.
next reply other threads:[~1998-03-19 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-19 20:33 David Hedbor [this message]
1998-03-20 11:28 ` Kai Grossjohann
1998-03-20 18:44 ` David Hedbor
1998-03-20 23:40 ` Justin Sheehy
1998-03-21 0:59 ` David Hedbor
1998-03-21 16:13 ` Kai Grossjohann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=odvhtacte0.fsf@frisco.inside.sealabs.com \
--to=david@hedbor.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.
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 NNTP newsgroup(s).