From: Jens Lautenbacher <jens@metrix.de>
Cc: ding@ifi.uio.no
Subject: Re: Gnus v5.4.62 is released
Date: 08 Jul 1997 04:39:10 +0200 [thread overview]
Message-ID: <m37mf2e08h.fsf@jens.metrix.de> (raw)
In-Reply-To: Hrvoje Niksic's message of "08 Jul 1997 01:52:46 +0200"
Hrvoje Niksic <hniksic@srce.hr> writes:
> Jens Lautenbacher <jens@metrix.de> writes:
>
> > Hmm, I may have missed the beginning of the thread, but I assume you
> > talk about gnus-read-active-file 'some and gnus-check-new-newsgroups
> > 'ask-server; then I see no possibility to keep track of killed
> > groups (and easiely list them) without having the list of killed
> > groups saved.
>
> You are right. What I meant is: if changes are being made, let's try
> to make Gnus behave logically.
>
> Logical behaviour includes not creating a 100K or so .newsrc.eld by
> default.
>
I beg to differ. from the beginners point it's still a bit difficult
to set up a gnus environment. Looking at other news readers
(blasphemy, I know) I can simply list all the groups and enter
them. All these subtle differences between subscribed
/unsbscribed/killed and so on are very nice once I have set up my whole
environment. But it's extremely non-logical if suddenly I can't access
the whole feed anymore without explicitely reloading the active file
-- and even at a fast scientific internet access with a fast computer
it still takes damned long to load the whole active file from the
server.
Besides that a newbie will not know what to do, and will switch to tin
after 5 minutes without getting what he wants (yeah yeah, RTFM, I
know. _I_ do, but we all know our users). The thousands of different
listing/loading/browsing commands don't help either, as they are layed
out in a totally flat way: there is no "hirarchy" build of them with
"general" commands which do the right thing most of the time and
"expert" commands, unfortunately. Even the menu doesn't suggest such a
hirarchy.
Conclusion: Follow the principle of least surprise, and that mean:
Selecting "List killed groups" selects the killed groups. Point. Don't
assume all a user understand the difference between C-u A k and A k;
and hey why is there a own list active A A.... has a C-u A A a
different effect.....
all of course just IMHO
jtl
next prev parent reply other threads:[~1997-07-08 2:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-06 15:24 Lars Magne Ingebrigtsen
1997-07-06 16:05 ` Hrvoje Niksic
1997-07-07 9:08 ` Lars Magne Ingebrigtsen
1997-07-07 21:14 ` Hrvoje Niksic
1997-07-07 23:15 ` Jens Lautenbacher
1997-07-07 23:52 ` Hrvoje Niksic
1997-07-08 1:28 ` Steven L Baur
1997-07-08 2:39 ` Jens Lautenbacher [this message]
1997-07-08 4:01 ` Hrvoje Niksic
1997-07-08 5:28 ` Sudish Joseph
1997-07-08 7:34 ` Hrvoje Niksic
1997-07-08 16:56 ` Sudish Joseph
1997-07-08 18:30 ` Jens Lautenbacher
1997-07-08 20:49 ` Hrvoje Niksic
1997-07-10 18:16 ` Lars Magne Ingebrigtsen
1997-07-07 8:51 ` Steven L Baur
1997-07-07 11:36 ` Lars Magne Ingebrigtsen
1997-07-07 21:13 ` Hrvoje Niksic
1997-07-07 23:56 ` Steven L Baur
1997-07-10 18:08 ` Lars Magne Ingebrigtsen
1997-07-13 23:25 ` Hrvoje Niksic
1997-07-18 3:12 ` Steven L Baur
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=m37mf2e08h.fsf@jens.metrix.de \
--to=jens@metrix.de \
--cc=ding@ifi.uio.no \
--cc=jens@lemming0.lem.uni-karlsruhe.de \
/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).