From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: article buffer still exists
Date: 04 Jun 2001 22:45:58 +0200 [thread overview]
Message-ID: <vafn17o6kjd.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <uu21wuha2.fsf@frank.pille3000.de> (Frank Haun's message of "04 Jun 2001 22:22:29 +0200")
Why is it bad that the Article buffer still exists after using `q'
to exit a Summary buffer? At times, I was happy it still existed.
Maybe you want `z' from the Group buffer to suspend Gnus? (Though I'm
not really sure what that does. But maybe it makes most of the
Gnus buffers go away.)
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-06-04 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 20:22 Frank Haun
2001-06-04 20:45 ` Kai Großjohann [this message]
2001-06-05 15:15 ` Frank Haun
2001-06-04 21:58 ` Francisco Solsona
2001-06-05 15:20 ` Frank Haun
2001-06-05 19:00 ` Francisco Solsona
2001-06-06 14:55 ` Frank Haun
2001-06-06 20:51 ` Josh Huber
2001-06-06 22:37 ` Frank Haun
2001-06-07 10:38 ` Kai Großjohann
2001-06-07 15:44 ` Frank Haun
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=vafn17o6kjd.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).