[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Location of contents for HTML

From: Gavin Smith
Subject: Re: Location of contents for HTML
Date: Sun, 15 Nov 2020 11:39:21 +0000
User-agent: Mutt/1.9.4 (2018-02-28)

On Mon, Nov 09, 2020 at 10:18:58PM +0100, Patrice Dumas wrote:
> What about replacing INLINE_CONTENTS by a customization variable for all
> the contents locations possibilities, for example
> which could take value
>  inline or at_commands (INLINE_CONTENTS=1)
>  separate_or_end (current INLINE_CONTENTS=0 case, separate if split, at
>                   end otherwise)
>  after_top (the new option you propose which would become the default)
>  before_top (after title)
> and there could be too
>  separate
>  end

I see you implemented this.  I suggest a few changes:

or just CONTENTS_LOCATION (both noun phrases).  OUTPUT_CONTENTS is
another possibility (an imperative clause like FORMAT_MENU), or
CONTENTS_OUTPUT (viewing "output" as a noun rather than a verb).

Use "inline" instead of "at_commands" (not clear whether the latter means
output the menu "at" where the commands were given, or if it means commands
starting with the at sign @ (i.e. all Texinfo commands)).

I should be able to easily make these changes myself, which I will do
unless there are further suggestions.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]