From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: gnus-group-suspend forgets "readedness" of newly read articles
Date: 07 Feb 2001 14:30:29 -0500 [thread overview]
Message-ID: <873ddq1eay.fsf@home.com> (raw)
In-Reply-To: <vxkd7cupbsp.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "07 Feb 2001 13:50:46 -0500")
Karl Kleinpaste <karl@charcoal.com> writes:
> Dmitry Yaitskov <dimas@home.com> writes:
> > There may be a technical reason for what's happening but it is
> > still bad UI.
>
> I guess I'd have to ask what you were doing back in *Group*, and
> outside an "unresolved" (unaccounted-for?) *Summary*, in the first
> place so that the question can even arise.
>
> That is, by the manner in which you were using Gnus, you had subverted
> a piece of its intended UI mechanism. (Enter group from *Group*; read
> articles from *Summary*; exit *Summary* properly to induce updates in
> *Group*.) Having successively subverted that, you then complain that
> it didn't watch closely enough as you did it.
>
> I see the point you're trying to make, but I see it as akin to someone
> complaining that their car's transmission was left on the highway in
> pieces as they shifted into reverse while racing. Sure, you can do
> that -- but what were you doing it for, and why is the damage done
> considered to be the fault of the car?
Sorry, but that's BS. I am not sure what you mean by Gnus' "intended
UI mechanism". Multi-window, multi-process GUI systems were invented
to allow the user to switch from one activity/window/etc. to another
without concern for the "intended UI mechanism" (read predefined
sequence of actions). It is perfectly ok to open several summaries,
and keep them open at the same time. I do not have to exit one summary
to open another. I don't remember reading anywhere in Gnus docs that
using list-buffers was illegal while in a summary buffer. And I don't
*have* to remember that I have groups open when I suspend Gnus any
more that I have to remember whether I have made any changes to a
document in an editor when I close it - the program should keep track
of it.
As far as your comparison to shifting into reverse while racing
goes... although it is IMO completely bogus, it still would obviously
be a good feature if it were impossible to shift into reverse at any
forward speed that would result in damage. The fact that it may be
technically difficult is irrelevant.
> About the most "fix" I could see for this would be for
> gnus-group-suspend to refuse to do its thing if it saw any
> unaccounted-for *Summary* buffers lying around, which would analogize
> to a transmission interlock to prevent shifting into reverse.
>
>
--
Cheers,
-Dima.
next prev parent reply other threads:[~2001-02-07 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 16:57 Dmitry Yaitskov
2001-02-07 17:03 ` Karl Kleinpaste
2001-02-07 17:29 ` Toby Speight
2001-02-07 18:02 ` Dmitry Yaitskov
2001-02-07 18:03 ` Dmitry Yaitskov
2001-02-07 18:50 ` Karl Kleinpaste
2001-02-07 18:59 ` Paul Jarc
2001-02-07 19:30 ` Dmitry Yaitskov [this message]
2001-02-08 1:17 ` Dan Christensen
2001-02-08 2:19 ` Karl Kleinpaste
2001-02-11 15:03 ` ShengHuo ZHU
2001-02-08 0:08 ` Andreas Fuchs
2001-02-08 15:43 ` Kai Großjohann
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=873ddq1eay.fsf@home.com \
--to=dimas@home.com \
/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).