From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: gnus-group-suspend forgets "readedness" of newly read articles
Date: 07 Feb 2001 13:03:06 -0500 [thread overview]
Message-ID: <87hf261icl.fsf@home.com> (raw)
In-Reply-To: <vxkpugupgrv.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "07 Feb 2001 12:03:16 -0500")
Karl Kleinpaste <karl@charcoal.com> writes:
> This is not specific to gnus-group-suspend. Any time that you are in
> *Group* and select a group, you get a *Summary* based on what is known
> at the time in the *Group* buffer. The reason is that updates to
> *Group* are made on exit from *Summary*. If you do not exit *Summary*
> in a way which allows Gnus to carry out normal updates, Gnus will
> simply start over again when you re-select the same group.
>
> This is not a bug. Perhaps it needs explanation somewhere, though.
Thanks for the explanation, but FWIW I disagree that it is not a bug.
"Forgetting" an action that the user has taken is akin to forgetting
e.g. that a file has been changed in a text editor. Imagine a feature
that would "suspend" (whatever that means) an edit session but will
lose all changes you have made to the files w/out so much as asking
you. There may be a technical reason for what's happening but it is
still bad UI. Same as Gnus asks about changes made to a new unsent
message it should ask about updating summaries (or update them
silently). IMHO.
--
Cheers,
-Dima.
next prev parent reply other threads:[~2001-02-07 18:03 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 [this message]
2001-02-07 18:50 ` Karl Kleinpaste
2001-02-07 18:59 ` Paul Jarc
2001-02-07 19:30 ` Dmitry Yaitskov
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=87hf261icl.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).