From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Gnus v5.4.62 is released
Date: 08 Jul 1997 06:01:30 +0200 [thread overview]
Message-ID: <kigvi2mp4yt.fsf@jagor.srce.hr> (raw)
In-Reply-To: Jens Lautenbacher's message of "08 Jul 1997 04:39:10 +0200"
Jens Lautenbacher <jens@metrix.de> writes:
> > 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.
Exactly. Which is why Gnus should provide the most palatable
behaviour by default. And I still think this category includes /not/
creating 100K+ .newsrc.eld by default.
> Looking at other news readers (blasphemy, I know) I can simply list
> all the groups and enter them.
You can do it in Gnus, too. Commands like `10 A T' will connect to
the server, get the list of groups and list them. I don't need the
list every day. And a beginner certainly doesn't need it in his
.newsrc.eld -- by default.
> But it's extremely non-logical if suddenly I can't access the whole
> feed anymore (...)
Sure you can -- see above.
> -- 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.
That's what all these others newsreaders do, in case you didn't know.
> 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).
And tin will do the exact same thing.
> 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.
Feel free to suggest a better layout of commands. I am sure Lars
would be happy to make Gnus equally usable to a totall dummy-type
beginner as well as RSI-prone-10-keys-per-second-control-meta-alt
expert.
> Conclusion: Follow the principle of least surprise,
I sounds like a broken record, but I'll say it again: the principle of
least surprise includes not creating giant files by default. If
necessary, the manual should be updated to explain the available
commands better.
If a person doesn't want to even glance at the manual, he'll be better
off with tin anyway.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Psychos _do not_ explode when sunlight hits them."
next prev parent reply other threads:[~1997-07-08 4:01 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
1997-07-08 4:01 ` Hrvoje Niksic [this message]
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=kigvi2mp4yt.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).