This is Info file hypb.info, produced by Makeinfo-1.47 from the input file hypb.texinfo.  File: hypb.info, Node: Smart Keyboard Keys, Prev: Smart Mouse Keys, Up: Smart Key Reference Smart Keyboard Keys =================== When prompting for a Hyperbole argument, a press in the minibuffer: PRIMARY Terminates this minibuffer argument. SECONDARY Offers completion help for current minibuffer argument. When reading a Hyperbole menu item or a Hyperbole completion-based argument: PRIMARY Returns value selected at point if any, else nil. If value is the same as the contents of the minibuffer, it is used as the current minibuffer argument, otherwise, the minibuffer is erased and value is inserted there. SECONDARY Displays Hyperbole menu item help when item is selected. When pressed at the end of a line but not the end of a buffer: PRIMARY Scrolls up according to value of smart-scroll-proportional. If smart-scroll-proportional is nil (the default) or if point is on the top window line, scrolls up (forward) a windowful. Otherwise, tries to bring current line to top of window. Leaves point at end of line and returns t if scrolled, nil if not. SECONDARY Scrolls down according to value of smart-scroll-proportional. If smart-scroll-proportional is nil (the default) or if point is on the bottom window line, scrolls down (backward) a windowful. Otherwise, tries to bring current line to bottom of window. Leaves point at end of line and returns t if scrolled, nil if not. When pressed on a Hyperbole button: PRIMARY Activates button. SECONDARY Displays help for button, typically a summary of its attributes. When pressed on a Smart Menu item: PRIMARY Activates item. SECONDARY Displays help for item. When pressed at the end of a Help buffer: PRIMARY or SECONDARY Restores screen to configuration prior to help display. When pressed within an OO-Browser listing window: PRIMARY (1) in a blank buffer or at the end of a buffer, browser help information is displayed in the viewer window; (2) at the beginning of a (non-single char) class name, the classes ancestors are listed; (3) at the end of an entry line, scrolls listing up; (4) on the '...', following a class name, point is moved to the class descendency expansion; (5) before a feature name, the implementor classes of the name are listed (6) anywhere else on an entry line, the source is displayed for editing. SECONDARY (1) in a blank buffer, a selection list of buffer files is displayed; (2) at the beginning of a (non-single char) entry, the classes descendants are listed; (3) at the end of an entry line, scrolls listing down; (4) on the '...', following a class name, point is moved to the class expansion; (5) anywhere else on a class entry line, lists the class' features; (6) anywhere else on a feature entry line, lists the feature's implementors; (7) on a blank line following all entries, the current listing buffer is exited. When pressed within an OO-Browser Command Help Menu buffer: PRIMARY Executes an OO-Browser command whose key binding is at point. SECONDARY Displays help for an OO-Browser command whose key binding is at point. When pressed on an identifier within an OO-Browser source file: PRIMARY Tries to display identifier definition. SECONDARY Not applicable. When pressed within a C code source file: PRIMARY Jumps to the definition of selected C construct: (1) on a '#include' statement, the include file is displayed; (2) on a C identifier, the identifier definition is displayed, assuming the identifier is found within an 'etags' generated tag file in the current directory or any of its ancestor directories. (3) if 'smart-c-use-lib-man' is non-nil, the C identifier is recognized as a library symbol, and a man page is found for the identifier, then the man page is displayed. SECONDARY Jumps to the next tag matching an identifier at point. When pressed on a Lisp symbol within a Lisp code buffer: PRIMARY Jumps to the definition of any selected Lisp construct. If on an Emacs Lisp require, load, or autoload clause and 'find-library' from load-library package by Hallvard Furuseth has been loaded, jumps to library source, if possible. SECONDARY Jumps to the next tag matching an identifier at point or if using the "wtags" package and identifier is an Emacs Lisp symbol, then displays documentation for the symbol. When the OO-Browser has been loaded and the press is within a C++ buffer: PRIMARY or SECONDARY Jumps to the definition of selected C++ construct via OO-Browser support. (1) on a '#include' statement, the include file is displayed; (2) within a method declaration, its definition is displayed; (3) on a class name, the class definition is shown. When pressed within an occur-mode or moccur-mode buffer: PRIMARY or SECONDARY Jumps to the source buffer and line of the current occurrence. When pressed within a calendar-mode buffer: PRIMARY (1) at the end of the buffer, the calendar is scrolled forward 3 months; (2) to the left of any dates on a calendar line, the calendar is scrolled backward 3 months; (3) on a date, the diary entries for the date, if any, are displayed. SECONDARY (1) at the end of the buffer, the calendar is scrolled backward 3 months; (2) to the left of any dates on a calendar line, the calendar is scrolled forward 3 months; (3) anywhere else, all dates with marking diary entries are marked in the calendar window. When pressed within a man page apropos buffer: PRIMARY (1) on a UNIX man apropos entry, the man page for that entry is displayed in another window; (2) on or after the last line, the buffer in the other window is scrolled up one screen. SECONDARY (1) on a UNIX man apropos entry, the man page for that entry is displayed in another window; (2) on or after the last line, the buffer in the other window is scrolled down one screen. If Smart Menu package has been loaded and 'smart-key-always-display-menu' is non-nil: PRIMARY or SECONDARY Pops up a window with a Smart Menu of commands. Menu displayed is selected by (smart-menu-choose-menu). If pressed within an outline-mode buffer or when 'selective-display' is non-nil: PRIMARY Collapses, expands, and moves outline entries. (1) after an outline heading has been cut via the smart-key, then paste the cut heading at point; (2) at the end of buffer, show all buffer text (3) at the beginning of a heading line, cut the headings subtree from the buffer; (4) on a header line but not at the beginning or end, if headings subtree is hidden then show it, otherwise hide it; (5) anywhere else, scroll up one screen. SECONDARY (1) after an outline heading has been cut via the smart-key, allow multiple pastes throughout the buffer (last paste should be done with smart key, not meta smart key); (2) at the end of buffer, hide all bodies in buffer; (3) at the beginning of a heading line, cut the current heading (sans subtree) from the buffer; (4) on a header line but not at the beginning or end, if heading body is hidden then show it, otherwise hide it; (5) anywhere else, scroll down one screen. If pressed within an Info manual node: PRIMARY (1) the first line of an Info Menu Entry or Cross Reference, the desired node is found; (2) the Up,Next,or Previous entries of a Node Header (first line), the desired node is found; (3) the File entry of a Node Header (first line), the 'Top' node within that file is found; (4) at the end of the current node, the Next node is found (this will descend subtrees if the function 'Info-global-next' is bound); (5) anywhere else (e.g. at the end of a line), the current node entry is scrolled up one screen SECONDARY (1) the first line of an Info Menu Entry or Cross Reference, the desired node is found; (2) the Up,Next,or Previous entries of a Node Header (first line), the last node in the history list is found; (3) the File entry of a Node Header (first line), the 'DIR' root-level node is found; (4) at the end of the current node, the Previous node is found (this will return from subtrees if the function 'Info-global-prev is bound); (5) anywhere else (e.g. at the end of a line), the current node entry is scrolled down one screen If pressed within a Hyperbole-supported mail reader, 'hmail:reader', or mail summary mode, 'hmail:lister', buffer at: PRIMARY (1) a msg buffer, within the first line or at the end of a message, the next undeleted message is displayed; (2) a msg buffer within the first line of an Info cross reference, the reference is followed; (3) anywhere else in a msg buffer, the window is scrolled up one screen; (4) a msg summary buffer on a header entry, the message corresponding to the header is displayed in the msg window; (5) a msg summary buffer, on or after the last line, the messages marked for deletion are expunged. SECONDARY (1) a msg buffer, within the first line or at the end of a message, the previous undeleted message is displayed; (2) a msg buffer within the first line of an Info cross reference, the reference is followed; (3) anywhere else in a msg buffer, the window is scrolled down one screen; (4) a msg summary buffer on a header entry, the message corresponding to the header is marked as deleted; (5) a msg summary buffer, on or after the last line, all messages are marked undeleted. If pressed within a GNUS listing of newsgroups buffer at: PRIMARY (1) a GNUS-GROUP line, that newsgroup is read; (2) to the left of any GNUS-GROUP line, on any of the whitespace, the current group is unsubscribed or resubscribed; (3) at the end of the GNUS-GROUP buffer, after all lines, checks for new news. SECONDARY (1) a GNUS-GROUP line, that newsgroup is read; (2) to the left of any GNUS-GROUP line, on any of the whitespace, the user is prompted for a group name to subscribe or unsubscribe to; (3) at the end of the GNUS-GROUP buffer, after all lines, quits from the newsreader. If pressed within a GNUS newsreader subject listing buffer at: PRIMARY (1) a GNUS-SUBJECT line, that article is read, marked deleted, and scrolled forward; (2) at the end of the GNUS-SUBJECT buffer, the next undeleted article is read or the next group is entered. SECONDARY (1) a GNUS-SUBJECT line, that article is read and scrolled backward; (2) at the end of the GNUS-SUBJECT buffer, the subject is exited, the user is returned to group mode. If pressed within a GNUS newsreader article buffer at: PRIMARY (1) the first line or end of an article, the next unread message is displayed; (2) the first line of an Info cross reference, the reference is followed; (3) anywhere else, the window is scrolled up one screen. SECONDARY (1) the first line or end of an article, the previous message is displayed; (2) the first line of an Info cross reference, the reference is followed; (3) anywhere else, the window is scrolled down one screen. If pressed within a listing of buffers (Buffer-menu-mode): PRIMARY (1) on the first column of an entry, the selected buffer is marked for display; (2) on the second column of an entry, the selected buffer is marked to be saved; (3) anywhere else within an entry line, all saves and deletes are done, and selected buffers are displayed, including the one just clicked on (if in the OO-Browser, only the selected buffer is displayed); (4) on or after the last line in the buffer, all saves and deletes are done. SECONDARY (1) on the first or second column of an entry, the selected buffer is unmarked for display and for saving or deletion; (2) anywhere else within an entry line, the selected buffer is marked for deletion; (3) on or after the last line in the buffer, all display, save, and delete marks on all entries are undone. If pressed within a dired-mode buffer: PRIMARY (1) within an entry line, the selected buffer is displayed for viewing; (2) on or after the last line in the buffer, if any deletes are to be performed, they are executed after user verification, otherwise, this dired invocation is quit. SECONDARY (1) on a '~' character, all backup files in the directory are marked for deletion; (2) on a '#' character, all auto-save files in the directory are marked for deletion; (3) anywhere else within an entry line, the selected buffer is marked for deletion; (4) on or after the last line in the buffer, all delete marks on all entries are undone. If pressed with a buffer in View mode: PRIMARY Scrolls buffer forward a windowful. SECONDARY Scrolls buffer backward a windowful. If pressed on a cross reference within a man page entry section labeled NAME, SEE ALSO, or PACKAGES USED, or within a man page C routine specification (see 'smart-man-c-routine-ref') and man page buffer has either an attached file or else a `man-path' local variable containing its pathname: PRIMARY or SECONDARY Displays man page or code source for cross reference. If pressed within the wrolo match display buffer: PRIMARY (1) At the start of a rolodex match entry, the entry is edited in the other window; (2) anywhere else within an entry line, toggles between displaying only the selected rolodex item and displaying all matches. SECONDARY (1) At the start of a rolodex match entry, the entry is edited in the other window; (2) anywhere else within an entry line, toggles between displaying only the selected rolodex item and displaying all matches.  File: hypb.info, Node: Suggestion or Bug Reporting, Next: Questions and Answers, Prev: Smart Key Reference, Up: Top Suggestion or Bug Reporting *************************** See the `README' file in the Hyperbole distribution directory for complete details on Hyperbole mailing lists and how to subscribe. If you find any errors in Hyperbole's operation or documentation, feel free to report them to the Hyperbole discussion list: hyperbole@cs.brown.edu. Be sure to use the Msg/Compose-Hypb-Mail menu item whenever you send a message to the mail list since it will insert important system version information for you. If you use Hyperbole mail or news support, *note Buttons in Mail::., a click with your primary Smart Key on the Hyperbole mail list address will insert a description of your Hyperbole configuration information into your outgoing message, so that you do not have to type it. This is useful when composing a reply for the Hyperbole mail list. Otherwise, be sure to include your Emacs, Hyperbole and window system versions in your message. Your Hyperbole version number can be found in the top-level Hyperbole menu. Please use your subject line to state the position that your message takes on the topic that it addresses, e.g. send "Subject: Basic bug in top-level Hyperbole menu." rather than "Subject: Hyperbole bug". This simple rule makes all e-mail communication much easier. If you have suggestions on how to improve Hyperbole, send them to the same address. Here are some issues you might address: * What did you like and dislike about the system? * What kinds of tasks, if any, does it seem to help you with? * What did you think of the Emacs-based user interface? * How was the Hyperbole Manual and other documentation? * Was the setup trivial, average or hard? * What areas of Hyperbole would you like to see expanded/added? * How does it compare to other hypertext tools you have used? * Was it easy or difficult to create your own types? Why? * Did you get any use out of the external system encapsulations?  File: hypb.info, Node: Questions and Answers, Next: Ongoing Work, Prev: Suggestion or Bug Reporting, Up: Top Questions and Answers ********************* *How can I change the Smart Mouse Key bindings?* Since the Smart Mouse Keys are set up for use under five different Emacs configurations, there is no easy way to provide user level customization. Therefore, to change the bindings you must edit the `sm-mouse-setup' and `sm-mouse-get-bindings' functions in the `hmouse-key.el' file. The SMART-KEY-ALIST and SMART-KEY-MOUSE-ALIST variable settings in `hui-mouse.el' and `hui-window.el' must be altered if you want to change what the Smart Keys do in particular contexts. You should then update the Smart Key summary documentation in the file, `hmouse-doc.txt', and potentially the same summary in this manual. *Missing Action Types* What if someone sends a mail message with a button for which I do not have the action type? Or a button whose link referent I can't access? You receive an error that an action type is not defined or a link referent is not accessible/readable if you try to use the button. This is hardly different than trying to get through a locked door without a key; you try the doorknob, find that it is locked, and then realize that you need to take a different approach or else give up. Like all communication, people need to coordinate, which usually requires an iterative process. If you get a mail message with a button for which you don't have the action type, you mail the sender and request it. *How can I modify a number of global buttons in succession?* Rather than typing the name for each, it is quicker to jump to the global button file and edit the buttons there as you would any explicit buttons. By default, the ButFile/PersonalFile menu item takes you to the file where global buttons are saved. *Why is all the button data scattered across directories?* When you think of a hyper-space that you depend on every day, you don't want to have a single point of failure make you incapable of doing work. With Hyperbole, if some directories become unavailable for a particular time (e.g. the filesystems on which they reside are dismounted) you can still work elsewhere with minimal effect. We believe this to be a compelling factor to leave the design with external button data storage. This design also permits the potential addition of buttons to read-only media. *Why are action types defined separately from their implicit button types?* Any category of button can make use of an action type. Some action types are useful as behavior definitions for a variety of button categories, so all action types are defined separately to give them independence from those types which apply them. For implicit button types that require a lot of code, it is useful to add a module that includes the implicit button type definition, its action type definition and supporting code.  File: hypb.info, Node: Ongoing Work, Next: References, Prev: Questions and Answers, Up: Top Ongoing Work ************ This appendix is included for a number of reasons: * to better allow you to assess whether to work with Hyperbole by providing sketches of possible additions (only minimal work is done on Hyperbole at the present time, however); * to direct further development effort towards known needs; * and to acknowledge known weaknesses in the current system. Note that due to a lack of volunteers to further develop Hyperbole, much of this work may not be done. So if you want to see these features, encourage qualified people to volunteer. Button Copying, Killing, and Yanking There is as yet no means of transferring buttons among buffers. We realize this is a critical need. Users should be able to manipulate text with embedded buttons in ordinary ways. Some of the Emacs Lisp functions that must be augmented to support this behavior include: (append-next-kill) (copy-region-as-kill) (delete-region) ;; a built-in function (get-register) (insert-buffer-substring) ;; a built-in function (insert-file-contents) (kill-append) (kill-region) (rotate-yank-pointer) (set-register) (view-register) (yank) (yank-pop) (undo) Hyperbole Views These will permit rapid perspective shifting when studying and manipulating bodies of text. They will also allow fine control over the presentation of information displayed by action types. Trails Trails are an extension to the basic history mechanism presently offered by Hyperbole. Trails will allow a user to capture, edit and store a specific sequence and set of views of information for later replay by other users. Conditional branching may also be supported. Storage of button data within button source files. The current design choice of storing buttons external to the source file was made under the assumption that people should be able to look at files that contain Hyperbole buttons with any standard editor or tool and not be bothered by the ugly button data (since they won't be able to utilize the buttons anyway, they don't need to see or have access to them). In many contexts, embedding the button data within the source files may be a better choice, so a provision which would allow selection of either configuration may be added. Here are some of the PROs and CONs of both design choices: POSITIVE NEGATIVE Bdata in src file Documents can stand alone. All edit operators have Normal file operations apply. to account for file structure and hide Simplifies creation and internal components. facility expansion for structured and multi-media files. Bdata external to src file Files can be displayed and Currently, bdata for printed exactly as they look. whole directory is No special display formatting locked when any bdata is necessary. entry is locked. Button-based searches and database-type lookup operations need only search one file per directory. NLS/AUGMENT-type File Structuring Being Investigated NLS/AUGMENT treated files as a hierarchical set of nodes, for example, each paragraph would be treated as a node, with its own address. This would aid greatly in idea structuring and cross-referencing. Don't expect anything soon on this front, but keep in mind that we are interested in hearing about any recent related work. Forms-based Interfaces This will allow one to create buttons more flexibly. For example, button attributes could be given in any order. Entry of long code sequences, quick note taking and cross-referencing would also be made easier. Collaboration Support From the early stages of Hyperbole design, collaborative work environments have been considered. A simple facility has demonstrated broadcast of button activations to a number of workstations on a local area network, so that one user can lead others around an information space, as during an online design review. (This facility is not yet ready for release.) We shall do some work in specific collaborative mechanisms, but also expect that others who concentrate in collaborative work will provide more extensive capabilities.  File: hypb.info, Node: References, Next: Key Binding Index, Prev: Ongoing Work, Up: Top References ********** [AkMcYo88] Akscyn, R. M., D. L. McCracken and E. A. Yoder. KMS: A Distributed Hypermedia System for Managing Knowledge in Organizations. *Communications of the ACM*, Vol. 31, No. 7, July 1988, pp. 820-835. [Bro87] Brown, P. J. Turning Ideas into Products: The Guide System. *Proceedings of Hypertext '87*, November 13-15, 1987, Chapel Hill, NC. ACM: NY, NY, pp. 33-40. [Con87] Conklin, Jeff. Hypertext: An Introduction and Survey. *IEEE Computer*, Vol. 20, No. 9, September 1987, pp. 17-41. [Eng68] Engelbart, D., and W. English. A research center for augmenting human intellect. *Proceedings of the Fall Joint Computer Conference*, 33, 1, AFIPS Press: Montvale, NJ, 1968, pp. 395-410. [Eng84a] Engelbart, D. C. Authorship Provisions in Augment. *Proceedings of the 1984 COMPCON Conference (COMPCON '84 Digest)*, February 27-March 1, 1984, San Francisco, CA. IEEE Computer Society Press, Spring, 1984. 465-472. (OAD,2250,) [Eng84b] Engelbart, D. C. Collaboration Support Provisions in Augment. *Proceedings of the AFIPS Office Automation Conference (OAC '84 Digest)*, February, 1984, Los Angeles, CA, 1984. 51-58. (OAD,2221,) [Fos88] Foss, C. L. Effective Browsing in Hypertext Systems. *Proceedings of the Conference on User-Oriented Content-Based Text and Image Handling (RIAO 88)*, March 21-24, MIT, Cambridge MA. Centre de Hautes Etudes Internationales d'Informatique Documentaire, 1988, pp. 82-98. [GaSmMe86] Garrett, N., K. E. Smith and N. Meyrowitz. Intermedia: Issues, Strategies, and Tactics in the Design of a Hypermedia Document System. *Computer-Supported Cooperative Work (CSCW '86) Proceedings*, December 3-5, Austin, TX, 1986, pp. 163-174. [HaMoTr87] Halasz, F. G., T. P. Moran and R. H. Trigg. NoteCards in a Nutshell. *Proceedings of the CHI and GI '87 Conference on Human Factors in Computing Systems*, Toronto, J. M. Carroll and P. P. Tanner, (editors), ACM: NY, NY, April 1987, pp. 45-52. [Har88] Harvey, G. *Understanding HyperCard.* Alameda, CA: SYBEX, Inc., 1988. [KaCaLoLa92] Kaplan, S., A. M. Carroll, C. Love and D. M. LaLiberte. *Epoch 4.0 Manual.* Department of Computer Science, University of Illinois, Urbana-Champaign, March 1992. [KaKaBeLaDr90] Kaplan, S. J., M. D. Kapor, E. J. Belove, R. A. Landsman, and T. R. Drake. AGENDA: A personal Information Manager. *Communications of the ACM*, No. 33, July 1990, pp. 105-116. [Nel87a] Nelson, T. H. *Computer Lib/Dream Machines.* MicroSoft Press, Redmond, WA, 1987. [Nel87b] Nelson, T. H. *Literary Machines, Edition 87.1*. Available from the Distributors, 702 South Michigan, South Bend, IN 46618, 1987. [NoDr86] Norman, D. A. and S. W. Draper, editors. *User Centered System Design.* Lawrence Erlbaum Associates: Hillsdale, New Jersey, 1986. [Shn82] Shneiderman, B. The future of interactive systems and the emergence of direct manipulation. *Behavior and Information Technology*, Vol. 1, 1982, pp. 237-256. [Sta87] Stallman, R. *GNU Emacs Manual.* Free Software Foundation, Cambridge: MA, March 1987. [Tri86] Trigg, R., L. Suchman, and F. Halasz. Supporting collaboration in NoteCards. *Proceedings of the CSCW '86 Conference*, Austin, TX, December 1986, pp. 147-153. [TrMoHa87] Trigg, R. H., T. P. Moran and F. G. Halasz. Adaptability and Tailorability in NoteCards. *Proceedings of INTERACT '87*, Stuttgart, West Germany, September 1987. [Wei92] Weiner, B. *PIEmail: A Personalized Information Environment Mail Tool.* Department of Computer Science Masters Project, Brown University: Providence, RI, May 10, 1992. [YaHaMeDr88] Yankelovich, N., B. J. Haan, N. Meyrowitz and S. M. Drucker. Intermedia: The Concept and the Construction of a Seamless Information Environment. *IEEE Computer*, Vol. 21, No. 1, January 1988, pp. 81-96. [YoAkMc89] Yoder, E. A., R. M. Akscyn and D. L. McCracken. Collaboration in KMS, A Shared Hypermedia System. *Proceedings of the 1989 ACM Conference on Human Factors in Computer Systems (CHI '89)*, April 30-May 4, 1989, Austin, TX, ACM: NY,NY, 1989, pp. 37-42.  File: hypb.info, Node: Key Binding Index, Next: Code and File Index, Prev: References, Up: Top Key Binding Index ***************** * Menu: * C-M-x: Creating Types. * C-c C-r: Renaming. * C-c C-y: Buttons in Mail. * C-c t: Smart Keys. * C-g: Operating Menus. * C-h S: Smart Keys. * C-h h: Operating Menus. * C-h t: Top. * C-t: Operating Menus. * C-u M-RET: Smart Keys. * C-x 4 DEL: Screen Configurations. * C-x 4 w: Screen Configurations. * C-x 4 y: Screen Configurations. * C-x C-e: Creating Types. * C-x m: Buttons in Mail. * M-RET: Smart Keys. * q: Operating Menus.  File: hypb.info, Node: Code and File Index, Next: Concept Index, Prev: Key Binding Index, Up: Top Code and File Index ******************* * Menu: * action:act-hook: Hook Variables. * actype:create: Action Types. * actype:create: Action Types. * actype:delete: Action Types. * class, ebut: Programmatic Button Creation. * class, ebut: Operational and Storage Formats. * class, hargs: Action Types. * class, hattr: Implicit Button Types. * class, hbdata: Operational and Storage Formats. * class, hbut: Implicit Button Types. * class, hbut: Operational and Storage Formats. * class, htype: Creating Types. * defact: Action Types. * defib: Implicit Button Types. * dir, ~/.hyperb: Button Files. * ebut:create: Programmatic Button Creation. * ebut:create-hook: Hook Variables. * ebut:delete-hook: Hook Variables. * ebut:map: Programmatic Button Creation. * ebut:modify-hook: Hook Variables. * ep:cycle-but-color: Initializing. * eval-defun: Creating Types. * eval-last-sexp: Creating Types. * file, .hypb: Explicit Buttons. * file, .~/.emacs: Renaming. * file, DEMO: Top. * file, HYPB: Operating Menus. * file, README: Initializing. * file, README: Suggestion or Bug Reporting. * file, hactypes.el: Creating Types. * file, hactypes.el: Action Types. * file, hbut.el: Programmatic Button Creation. * file, hbut.el: Action Types. * file, hgnus.el: Buttons in News. * file, hib-kbd.el: Implicit Button Types. * file, hibtypes.el: Implicit Buttons and Types. * file, hibtypes.el: Creating Types. * file, hmail.el: Buttons in Mail. * file, hmouse-key.el: Questions and Answers. * file, hmouse-key.el: Questions and Answers. * file, hsite.el: Initializing. * file, hsite.el: Initializing. * file, hsite.el: Buttons in News. * file, hsite.el: Renaming. * file, hsite.el: Smart Keys. * file, hsys-*: Encapsulating Systems. * file, hui-ep*.el: Initializing. * file, hui-window.el: Questions and Answers. * file, wconfig.el: Screen Configurations. * file, wrolo.el: Rolodex. * file, ~/.emacs: Initializing. * file, ~/.emacs: Smart Keys. * file, ~/.emacs: Buttons in Mail. * fill-prefix: Operational and Storage Formats. * find-file-hooks: Hook Variables. * gbut:file: Glossary. * hbmap:dir-user: Button Files. * hbmap:filename: Button Files. * hbut:current: Operational and Storage Formats. * hbut:current: Hook Variables. * hbut:fill-prefix-regexps: Operational and Storage Formats. * hbut:label-to-key: Operational and Storage Formats. * hibtypes:begin-load-hook: Hook Variables. * hibtypes:end-load-hook: Hook Variables. * htype:create-hook: Hook Variables. * htype:delete-hook: Hook Variables. * hui:ebut-delete-confirm-p: Deletion. * hui:ebut-prompt-for-action: Action Types and Actions. * hyperb:init-hook: Hook Variables. * ibtype:create: Implicit Button Types. * ibtype:delete: Implicit Button Types. * ibut:at-p: Implicit Button Types. * interactive: Action Types. * kill-ring: Screen Configurations. * mail: Buttons in Mail. * mail-yank-original: Buttons in Mail. * rolo-email-format: Rolo Settings. * rolo-entry-regexp: Rolo Settings. * rolo-file-list: Rolo Settings. * rolo-hdr-regexp: Rolo Settings. * rolo-kill-buffers-after-use: Rolo Settings. * rolo-save-buffers-after-use: Rolo Settings. * run-hooks: Glossary. * sm-mouse-get-bindings: Questions and Answers. * sm-mouse-setup: Questions and Answers. * smail:comment: Buttons in Mail. * smart-key-alist: Questions and Answers. * smart-key-init: Smart Keys. * smart-key-init: Smart Keys. * smart-key-mouse-alist: Questions and Answers. * wconfig-delete-pop: Screen Configurations. * wconfig-ring-max: Screen Configurations. * wconfig-ring-save: Screen Configurations. * wconfig-yank-pop: Screen Configurations. * write-file-hooks: Hook Variables.