>> > ... 'menu_no_detailmenu' sounds good to me.
>>
>> Sounds good to me too.
>
> I will implement then. It will apply to Info output too.
+1, and thanks.
Werner
On Mon, Feb 24, 2025 at 10:05:23PM +0100, pertu...@free.fr wrote:
> I will implement then. It will apply to Info output too.
Actually, it won't as for now in Plaintext/Info output code, FORMAT_MENU
is not checked when adding an automatically generated menu. That could
be changed, but not for the
On Mon, Feb 24, 2025 at 08:52:15PM +, Gavin Smith wrote:
> On Mon, Feb 24, 2025 at 05:28:19PM +, Werner LEMBERG wrote:
> > Given that a detailmenu in Info style looks very un-HTML-ish I think
> > it would be best if `texi2any` didn't generate a detailmenu for HTML
> > output by default if `
On Mon, Feb 24, 2025 at 05:28:19PM +, Werner LEMBERG wrote:
> Given that a detailmenu in Info style looks very un-HTML-ish I think
> it would be best if `texi2any` didn't generate a detailmenu for HTML
> output by default if `FORMAT_MENU` is set to 'menu'. However, such a
> change wouldn't be
On Mon, Feb 24, 2025 at 09:31:16PM +0100, Patrice Dumas wrote:
> On Mon, Feb 24, 2025 at 06:27:39AM +, Werner LEMBERG wrote:
> >
> > I was just bitten by the undocumented feature that `texi2any`
> > generates a `@detailmenu` block if it auto-generates menus, and the
> > top-level menu of a doc
On Mon, Feb 24, 2025 at 07:46:53PM +, Gavin Smith wrote:
> Could we not do the opposite? That is, make an empty @detailmenu block
> *suppress* autogeneration of a detailmenu.
I think that we should not force users to use non sensical Texinfo code
to customize the output.
In that case, in add
On Mon, Feb 24, 2025 at 06:27:39AM +, Werner LEMBERG wrote:
>
> I was just bitten by the undocumented feature that `texi2any`
> generates a `@detailmenu` block if it auto-generates menus, and the
> top-level menu of a document is not present.
>
> Please make this controllable. For example, a
On Mon, Feb 24, 2025 at 06:27:39AM +, Werner LEMBERG wrote:
>
> I was just bitten by the undocumented feature that `texi2any`
> generates a `@detailmenu` block if it auto-generates menus, and the
> top-level menu of a document is not present.
>
> Please make this controllable. For example, a
On Sun, Feb 23, 2025 at 06:17:56PM +0100, Patrice Dumas wrote:
> On Fri, Feb 21, 2025 at 07:32:25PM +, Gavin Smith wrote:
> > I'm not sure that the whole paragraph about a "reference implementation"
> > is particularly relevant either.
>
> Here is a proposal to move that paragraph to the Overv
>> I was just bitten by the undocumented feature that `texi2any`
>> generates a `@detailmenu` block if it auto-generates menus, and the
>> top-level menu of a document is not present.
>
> Is it an issue for you for Info or HTML output format?
HTML.
> In Info, it seems to me that a @detailmenu
On Mon, Feb 24, 2025 at 06:27:39AM +, Werner LEMBERG wrote:
>
> I was just bitten by the undocumented feature that `texi2any`
> generates a `@detailmenu` block if it auto-generates menus, and the
> top-level menu of a document is not present.
Is it an issue for you for Info or HTML output for
11 matches
Mail list logo