aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMichal Nazarewicz2013-06-30 18:29:23 -0400
committerStefan Monnier2013-06-30 18:29:23 -0400
commitef099a941f7fb2d74ce1768388463f18b284f9c5 (patch)
tree1573bfacf90fc940c297c5428c132e9e65318716 /doc
parent6d89e343ab402851d94e37b2ca79a67e4c6fb474 (diff)
downloademacs-ef099a941f7fb2d74ce1768388463f18b284f9c5.tar.gz
emacs-ef099a941f7fb2d74ce1768388463f18b284f9c5.zip
Add `remember-notes' function to store random notes across Emacs
restarts. * remember.el (remember-data-file): Add :set callback to affect notes buffer (if any). (remember-notes): New command. (remember-notes-buffer-name, bury-remember-notes-on-kill): New defcustoms for the `remember-notes' function. (remember-notes-save-and-bury-buffer): New command. (remember-notes-mode-map): New variable. (remember-mode): New minor mode. (remember-notes--kill-buffer-query): New function. * lisp/startup.el (initial-buffer-choice): Add notes to custom type. * src/buffer.c (FKill_buffer): Run `kill-buffer-query-functions' before checking whether buffer is modified. This lets `kill-buffer-query-functions' cancel killing of the buffer or save its content before `kill-buffer' asks user the "Buffer %s modified; kill anyway?" question. * remember.el (remember-append-to-file): Don't mix `find-buffer-visiting' and `get-file-buffer'. * lisp/files.el (find-file-noselect): Simplify conditional expression.
Diffstat (limited to 'doc')
-rw-r--r--doc/lispref/buffers.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lispref/buffers.texi b/doc/lispref/buffers.texi
index 40fd0176116..01269851250 100644
--- a/doc/lispref/buffers.texi
+++ b/doc/lispref/buffers.texi
@@ -1065,7 +1065,7 @@ Buffer foo.changed modified; kill anyway? (yes or no) @kbd{yes}
1065@end deffn 1065@end deffn
1066 1066
1067@defvar kill-buffer-query-functions 1067@defvar kill-buffer-query-functions
1068After confirming unsaved changes, @code{kill-buffer} calls the functions 1068Before confirming unsaved changes, @code{kill-buffer} calls the functions
1069in the list @code{kill-buffer-query-functions}, in order of appearance, 1069in the list @code{kill-buffer-query-functions}, in order of appearance,
1070with no arguments. The buffer being killed is the current buffer when 1070with no arguments. The buffer being killed is the current buffer when
1071they are called. The idea of this feature is that these functions will 1071they are called. The idea of this feature is that these functions will