[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-function
From: |
Eric Abrahamsen |
Subject: |
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions |
Date: |
Mon, 18 Sep 2017 12:12:01 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Kaushal Modi <kaushal.modi@gmail.com>
>> Date: Mon, 18 Sep 2017 16:16:05 +0000
>>
>> - 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?
>
> Exempting buffers whose name starts with a space sounds reasonable.
> Eric?
Also, there don't appear to be any built-in functions or regexps for
dealing with "hidden" buffers, I'm assuming:
(not (string-prefix-p " " (buffer-name buffer)))
is okay?
- bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions), (continued)
- Message not available
- bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions), Eric Abrahamsen, 2017/09/10
- bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions), Eli Zaretskii, 2017/09/11
- bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions), Eric Abrahamsen, 2017/09/11
- bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions), Eli Zaretskii, 2017/09/12
- bug#28412: Acknowledgement (26.0.50; Let save-some-buffers accept write-contents-functions), Eric Abrahamsen, 2017/09/12
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Kaushal Modi, 2017/09/18
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions,
Eric Abrahamsen <=
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Kaushal Modi, 2017/09/18
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Eric Abrahamsen, 2017/09/18
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Kaushal Modi, 2017/09/18
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Eli Zaretskii, 2017/09/19
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Kaushal Modi, 2017/09/25
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Eli Zaretskii, 2017/09/19
bug#28412: 26.0.50; Let save-some-buffers accept write-contents-functions, Eli Zaretskii, 2017/09/18