On Wed, Mar 22, 2023 at 12:00:00AM +0100, Patrice Dumas wrote:
> On Tue, Mar 21, 2023 at 02:20:41PM +, Werner LEMBERG wrote:
> >
> > (1) Introduce something like my suggested `@set txiindexinpara`.
> > (2) In version 7.1, make `@set txiindexinpara off` the default.
> > (3) In version 7.1, anno
On Tue, Mar 21, 2023 at 02:20:41PM +, Werner LEMBERG wrote:
>
> (1) Introduce something like my suggested `@set txiindexinpara`.
> (2) In version 7.1, make `@set txiindexinpara off` the default.
> (3) In version 7.1, announce that you are going to change the
> behaviour of `@XXindex` in 7.
On Tue, Mar 21, 2023 at 07:11:52AM +, Gavin Smith wrote:
> On Tue, Mar 21, 2023 at 04:04:49AM +, Werner LEMBERG wrote:
> > What about introducing a new flag, something like
> >
> > ```
> > @set txiindexinpara
> > ```
> >
> > that restores the previous behaviour? At least on the `texinfo.
>> What about introducing a new flag, something like
>>
>> ```
>> @set txiindexinpara
>> ```
>>
>> that restores the previous behaviour? At least on the `texinfo.tex`
>> side this shouldn't be too difficult. However, I have no idea about
>> `makeinfo` and `texi2any`...
>
> I've reverted the
Hello.
As suggested by Gavin, I'm reporting a problem (or at least a
"surprising inconsistency") in the texi2dvi script. This is related to
Automake bug#29188 (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29188).
Since texinfo-4.9, one can set the build directory with an
environment varia
On Tue, Mar 21, 2023 at 04:04:49AM +, Werner LEMBERG wrote:
> What about introducing a new flag, something like
>
> ```
> @set txiindexinpara
> ```
>
> that restores the previous behaviour? At least on the `texinfo.tex`
> side this shouldn't be too difficult. However, I have no idea about
>