| blob | 7957343714607597d479d1e4ce1e16120edd65f4 |
1 ;;; easymenu.el --- support the easymenu interface for defining a menu
3 ;; Copyright (C) 1994, 1996, 1998-2011 Free Software Foundation, Inc.
5 ;; Keywords: emulations
6 ;; Author: Richard Stallman <rms@gnu.org>
7 ;; Package: emacs
9 ;; This file is part of GNU Emacs.
11 ;; GNU Emacs is free software: you can redistribute it and/or modify
12 ;; it under the terms of the GNU General Public License as published by
13 ;; the Free Software Foundation, either version 3 of the License, or
14 ;; (at your option) any later version.
16 ;; GNU Emacs is distributed in the hope that it will be useful,
17 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
18 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 ;; GNU General Public License for more details.
21 ;; You should have received a copy of the GNU General Public License
22 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
24 ;;; Commentary:
26 ;; This is compatible with easymenu.el by Per Abrahamsen
27 ;; but it is much simpler as it doesn't try to support other Emacs versions.
28 ;; The code was mostly derived from lmenu.el.
30 ;;; Code:
35 "Determine when equivalent key bindings are computed for easy-menu menus.
36 It can take some time to calculate the equivalent key bindings that are shown
37 in a menu. If the variable is on, then this calculation gives a (maybe
38 noticeable) delay when a mode is first entered. If the variable is off, then
39 this delay will come when a menu is displayed the first time. If you never use
47 ;;;###autoload
49 "Define a menu bar submenu in maps MAPS, according to MENU.
51 If SYMBOL is non-nil, store the menu keymap in the value of SYMBOL,
52 and define SYMBOL as a function to pop up the menu, with DOC as its doc string.
53 If SYMBOL is nil, just store the menu keymap into MAPS.
55 The first element of MENU must be a string. It is the menu bar item name.
56 It may be followed by the following keyword argument pairs
58 :filter FUNCTION
60 FUNCTION is a function with one argument, the rest of menu items.
61 It returns the remaining items of the displayed menu.
63 :visible INCLUDE
65 INCLUDE is an expression; this menu is only visible if this
66 expression has a non-nil value. `:included' is an alias for `:visible'.
68 :active ENABLE
70 ENABLE is an expression; the menu is enabled for selection whenever
71 this expression's value is non-nil. `:enable' is an alias for `:active'.
73 The rest of the elements in MENU, are menu items.
75 A menu item is usually a vector of three elements: [NAME CALLBACK ENABLE]
77 NAME is a string--the menu item name.
79 CALLBACK is a command to run when the item is chosen,
80 or a list to evaluate when the item is chosen.
82 ENABLE is an expression; the item is enabled for selection
83 whenever this expression's value is non-nil.
85 Alternatively, a menu item may have the form:
87 [ NAME CALLBACK [ KEYWORD ARG ] ... ]
89 Where KEYWORD is one of the symbols defined below.
91 :keys KEYS
93 KEYS is a string; a complex keyboard equivalent to this menu item.
94 This is normally not needed because keyboard equivalents are usually
95 computed automatically.
96 KEYS is expanded with `substitute-command-keys' before it is used.
98 :key-sequence KEYS
100 KEYS is nil, a string or a vector; nil or a keyboard equivalent to this
101 menu item.
102 This is a hint that will considerably speed up Emacs' first display of
103 a menu. Use `:key-sequence nil' when you know that this menu item has no
104 keyboard equivalent.
106 :active ENABLE
108 ENABLE is an expression; the item is enabled for selection whenever
109 this expression's value is non-nil. `:enable' is an alias for `:active'.
111 :visible INCLUDE
113 INCLUDE is an expression; this item is only visible if this
114 expression has a non-nil value. `:included' is an alias for `:visible'.
116 :label FORM
118 FORM is an expression that will be dynamically evaluated and whose
119 value will be used for the menu entry's text label (the default is NAME).
121 :suffix FORM
123 FORM is an expression that will be dynamically evaluated and whose
124 value will be concatenated to the menu entry's label.
126 :style STYLE
128 STYLE is a symbol describing the type of menu item. The following are
129 defined:
131 toggle: A checkbox.
132 Prepend the name with `(*) ' or `( ) ' depending on if selected or not.
133 radio: A radio button.
134 Prepend the name with `[X] ' or `[ ] ' depending on if selected or not.
135 button: Surround the name with `[' and `]'. Use this for an item in the
136 menu bar itself.
137 anything else means an ordinary menu item.
139 :selected SELECTED
141 SELECTED is an expression; the checkbox or radio button is selected
142 whenever this expression's value is non-nil.
144 :help HELP
146 HELP is a string, the help to display for the menu item.
148 A menu item can be a string. Then that string appears in the menu as
149 unselectable text. A string consisting solely of hyphens is displayed
150 as a solid horizontal line.
152 A menu item can be a list with the same format as MENU. This is a submenu."
159 "Return a binding suitable to pass to `define-key'.
160 This is expected to be bound to a mouse event."
161 ;; Under Emacs this is almost trivial, whereas under XEmacs this may
162 ;; involve defining a function that calls popup-menu.
176 ;;;###autoload
178 ;; We can't do anything that might differ between Emacs dialects in
179 ;; `easy-menu-define' in order to make byte compiled files
180 ;; compatible. Therefore everything interesting is done in this
181 ;; function.
187 ;; FIXME: XEmacs uses popup-menu which calls the binding
188 ;; while x-popup-menu only returns the selection.
203 "Convert MENU to the right thing to return from a menu filter.
204 MENU is a menu as computed by `easy-menu-define' or `easy-menu-create-menu' or
205 a symbol whose value is such a menu.
206 In Emacs a menu filter must return a menu (a keymap), in XEmacs a filter must
207 return a menu items list (without menu name and keywords).
208 This function returns the right thing in the two cases.
209 If NAME is provided, it is used for the keymap."
212 ;; If it's a cons but not a keymap, then it can't be right
213 ;; unless it's an XEmacs menu.
216 ;; It's just a menu entry.
218 menu)
221 "Dynamically scoped var to register already used keys in a menu.
222 If it holds a list, this is expected to be a list of keys already seen in the
225 ;;;###autoload
227 "Create a menu called MENU-NAME with items described in MENU-ITEMS.
228 MENU-NAME is a string, the name of the menu. MENU-ITEMS is a list of items
229 possibly preceded by keyword pairs as described in `easy-menu-define'."
232 prop keyword arg label enable filter visible help)
233 ;; Look for keywords.
240 (:filter
248 nil ; Invisible menu entry, return nil.
257 ;; The filter expects the menu in its XEmacs form and the
258 ;; pre-filter form will only be passed to the filter
259 ;; anyway, so we'd better not convert it at all (it will
260 ;; be converted on the fly by easy-menu-filter-return).
261 menu-items
266 menu)))
269 ;; Known button types.
276 "Memoize the value returned by `easy-menu-convert-item-1' called on ITEM.
277 This makes key-shortcut-caching work a *lot* better when this
278 conversion is done from within a filter.
279 This also helps when the NAME of the entry is recreated each time:
280 since the menu is built and traversed separately, the lookup
281 would always fail because the key is `equal' but not `eq'."
286 ;; Merging multiple entries with the same name is sometimes what we
287 ;; want, but not when the entries are actually different (e.g. same
288 ;; name but different :suffix as seen in cal-menu.el) and appear in
289 ;; the same menu. So we try to detect and resolve conflicts.
291 ;; We need to use some distinct object, ideally a symbol, ideally
292 ;; related to the `name'. Uninterned symbols do not work (they
293 ;; are apparently turned into strings and re-interned later on).
300 result))
303 "Parse an item description and convert it to a menu keymap element.
304 ITEM defines an item as in `easy-menu-define'."
315 ;; Invisible menu item. Don't insert into keymap.
326 cache cache-specified)
331 keyword arg suffix visible style selected keys)
365 keys)
382 ;; Invisible menu item. Don't insert into keymap.
391 ;; `intern' the name so as to merge multiple entries with the same name.
392 ;; It also makes it easier/possible to lookup/change menu bindings
393 ;; via keymap functions.
403 "Add binding in MENU for KEY => ITEM. Similar to `define-key-after'.
404 If KEY is not nil then delete any duplications.
405 If ITEM is nil, then delete the definition of KEY.
407 Optional argument BEFORE is nil or a key in MENU. If BEFORE is not nil,
408 put binding before the item in MENU named BEFORE; otherwise,
409 if a binding for KEY is already present in MENU, just change it;
410 otherwise put the new binding last in MENU.
411 BEFORE can be either a string (menu item name) or a symbol
412 \(the fake function key for the menu item).
413 KEY does not have to be a symbol, and comparison is done with equal."
416 tail done)
421 ;; If key is nil, stop here, otherwise keep going past the
422 ;; inserted element so we can delete any duplications that come
423 ;; later.
444 "Return t if NAME is the name of menu item ITEM.
445 NAME can be either a string, or a symbol.
446 ITEM should be a keymap binding of the form (KEY . MENU-ITEM)."
451 ;; Match against the text that is displayed to the user.
454 ;; Also check the string version of the symbol name,
455 ;; for backwards compatibility.
459 "Return true if form X never evaluates to nil."
466 "Return a unique symbol with CALLBACK as function value.
467 When non-nil, NOEXP indicates that CALLBACK cannot be an expression
468 \(i.e. does not need to be turned into a function)."
474 ;; `functionp' is probably not needed.
476 callback
478 command))
480 ;;;###autoload
482 "Change menu found at PATH as item NAME to contain ITEMS.
483 PATH is a list of strings for locating the menu that
484 should contain a submenu named NAME.
485 ITEMS is a list of menu items, as in `easy-menu-define'.
486 These items entirely replace the previous items in that submenu.
488 If MAP is specified, it should normally be a keymap; nil stands for the local
489 menu-bar keymap. It can also be a symbol, which has earlier been used as the
490 first argument in a call to `easy-menu-define', or the value of such a symbol.
492 If the menu located by PATH has no submenu named NAME, add one.
493 If the optional argument BEFORE is present, add it just before
494 the submenu named BEFORE, otherwise add it at the end of the menu.
496 To implement dynamic menus, either call this from
497 `menu-bar-update-hook' or use a menu filter."
500 ;; XEmacs needs the following two functions to add and remove menus.
501 ;; In Emacs this is done automatically when switching keymaps, so
502 ;; here easy-menu-remove is a noop.
504 "Remove MENU from the current menu bar.
505 Contrary to XEmacs, this is a nop on Emacs since menus are automatically
506 \(de)activated when the corresponding keymap is (de)activated.
511 "Add the menu to the menubar.
512 On Emacs, menus are already automatically activated when the
513 corresponding keymap is activated. On XEmacs this is needed to
514 actually add the menu to the current menubar.
516 You should call this once the menu and keybindings are set up
517 completely and menu filter functions can be expected to work."
518 )
521 "Add submenu SUBMENU in the menu at MENU-PATH.
522 If BEFORE is non-nil, add before the item named BEFORE.
523 If IN-MENU is non-nil, follow MENU-PATH in IN-MENU.
524 This is a compatibility function; use `easy-menu-add-item'."
527 submenu before))
530 "To the submenu of MAP with path PATH, add ITEM.
532 If an item with the same name is already present in this submenu,
533 then ITEM replaces it. Otherwise, ITEM is added to this submenu.
534 In the latter case, ITEM is normally added at the end of the submenu.
535 However, if BEFORE is a string and there is an item in the submenu
536 with that name, then ITEM is added before that item.
538 MAP should normally be a keymap; nil stands for the local menu-bar keymap.
539 It can also be a symbol, which has earlier been used as the first
540 argument in a call to `easy-menu-define', or the value of such a symbol.
542 PATH is a list of strings for locating the submenu where ITEM is to be
543 added. If PATH is nil, MAP itself is used. Otherwise, the first
544 element should be the name of a submenu directly under MAP. This
545 submenu is then traversed recursively with the remaining elements of PATH.
547 ITEM is either defined as in `easy-menu-define' or a non-nil value returned
548 by `easy-menu-item-present-p' or `easy-menu-remove-item' or a menu defined
549 earlier by `easy-menu-define' or `easy-menu-create-menu'."
555 ;; This is a value returned by `easy-menu-item-present-p' or
556 ;; `easy-menu-remove-item'.
562 ;; Item is a keymap, find the prompt string and use as item name.
568 "In submenu of MAP with path PATH, return non-nil if item NAME is present.
569 MAP and PATH are defined as in `easy-menu-add-item'.
570 NAME should be a string, the name of the element to be looked for."
574 "From submenu of MAP with path PATH remove item NAME.
575 MAP and PATH are defined as in `easy-menu-add-item'.
576 NAME should be a string, the name of the element to be removed."
580 ret))
583 "In menu MENU try to look for menu item with name NAME.
584 If a menu item is found, return (NAME . item), otherwise return nil.
585 If item is an old format item, a new format item is returned."
586 ;; The call to `lookup-key' also calls the C function `get_keyelt' which
587 ;; looks inside a menu-item to only return the actual command. This is
588 ;; not what we want here. We should either add an arg to lookup-key to be
589 ;; able to turn off this "feature", or else we could use map-keymap here.
590 ;; In the mean time, I just use `assq' which is an OK approximation since
591 ;; menus are rarely built from vectors or char-tables.
594 ret enable cache label)
597 ;; This is the old menu format. Convert it to new format.
612 )))
615 "Lookup menu item NAME in keymap MAP.
616 Like `lookup-key' except that NAME is not an array but just a single key
617 and that NAME can be a string representing the menu item's name."
620 ;; `lookup-key' failed and we have a menu item name: look at the
621 ;; actual menu entries's names.
626 ;; Found it!! Look for it again with
627 ;; `lookup-key' so as to handle inheritance and
628 ;; to extract the actual command/keymap bound to
629 ;; `name' from the item (via get_keyelt).
631 map)))))
634 "Return a sparse keymap in which to add or remove an item.
635 MAP and PATH are as defined in `easy-menu-add-item'.
637 TO-MODIFY, if non-nil, is the name of the item the caller
638 wants to modify in the map that we return.
639 In some cases we use that to select between the local and global maps."
646 ;; Look for PATH in each map.
652 map name))
654 maps))))
656 ;; Prefer a map that already contains the to-be-modified entry.
661 ;; Use the first valid map.
664 ;; Otherwise, make one up.
665 ;; Hardcoding current-local-map is lame, but it's difficult
666 ;; to know what the caller intended for us to do ;-(
672 newmap))))
674 map)
678 ;;; easymenu.el ends here