@ifset at Line Beginning and @menu after sectioning calls
Dear Compeers, Customarily the texinfo structures for my manuals get quite complicated. Consequently, I point out two things. 1. @ifset @ifclear have only appear at a line beginning 2. @menu cannot occur after every sectioning label @section @subsection @heading @unnumbered Comments: 1. @ifset should allow indentation like many other commands 2. A menu should be allowed to display itself after section commands In my intro file I have added a menu after @chapter and before the first @section I put the menu in a macro, then I simply call the macro @Gela-. --- Top Level File: 00-gungadin-elisp-abbrev \input texinfo etc @menu * Introduction:: Introduction to Emacs Lisp. @detailmenu Subnodes so you can view them easily in one step: Introduction * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end detailmenu @end menu @ifset Volume-1 @include 01-gela-intro.texi @end ifset @bye --- Intro File: 01-gela-intro.texi @macro Gela-Menu @menu * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end menu @end macro @node Introduction @chapter Introduction Introduction Text @chapter CTitle @section First Section @Gela-Menu @subsection First SubSection @section Second Section @Gela-Menu Regards Christopher
@ifset at Line Beginning and @menu after sectioning calls
Continuing some more regarding @menu. Normally, when you view an info file, the first line shows where you are located For instance (gungadin-elisp-abbrev)Top > Introduction > Modifier Keys It is great and I love it. It would be better still if this is also displayed at the bottom after one has finished scrolling down. With this additional thing reading would be super. Regards C* Dear Compeers, Customarily the texinfo structures for my manuals get quite complicated. Consequently, I point out two things. 1. @ifset @ifclear have only appear at a line beginning 2. @menu cannot occur after every sectioning label @section @subsection @heading @unnumbered Comments: 1. @ifset should allow indentation like many other commands 2. A menu should be allowed to display itself after section commands In my intro file I have added a menu after @chapter and before the first @section I put the menu in a macro, then I simply call the macro @Gela-. --- Top Level File: 00-gungadin-elisp-abbrev \input texinfo etc @menu * Introduction:: Introduction to Emacs Lisp. @detailmenu Subnodes so you can view them easily in one step: Introduction * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end detailmenu @end menu @ifset Volume-1 @include 01-gela-intro.texi @end ifset @bye --- Intro File: 01-gela-intro.texi @macro Gela-Menu @menu * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end menu @end macro @node Introduction @chapter Introduction Introduction Text @chapter CTitle @section First Section @Gela-Menu @subsection First SubSection @section Second Section @Gela-Menu Regards Christopher
Re: @ifset at Line Beginning and @menu after sectioning calls
On Fri, Oct 16, 2020 at 06:49:22PM +0200, Christopher Dimech wrote: > > > > Continuing some more regarding @menu. > > Normally, when you view an info file, the first line shows where you are > located > > For instance > > (gungadin-elisp-abbrev)Top > Introduction > Modifier Keys > > It is great and I love it. It would be better still if this is also > displayed at the bottom > after one has finished scrolling down. With this additional thing reading > would be super. > > Regards > C* This is an Emacs question which you should send to help-gnu-em...@gnu.org.
Re: @ifset at Line Beginning and @menu after sectioning calls
(It's awkward for me to receive HTML emails, could you configure your mail program to send plain text instead?) On Fri, Oct 16, 2020 at 02:39:14PM +0200, Christopher Dimech wrote: > > > Dear Compeers, > > > > Customarily the texinfo structures for my manuals get quite > complicated. > > Consequently, I point out two things. > > > > > > 1. @ifset @ifclear have only appear at a line beginning What is the problem with this? > > 2. @menu cannot occur after every sectioning label @section @subsection > @heading @unnumbered > > > > > > Comments: > > > > 1. @ifset should allow indentation like many other commands > > > > 2. A menu should be allowed to display itself after section > commands > I'm not sure what the problem is because I had to do edit your email to get input files I could use (e.g. adding "@set Volume-1"). Next time, could you send them as file attachments? Output seemed OK with "texi2any --no-validate test.texi". See attached. test.texi Description: TeXInfo document 01-gela-intro.texi Description: TeXInfo document test.info Description: application/info
