GNU bug report logs - #28412
26.0.50; Let save-some-buffers accept write-contents-functions

Previous Next

Package: emacs;

Reported by: Eric Abrahamsen <eric <at> ericabrahamsen.net>

Date: Sun, 10 Sep 2017 21:52:02 UTC

Severity: wishlist

Found in version 26.0.50

Done: Eric Abrahamsen <eric <at> ericabrahamsen.net>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 28412 <at> debbugs.gnu.org (full text, mbox):

From: Kaushal Modi <kaushal.modi <at> gmail.com>
To: 28412 <at> debbugs.gnu.org
Subject: 26.0.50; Let save-some-buffers accept write-contents-functions
Date: Mon, 18 Sep 2017 16:16:05 +0000
[Message part 1 (text/plain, inline)]
Hello Eric, Eli:

I became a victim of this change because of these overlapping use-cases:

- I use ggtags.el that creates a hidden (is that the right term for that?)
buffer (starting with space) to fontify code snippets using the file's
major mode.
- The major mode I use (verilog-mode) sets write-file-functions to a
non-nil value.

So each time I quit emacs, I get a prompt to save that hidden buffer "
*Code-Fontify*" (which it didn't earlier, as intended).

Details: https://github.com/leoliu/ggtags/issues/157

I suggested calling (set-buffer-modified-p nil) in that special buffer.

But is that the best way to fix this? Or should save-some-buffers never try
to save buffers whose names begin with space?

PS: Please CC me on the replies, else I won't get those.

-- 

Kaushal Modi
[Message part 2 (text/html, inline)]

This bug report was last modified 7 years and 294 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.