Lines Matching defs:descriptions
58 ;; which menu descriptions are indented.
114 ;; Whenever an existing menu is updated, the descriptions from
116 ;; descriptions from the existing menu to the entries in the new menu
118 ;; descriptions are not copied to the new menu.
129 ;; descriptions from pre-existing menus), and then constructs a master
267 Whenever a menu exists, and is being updated, the descriptions that
271 Leaves trailing whitespace in a menu that lacks descriptions, so
272 descriptions will format well. In general, a menu should contain
273 descriptions, because node names and section titles are often too
331 (texinfo-incorporate-descriptions new-menu-list)
343 Indents the first line of descriptions, and leaves trailing whitespace
344 in a menu that lacks descriptions, so descriptions will format well.
345 In general, a menu should contain descriptions, because node names and
364 (let ((end-of-detailed-menu-descriptions
369 (delete-region (point) end-of-detailed-menu-descriptions))))
444 "Make a list of node names and their descriptions.
451 Node names and descriptions are dotted pairs of strings. Each pair is
550 (defun texinfo-incorporate-descriptions (new-menu-list)
551 "Copy the old menu line descriptions that exist to the new menu.
628 ;; don't copy @detailmenu or @end menu or @ignore as descriptions!
630 ;; !! Known bug: does not copy descriptions starting with ^|\{?* etc.
669 "*Column at which descriptions start in a Texinfo menu.")
673 Indents the first line of descriptions, if any, to the value of
675 in a menu that lacks descriptions, so descriptions will format well.
676 In general, a menu should contain descriptions, because node names and
718 ;;; Starting menu descriptions by inserting titles
804 ;; Since the make-menu functions indent descriptions, these functions
814 "nIndent menu descriptions to (column number): \nP")
823 "Indented descriptions in menu. You may save the buffer."))
873 menus in the buffer (incorporating descriptions from pre-existing
896 Indents the first line of descriptions, and leaves trailing whitespace
897 in a menu that lacks descriptions, so descriptions will format well.
898 In general, a menu should contain descriptions, because node names and
924 (let ((end-of-detailed-menu-descriptions
929 (delete-region (point) end-of-detailed-menu-descriptions)))))
1108 ;; copy multi-line descriptions
1253 which menu descriptions are indented. Its default value is 32."
2022 (texinfo-incorporate-descriptions main-menu-list)
2049 (let ((end-of-detailed-menu-descriptions
2054 (delete-region (point) end-of-detailed-menu-descriptions))))