+++
** When Emacs receives a USR1 or USR2 signal, this generates
-input event sequences: [signal usr1] or [signal usr2].
+input events: sigusr1 or sigusr2. Use special-event-map to
+handle these events.
+
\f
* Lisp Changes in Emacs 22.1
2006-12-19 Kim F. Storm <storm@cua.dk>
+ * bindings.el: Bind sigusr1 and sigusr2 in special-event-map
+ instead of global-map.
+
* files.el (magic-mode-alist): Allow matching file type by
calling a function at bob. Check for image types by calling
image-type-from-buffer. Suggested by Juanma Barranquero.
+2006-12-19 Kim F. Storm <storm@cua.dk>
+
+ * commands.texi (Misc Events): User signals now result in sigusr1
+ and sigusr2 events which are handled through special-event-map.
+ (Special Events): User signals and drag-n-drop are special.
+
2006-12-17 Richard Stallman <rms@gnu.org>
* loading.texi (Named Features): Explain subfeatures better.
+2006-12-19 Kim F. Storm <storm@cua.dk>
+
+ Rework 2006-12-04 change. A SIGUSR1 (SIGUSR2) signal now generates
+ a sigusr1 event instead of [signal usr1] sequence, and signal events
+ are now supposed to be handled via special-event-map.
+
+ * keyboard.c (kbd_buffer_store_event_hold): Undo 2006-12-04 change.
+ (make_lispy_event): Don't generate Qsignal prefix for code 0.
+ Abort if signal code is unknown.
+ (store_user_signal_events): Don't make Qsignal prefix (code 0).
+ (Qsignal): Move declaration back to process.c.
+ (syms_of_keyboard): Don't intern or staticpro it here.
+
+ * process.c (Qsignal): Declare here.
+ (syms_of_process): Intern or staticpro it.
+
+ * emacs.c (main): Rename user signals to sigusr1 and sigusr2.
+
+ * .gdbinit: Pass on SIGUSR1 and SIGUSR2 to Emacs.
+
2006-12-19 Juanma Barranquero <lekktu@gmail.com>
* buffer.c (syms_of_buffer) <buffer-display-table>: