Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Schmidt <dfan@harmonixmusic.com>
Subject: Re: Question about ticked articles being unticked...
Date: 16 May 1997 16:46:06 -0400	[thread overview]
Message-ID: <wkenb7no1d.fsf@turangalila.harmonixmusic.com> (raw)
In-Reply-To: Justin Sheehy's message of 16 May 1997 16:11:06 -0400

Justin Sheehy <dworkin@ccs.neu.edu> writes:

| Dan Schmidt <dfan@harmonixmusic.com> writes:
| 
| > I have noticed that sometimes if I have one nnfolder *Summary* buffer
| > open, and switch buffers back to *Group* without closing it, and then
| > enter another nnfolder group, a lot of the first group's articles get
| > unticked.
| 
| Why would you do this?

A standard scenario is that I'm reading through the messages in my
personal folder, and I reply to one of them.  While writing my reply, I
realize that I need some piece of information in one of my mailing-list
folders.  So I switch-buffer to *Group* and select the appropriate
mailing-list folder.  Then I curse as I realize what I have just done.

| You should exit a group by pressing 'q' in its Summary buffer, not by
| changing buffers.

Yes, that is true.  But I'll make the following points:

1. I thought that somewhere in the gnus manual, it says that you're
   allowed to have multiple *Summary* buffers open at once.  Of
   course, now I can't find that section, but in any case:

2. If opening multiple *Summary* buffers results in loss of data, the
   user should be forcibly prevented from doing it.

3. I could live with a one *Summary* buffer restriction, but multiple
   *Summary* buffers are useful in the scenario mentioned above.  In
   that scenario,

   a. I was never in the first *Summary* buffer at a time where I
      wanted it to go away; I would have had to explicitly return to
      it from my *reply* buffer and then hit 'q', which is a slight
      pain both to execute and to remember to do.

   b. Having to 'q' out of the first *Summary* buffer is also a pain
      in that I'm in the middle of traversing my messages in that
      folder, and I'd rather not have to quit out of that and re-enter
      just to reply to one of the messages.

-- 
                 Dan Schmidt --> dfan@harmonixmusic.com, dfan@alum.mit.edu
Honest Bob & the                 http://www2.thecia.net/users/dfan/
Factory-to-Dealer Incentives --> http://www2.thecia.net/users/dfan/hbob/
          Gamelan Galak Tika --> http://web.mit.edu/galak-tika/www/


  reply	other threads:[~1997-05-16 20:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-16 12:42 Karl Asha
1997-05-16 14:13 ` Mark Boyns
1997-05-16 14:56   ` Kai Grossjohann
1997-05-16 15:02     ` Karl Asha
1997-05-16 15:08     ` Mark Boyns
1997-05-16 17:13       ` Hrvoje Niksic
1997-05-16 17:31         ` Mark Boyns
1997-05-16 18:05           ` Hrvoje Niksic
1997-05-16 17:53       ` Stainless Steel Rat
1997-05-16 18:43 ` Dan Schmidt
1997-05-16 20:11   ` Justin Sheehy
1997-05-16 20:46     ` Dan Schmidt [this message]
1997-05-16 21:43       ` Hrvoje Niksic
1997-05-16 22:42       ` Sudish Joseph
1997-05-17  3:58         ` Lars Magne Ingebrigtsen
1997-05-17 13:30     ` Kai Grossjohann
1997-05-18  7:22       ` Hrvoje Niksic
1997-05-17  3:55   ` Lars Magne Ingebrigtsen
1997-05-17  3:54 ` Lars Magne Ingebrigtsen

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=wkenb7no1d.fsf@turangalila.harmonixmusic.com \
    --to=dfan@harmonixmusic.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).