From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: still asked later after gnus-summary-exit-no-update
Date: Thu, 02 Feb 2012 18:54:34 -0500 [thread overview]
Message-ID: <87ehucdc5h.fsf@uwo.ca> (raw)
In-Reply-To: <87wr86wv37.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Dan Christensen <jdc@uwo.ca> writes:
>
>>>> Gnus doesn't prompt me. It just jumps me to the *Group* buffer and
>>>> leaves the *Summary* buffer hanging around.
>>>
>>> When you type `Q' in the group buffer?
>>
>> When I type `Q' in the summary buffer.
>
> Yes, that's what's supposed to happen if you don't have
> `gnus-kill-summary-on-exit' set. :-)
No. With gnus-kill-summary-on-exit set to nil, the summary buffer
is supposed to be renamed when you exit. If I hit `Q' in the summary
buffer, then I want any changes I made to that buffer to not be made.
But when I re-enter the group (after exiting with `Q' and with
gnus-kill-summary-on-exit set to nil) I just pop right back into the
*same* summary buffer, with the same changes still in place. I don't
think that makes sense. And it isn't consistent with what happens if I
exit with `q', and re-enter, which gives me a fresh summary buffer
(since the old one has been renamed).
Moreover, it looks like the intent of the code agrees with me.
In gnus-summary-exit-no-update I find:
(if (not gnus-kill-summary-on-exit)
(gnus-deaden-summary)
(gnus-close-group group)
(gnus-kill-buffer gnus-summary-buffer))
So I'm not sure why this isn't working!
> I think this bug report was about `Q' in the group buffer.
No, it was about `Q' in the summary buffer:
> Lars wrote:
>
> jidanni@jidanni.org writes:
>
> > Let's say we exit a group with
> > Q runs the command gnus-summary-exit-no-update
> > Well, later when we use
> > q runs the command gnus-group-exit
> > we are still asked
> > Update summary buffer *Summary ...*? (y, n, !, ., q, or C-h)
>
> Doesn't `Q' delete the summary buffer for you? It does for me.
The message jidanni sees when exiting gnus with q is a side-effect of
the same problem that I'm noticing when you exit the Summary buffer
with `Q'. And it's slightly dangerous, since my reaction is to hit
`y' when I see that question, which would save changes that I explicitly
asked gnus not to save.
Dan
next prev parent reply other threads:[~2012-02-02 23:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 18:32 jidanni
2011-11-29 5:42 ` Dan Christensen
2012-01-03 22:24 ` Lars Magne Ingebrigtsen
2012-01-05 14:01 ` jidanni
2012-01-06 20:47 ` Lars Magne Ingebrigtsen
2012-01-06 23:15 ` jidanni
2012-01-05 16:03 ` Dan Christensen
2012-01-06 20:46 ` Lars Magne Ingebrigtsen
2012-01-08 17:34 ` Dan Christensen
2012-01-27 17:12 ` Lars Ingebrigtsen
2012-01-28 0:57 ` Dan Christensen
2012-01-30 16:59 ` Lars Ingebrigtsen
2012-02-01 3:34 ` Dan Christensen
2012-02-01 13:18 ` Lars Ingebrigtsen
2012-02-02 23:54 ` Dan Christensen [this message]
2012-02-06 22:22 ` Lars Ingebrigtsen
2012-02-09 1:33 ` Dan Christensen
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=87ehucdc5h.fsf@uwo.ca \
--to=jdc@uwo.ca \
--cc=ding@gnus.org \
/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).