From: Frank Haun <pille3000@gmx.net>
Subject: Re: article buffer still exists
Date: 05 Jun 2001 17:20:44 +0200 [thread overview]
Message-ID: <u7kyr54xf.fsf@frank.pille3000.de> (raw)
In-Reply-To: <86n17nnbz3.fsf@biblio06.fciencias.unam.mx>
Francisco Solsona <flsc@hp.fciencias.unam.mx> writes:
> > I read some news then after reading (`q' or `c' in the summary buffer) I
> > stay in the group buffer. I noticed that there is still an *Article*
> > buffer. Hmm I don't like this, bug or feature?
>
> I'm not sure, but I don't like it either, so I use the following:
>
> (add-hook 'gnus-exit-group-hook
> (lambda ()
> (kill-buffer-safe gnus-article-buffer)))
I get with GNU Emacs 20.7.1:
Symbol's function definition is void: kill-buffer-safe
Frank
--
(error "Couldn't find doc group")
next prev parent reply other threads:[~2001-06-05 15:20 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
2001-06-05 15:15 ` Frank Haun
2001-06-04 21:58 ` Francisco Solsona
2001-06-05 15:20 ` Frank Haun [this message]
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=u7kyr54xf.fsf@frank.pille3000.de \
--to=pille3000@gmx.net \
/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).