From: David Hedbor <david@hedbor.org>
Subject: Re: "incorrect" read order
Date: 20 Mar 1998 10:44:18 -0800 [thread overview]
Message-ID: <odvht9xkvx.fsf@frisco.inside.sealabs.com> (raw)
In-Reply-To: Kai Grossjohann's message of "20 Mar 1998 12:28:17 +0100"
Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:
> >>>>> On 19 Mar 1998, David Hedbor said:
>
> David> I would like the read order to be 1.1, 1.2, 1.n, 2.1, 2.2 etc
> David> and not 1.1, 2.1 ...
>
> This order is the default if all groups have the same level. I think.
The thing is that all groups don't have the same level. If they did, I
would get them in alphabetical order, which is not what I want. One
example is:
[Work] Level
work.personal 1
work.admin 2
work.misc 2
work.daemon 3
I want to read them in that order, so I use the level to sort them
correctly (visually). Then I have other topics, which I sort the same
way, but which is less important than [Work].
--
[ Below is a random fortune, which is unrelated to the above message. ]
Time is an illusion perpetrated by the manufacturers of space.
next prev parent reply other threads:[~1998-03-20 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-19 20:33 David Hedbor
1998-03-20 11:28 ` Kai Grossjohann
1998-03-20 18:44 ` David Hedbor [this message]
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=odvht9xkvx.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).