From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Juanma Barranquero <lekktu@gmail.com>,
MON KEY <monkey@sandpframing.com>,
6241@debbugs.gnu.org
Subject: bug#6241: Please make buffer-offer-save permanent local
Date: Wed, 13 Jul 2011 23:59:41 +0200 [thread overview]
Message-ID: <m3bowxrgdu.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <AANLkTikSnv1A7gCeyA0xJjFGjnoM8kfBg5FQAZNn3_2f@mail.gmail.com> (Lennart Borgman's message of "Fri, 28 May 2010 02:39:51 +0200")
Lennart Borgman <lennart.borgman@gmail.com> writes:
>> So, now that the question of "should it ideally be permanent-local?" is
>> resolved, the remaining question is: "what would be the impact of such
>> a change", which requires examining all uses of the variable and
>> assessing the effect of the change for each case.
>
> I think the only really important cases is when buffer-offer-save is
> set to t somewhere which is in
>
> ./ediff-util.el:589: (setq buffer-offer-save t) ; ask before
> killing buffer
> Seems OK.
>
> ./gnus/message.el:2900: (setq buffer-offer-save t)
> ./mail/sendmail.el:654: (setq buffer-offer-save t)
> ./mh-e/mh-folder.el:647: (setq buffer-offer-save t)
> All those seems OK to me, but I am not sure. I am not using them.
>
> ./org/org-src.el:629: (setq buffer-offer-save t)
> Seems OK.
I think it would make sense to make it 'permanent-local in these cases,
at least. If there's only these use cases, then it seems like the right
thing to do.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-13 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 17:33 bug#6241: Please make buffer-offer-save permanent local Lennart Borgman
2010-05-25 16:49 ` Stefan Monnier
2010-05-25 17:24 ` Juanma Barranquero
2010-05-25 18:09 ` Stefan Monnier
2010-05-25 18:53 ` Lennart Borgman
2010-05-27 1:28 ` MON KEY
2010-05-27 1:35 ` Lennart Borgman
2010-05-27 21:56 ` MON KEY
2010-05-27 22:25 ` Lennart Borgman
2010-05-28 0:27 ` Stefan Monnier
2010-05-28 0:39 ` Lennart Borgman
2011-07-13 21:59 ` Lars Magne Ingebrigtsen [this message]
2011-07-16 19:02 ` Stefan Monnier
2011-07-16 20:00 ` Lars Magne Ingebrigtsen
2010-05-28 4:38 ` MON KEY
2010-05-28 4:48 ` MON KEY
2010-05-28 10:39 ` Lennart Borgman
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=m3bowxrgdu.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=6241@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=lennart.borgman@gmail.com \
--cc=monkey@sandpframing.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.
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).