From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: master 5ee3c37: Make sure that all gnus buffers are killed on exit
Date: Wed, 29 Jan 2020 15:51:23 -0500 [thread overview]
Message-ID: <m1wo9a6l6c.fsf@gnu.org> (raw)
In-Reply-To: 87blqmyusz.fsf@gnus.org
> * Lars Ingebrigtsen <ynefv@tahf.bet> [2020-01-29 19:35:56 +0100]:
>
> sds@gnu.org (Sam Steingold) writes:
>
>> Make sure that all gnus buffers are killed on exit
>
> This introduces a bunch of compilation warnings:
>
> In end of data:
> gnus/smime.el:694:1: Warning: the function ‘gnus-get-buffer-create’ is not
> known to be defined.
> ELC gnus/spam-report.elc
> ELC gnus/spam-stat.elc
>
> It also sounds somewhat odd for a library like smime.el to be calling
> Gnus functions (and the same goes for the other calls in packages like
> mail-source.el).
Are these packages actually used outside of gnus?
Are the buffers in question intended to be seen by users?
> And why should buffers created by those packages be killed when you hit
> `q' in Gnus? This sounds like very surprising behaviour.
I found many buffers created by gnus lying around after I exit, and it
seemed like all the files in the gnus directory were only used by gnus.
Thanks.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1671
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://www.dhimmitude.org https://ffii.org https://jihadwatch.org
Experience comes with debts.
next prev parent reply other threads:[~2020-01-29 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200128154818.27592.27475@vcs0.savannah.gnu.org>
[not found] ` <20200128154820.7AEB620997@vcs0.savannah.gnu.org>
2020-01-29 18:35 ` master 5ee3c37: Make sure that all gnus buffers are killed on exit Lars Ingebrigtsen
2020-01-29 20:51 ` Sam Steingold [this message]
2020-01-30 18:36 ` Sam Steingold
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1wo9a6l6c.fsf@gnu.org \
--to=sds@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).