From: MON KEY <monkey@sandpframing.com>
To: 6241@debbugs.gnu.org
Cc: Juanma Barranquero <lekktu@gmail.com>
Subject: bug#6241: Please make buffer-offer-save permanent local
Date: Wed, 26 May 2010 21:28:15 -0400 [thread overview]
Message-ID: <AANLkTilP8P9QbyWHXJS0TKCE8kvurQq_QVidLEIbwnqo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimzeLS88bEJt8Y70IL9td56X0i4Ka8NgklNBYeI@mail.gmail.com>
> importantly, I'm not sure how it'd affect existing code. Could someone
> investigate how safe would be such a change, and could someone argue for
> (and/or against) it?
I don't have a definitive use case where this is clearly NTRT but in
general I find these types of `globals' invasive and I appreciate the
luxury of being able to nuke them when and as I see fit. Let
third-parties put the variable as needed if that is what they/their code
requires.... esp. as they may have no idea whatsoever what _I_ will be
doing with _my_ buffers. From a user perspective it is often a burden
for me to undo this type overreaching.
--
/s_p\
next prev parent reply other threads:[~2010-05-27 1:28 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 [this message]
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
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=AANLkTilP8P9QbyWHXJS0TKCE8kvurQq_QVidLEIbwnqo@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=6241@debbugs.gnu.org \
--cc=lekktu@gmail.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).