783 |
(info-lookup-maybe-add-help |
(info-lookup-maybe-add-help |
784 |
:mode 'octave-mode |
:mode 'octave-mode |
785 |
:regexp "[_a-zA-Z0-9]+" |
:regexp "[_a-zA-Z0-9]+" |
786 |
:doc-spec '(("(octave)Function Index" nil |
:doc-spec '(("(octave)Function Index" nil |
787 |
"^ - [^:]+:[ ]+\\(\\[[^=]*=[ ]+\\)?" nil) |
"^ - [^:]+:[ ]+\\(\\[[^=]*=[ ]+\\)?" nil) |
788 |
("(octave)Variable Index" nil "^ - [^:]+:[ ]+" nil) |
("(octave)Variable Index" nil "^ - [^:]+:[ ]+" nil) |
789 |
;; Catch lines of the form "xyz statement" |
;; Catch lines of the form "xyz statement" |
797 |
nil))) |
nil))) |
798 |
|
|
799 |
;; coreutils and bash builtins overlap in places, eg. printf, so there's a |
;; coreutils and bash builtins overlap in places, eg. printf, so there's a |
800 |
;; question which should come first. Some of the sh-utils descriptions are |
;; question which should come first. Some of the coreutils descriptions are |
801 |
;; more detailed, but if bash is usually /bin/sh on a GNU system then the |
;; more detailed, but if bash is usually /bin/sh on a GNU system then the |
802 |
;; builtins will be what's normally run. |
;; builtins will be what's normally run. |
803 |
;; |
;; |