[Top][All Lists]

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

Re: Deprecate Texinfo commands

From: Gavin Smith
Subject: Re: Deprecate Texinfo commands
Date: Wed, 11 Nov 2020 19:05:17 +0000
User-agent: Mutt/1.9.4 (2018-02-28)

On Wed, Nov 11, 2020 at 07:43:56PM +0100, Patrice Dumas wrote:
> On Tue, Nov 10, 2020 at 08:30:15PM +0000, Gavin Smith wrote:
> > On Sun, Nov 08, 2020 at 10:39:02AM +0100, Werner LEMBERG wrote:
> > > > One idea is to change Texinfo to allow @example to have an argument
> > > > which would be output as a 'class' in HTML.  [...]
> > > 
> > > Basically, your suggestions are sound – they kind-of resemble the
> > > markdown extensions introduced by pandoc...
> > 
> > Implemented in commit 758870e30b.  You can give more than one argument
> > to @example separated by spaces, and they will be appended to the
> > class attribute on the <div>.
> I think that the arguments should be separated by commas both for
> consistency and also because we eventually want to allow for spaces in
> arguments.  Also I think that it would be much better if the arguments
> were semantically defined.  The first argument could be the language,
> the second a hint about the size.

Could arbitrarily many arguments be provided?  Are there any other
Texinfo commands which are variadic (separating arguments with commas)?

Maybe there won't be any uses for this feature other than source
language and size, so it won't matter.  I don't like making size part
of the language, though: I thought of this as a hack to be used when
you couldn't avoid it, rather than something to be encouraged.

reply via email to

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