From: Dave Abrahams <dave@boostpro.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
"8891@debbugs.gnu.org" <8891@debbugs.gnu.org>
Subject: bug#8891: 23.3; save-buffer messages about writing files that may not be written
Date: Mon, 4 Jul 2011 16:36:02 -0400 [thread overview]
Message-ID: <45DE9080-191C-45FA-993D-ADEEF2435BCF@boostpro.com> (raw)
In-Reply-To: <87aacuuene.fsf@stupidchicken.com>
On Jul 4, 2011, at 1:41 PM, Chong Tiding <cyd@stupidchicken.com> wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>>> I don't think it's worth changing.
>>
>> It would be a very minor change -- it would just be moving a `message'
>> down into `basic-save-buffer-2' from `save-buffer', I think.
>
> The implications are not obvious. One good thing about emitting the
> "saving" message early is that if any of the intermediate steps take a
> long time, at least the user is informed about what Emacs is working on.
>
> Postphoning the "saving" message eliminates that benefit, for the very
> minor benefit of handling a corner case (a custom write-file-functions
> entry) a tiny bit better.
FWIW I think I agree with you. I work around it by advising save-buffer; maybe that's for the best.
--
BoostPro Computing * http://boostpro.com
[Sent from coveted but awkward mobile device]
prev parent reply other threads:[~2011-07-04 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 16:50 bug#8891: 23.3; save-buffer messages about writing files that may not be written Dave Abrahams
2011-07-03 16:15 ` Lars Magne Ingebrigtsen
2011-07-03 20:26 ` Dave Abrahams
2011-07-03 20:31 ` Lars Magne Ingebrigtsen
2011-07-03 20:51 ` Dave Abrahams
2011-07-04 2:35 ` Chong Yidong
2011-07-04 12:19 ` Lars Magne Ingebrigtsen
2011-07-04 17:41 ` Chong Yidong
2011-07-04 20:36 ` Dave Abrahams [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45DE9080-191C-45FA-993D-ADEEF2435BCF@boostpro.com \
--to=dave@boostpro.com \
--cc=8891@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.