comparison lispref/buffers.texi @ 11545:a91fcb58e8d2

Fix backwards test in kill-buffer-query-functions.
author Richard M. Stallman <rms@gnu.org>
date Mon, 24 Apr 1995 22:36:08 +0000
parents 431b1a011c29
children 73dc8205d259
comparison
equal deleted inserted replaced
11544:cc965273a769 11545:a91fcb58e8d2
693 After confirming unsaved changes, @code{kill-buffer} calls the functions 693 After confirming unsaved changes, @code{kill-buffer} calls the functions
694 in the list @code{kill-buffer-query-functions}, in order of appearance, 694 in the list @code{kill-buffer-query-functions}, in order of appearance,
695 with no arguments. The buffer being killed is the current buffer when 695 with no arguments. The buffer being killed is the current buffer when
696 they are called. The idea is that these functions ask for confirmation 696 they are called. The idea is that these functions ask for confirmation
697 from the user for various nonstandard reasons. If any of them returns 697 from the user for various nonstandard reasons. If any of them returns
698 non-@code{nil}, @code{kill-buffer} spares the buffer's life. 698 @code{nil}, @code{kill-buffer} spares the buffer's life.
699 @end defvar 699 @end defvar
700 700
701 @defvar kill-buffer-hook 701 @defvar kill-buffer-hook
702 This is a normal hook run by @code{kill-buffer} after asking all the 702 This is a normal hook run by @code{kill-buffer} after asking all the
703 questions it is going to ask, just before actually killing the buffer. 703 questions it is going to ask, just before actually killing the buffer.