Mercurial > emacs
view lisp/macros.el @ 1310:8db103d11270
* keyboard.c (echo_char, read_char): Apply EVENT_HEAD without first
testing for EVENT_HAS_PARAMETERS; EVENT_HEAD works properly on
all sorts of events now.
(read_key_sequence): Use the new accessors to decide in which window
an event occurred.
* keyboard.c (Qevent_unmodified): Replaced by...
(Qevent_symbol_elements): New property.
(syms_of_keyboard): initialize and staticpro the latter, not the
former.
* keyboard.c (readable_events): This doesn't need to scan and
discard mouse release events anymore; it just uses
EVENT_QUEUES_EMPTY.
(kbd_buffer_get_event): No need to skip past mouse release events.
* keyboard.c (button_down_location): New variable, which
stores the location at which each button was pressed, so we
can build a complete drag event when the button is released.
(make_lispy_event): When a button is pressed, record its
location in button_down_location, and turn it into a `down'
event. When a button is released, compare its release
location with its press location, and decide whether to call
it a `click' or `drag' event.
Change mouse movement events to be arranged like click events.
(format_modifiers): Note that the click modifier has no
written representation.
(modifier_names, modifer_symbols): New variables, used to
create the Qevent_symbol_elements property.
(modify_event_symbol): Change the format of the modified
symbol cache; there are too many modifier bits now to use a
vector indexed by a modifier mask. Use an assoc-list instead.
Document the format of the cache.
Put the Qevent_symbol_elements property on each new symbol,
instead of a Qevent_unmodified property.
(symbols_of_keyboard): Put Qevent_symbol_elements properties on
the symbols specified in head_table, not Qevent_unmodifed properties.
Initialize and staticpro modifier_symbols, and staticpro the
window elements of button_down_location.
author | Jim Blandy <jimb@redhat.com> |
---|---|
date | Fri, 02 Oct 1992 23:55:39 +0000 |
parents | 213978acbc1e |
children | af4fe5e670f2 |
line wrap: on
line source
;;; macros.el --- non-primitive commands for keyboard macros. ;; Copyright (C) 1985, 1986, 1987 Free Software Foundation, Inc. ;; Maintainer: FSF ;; This file is part of GNU Emacs. ;; GNU Emacs is free software; you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 2, or (at your option) ;; any later version. ;; GNU Emacs is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs; see the file COPYING. If not, write to ;; the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. ;;; Code: ;;;###autoload (defun name-last-kbd-macro (symbol) "Assign a name to the last keyboard macro defined. Argument SYMBOL is the name to define. The symbol's function definition becomes the keyboard macro string. Such a \"function\" cannot be called from Lisp, but it is a valid editor command." (interactive "SName for last kbd macro: ") (or last-kbd-macro (error "No keyboard macro defined")) (and (fboundp symbol) (not (stringp (symbol-function symbol))) (error "Function %s is already defined and not a keyboard macro." symbol)) (fset symbol last-kbd-macro)) ;;;###autoload (defun insert-kbd-macro (macroname &optional keys) "Insert in buffer the definition of kbd macro NAME, as Lisp code. Optional second arg KEYS means also record the keys it is on (this is the prefix argument, when calling interactively). This Lisp code will, when executed, define the kbd macro with the same definition it has now. If you say to record the keys, the Lisp code will also rebind those keys to the macro. Only global key bindings are recorded since executing this Lisp code always makes global bindings. To save a kbd macro, visit a file of Lisp code such as your ~/.emacs, use this command, and then save the file." (interactive "CInsert kbd macro (name): \nP") (insert "(fset '") (prin1 macroname (current-buffer)) (insert "\n ") (prin1 (symbol-function macroname) (current-buffer)) (insert ")\n") (if keys (let ((keys (where-is-internal macroname nil))) (while keys (insert "(global-set-key ") (prin1 (car keys) (current-buffer)) (insert " '") (prin1 macroname (current-buffer)) (insert ")\n") (setq keys (cdr keys)))))) ;;;###autoload (defun kbd-macro-query (flag) "Query user during kbd macro execution. With prefix argument, enters recursive edit, reading keyboard commands even within a kbd macro. You can give different commands each time the macro executes. Without prefix argument, reads a character. Your options are: Space -- execute the rest of the macro. DEL -- skip the rest of the macro; start next repetition. C-d -- skip rest of the macro and don't repeat it any more. C-r -- enter a recursive edit, then on exit ask again for a character C-l -- redisplay screen and ask again." (interactive "P") (or executing-macro defining-kbd-macro (error "Not defining or executing kbd macro")) (if flag (let (executing-macro defining-kbd-macro) (recursive-edit)) (if (not executing-macro) nil (let ((loop t)) (while loop (let ((char (let ((executing-macro nil) (defining-kbd-macro nil)) (message "Proceed with macro? (Space, DEL, C-d, C-r or C-l) ") (read-char)))) (cond ((= char ? ) (setq loop nil)) ((= char ?\177) (setq loop nil) (setq executing-macro "")) ((= char ?\C-d) (setq loop nil) (setq executing-macro t)) ((= char ?\C-l) (recenter nil)) ((= char ?\C-r) (let (executing-macro defining-kbd-macro) (recursive-edit)))))))))) ;;;###autoload (defun apply-macro-to-region-lines (top bottom &optional macro) "For each complete line between point and mark, move to the beginning of the line, and run the last keyboard macro. When called from lisp, this function takes two arguments TOP and BOTTOM, describing the current region. TOP must be before BOTTOM. The optional third argument MACRO specifies a keyboard macro to execute. This is useful for quoting or unquoting included text, adding and removing comments, or producing tables where the entries are regular. For example, in Usenet articles, sections of text quoted from another author are indented, or have each line start with `>'. To quote a section of text, define a keyboard macro which inserts `>', put point and mark at opposite ends of the quoted section, and use `\\[apply-macro-to-region-lines]' to mark the entire section. Suppose you wanted to build a keyword table in C where each entry looked like this: { \"foo\", foo_data, foo_function }, { \"bar\", bar_data, bar_function }, { \"baz\", baz_data, baz_function }, You could enter the names in this format: foo bar baz and write a macro to massage a word into a table entry: \\C-x ( \\M-d { \"\\C-y\", \\C-y_data, \\C-y_function }, \\C-x ) and then select the region of un-tablified names and use `\\[apply-macro-to-region-lines]' to build the table from the names. " (interactive "r") (or macro (progn (if (null last-kbd-macro) (error "No keyboard macro has been defined.")) (setq macro last-kbd-macro))) (save-excursion (let ((end-marker (progn (goto-char bottom) (beginning-of-line) (point-marker))) next-line-marker) (goto-char top) (if (not (bolp)) (forward-line 1)) (setq next-line-marker (point-marker)) (while (< next-line-marker end-marker) (goto-char next-line-marker) (save-excursion (forward-line 1) (set-marker next-line-marker (point))) (save-excursion (execute-kbd-macro (or macro last-kbd-macro)))) (set-marker end-marker nil) (set-marker next-line-marker nil)))) ;;;###autoload (define-key ctl-x-map "q" 'kbd-macro-query) ;;; macros.el ends here