From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25642@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#25642: 26.0.50; Save unmodified buffers not visiting a file yet
Date: Wed, 8 Feb 2017 02:22:19 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1702080212590.8970@calancha-pc> (raw)
In-Reply-To: <83shnq569a.fsf@gnu.org>
On Tue, 7 Feb 2017, Eli Zaretskii wrote:
>> Subject: [PATCH] Save unmodified buffers not visiting a file yet
>>
>> * lisp/files.el (save-buffer): Set modified flag non-nil before
>> 'basic-save-buffer' call (Bug#25642).
>
> Please don't, at least not unconditionally. I use this feature all
> the time, e.g. when composing email messages.
OK.
>
> I don't actually understand why this would be a problem: the user
> explicitly wanted to reset the modified status of a buffer, why should
> Emacs second-guess what the user meant? But if there are some use
> cases where you find this annoying (please describe them), let's make
> this an optional behavior, off by default.
No i don't have in mind cases where i have being annoying but that.
Setting modified flag nil followed to trying to save the buffer
sounds like the user don't want to save the buffer.
I think we can close this bug report. Thanks.
prev parent reply other threads:[~2017-02-07 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:08 bug#25642: 26.0.50; Save unmodified buffers not visiting a file yet Tino Calancha
2017-02-07 16:13 ` Eli Zaretskii
2017-02-07 17:22 ` Tino Calancha [this message]
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=alpine.DEB.2.20.1702080212590.8970@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=25642@debbugs.gnu.org \
--cc=eliz@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).