From: MON KEY <monkey@sandpframing.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6241@debbugs.gnu.org
Subject: bug#6241: Please make buffer-offer-save permanent local
Date: Fri, 28 May 2010 00:48:10 -0400 [thread overview]
Message-ID: <AANLkTimZRfUJnk4EdAlB_eZxLTI3HJcNhJv-wMB_lUbx@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinWI2Q-LdLGycrt-4t4uDXvn0rcdt12DaoEKTNL@mail.gmail.com>
On Thu, May 27, 2010 at 6:25 PM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
>
> Please explain more exactly in what situations and why you think they
> want to kill `buffer-offer-save'. If you do that we can fix such
> cases. I can't think of any myself at the moment.
>
This is wrong. It is your request, you should be explaining on
emacs-devel the exact
reason, rationale and use case intended for why this change is needed.
> Same question as above. Exactly when and why?
Indeed.
What are the specific situations this change will remedy.
What is the current practice for dealing with them.
What is lost if the proposed change doesn't occur.
These are the things you should be asking in a more public forum.
--
/s_P\
next prev parent reply other threads:[~2010-05-28 4:48 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
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 [this message]
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=AANLkTimZRfUJnk4EdAlB_eZxLTI3HJcNhJv-wMB_lUbx@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=6241@debbugs.gnu.org \
--cc=lennart.borgman@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).