On 10 October 2015 at 08:06, Eli Zaretskii wrote:
>
> So I guess we should have an option to enable/disable this feature,
> since "one size fits all" clearly doesn't work here?
>
I see there is already an undocumented option to ignore left quotes
(introduced for the 2nd edition of "Free Software,
On 10 October 2015 at 08:06, Eli Zaretskii wrote:
>> Date: Fri, 9 Oct 2015 21:51:31 GMT
>> From: Karl Berry
>>
>> Wrt the general point: as far as I can imagine, the (vast) majority of
>> manuals indexing \ sequences would be for C-style \n, \r, etc. As a
>> reader, I would certainly expect thos
> Date: Fri, 9 Oct 2015 21:51:31 GMT
> From: Karl Berry
>
> Wrt the general point: as far as I can imagine, the (vast) majority of
> manuals indexing \ sequences would be for C-style \n, \r, etc. As a
> reader, I would certainly expect those to be indexed under \.
>
> Wrt \mathopsup: since \ is
> Date: Fri, 9 Oct 2015 16:39:14 +0100
> From: Gavin Smith
> Cc: Texinfo
>
> On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> > So perhaps we should introduce a facility for such tests, and
> > preferably in a way that is itself backward-compatible, e.g., testable
> > with @ifset or some such
> Date: Thu, 8 Oct 2015 21:08:11 +0100
> From: Gavin Smith
> Cc: Texinfo
>
> There is a new syntax for specifying an explicit sort key that was
> introduced after the Texinfo 6.0 release. It looks like
>
> @cindex @sortas{\ escape sequence} \ (backslash), escape sequence
>
> Here "\ (backslash
On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> So perhaps we should introduce a facility for such tests, and
> preferably in a way that is itself backward-compatible, e.g., testable
> with @ifset or some such.
It already exists. See (texinfo)Testing for Texinfo Commands:
These
and the < sign?
Thanks,
Arnold
> Date: Thu, 8 Oct 2015 21:08:11 +0100
> Subject: Re: texinfo 6.0 texindex problem?
> From: Gavin Smith
> To: Aharon Robbins
> Cc: Texinfo
>
> On 8 October 2015 at 20:06, Aharon Robbins wrote:
> > Hi.
> >
> > I add
> many manuals have indexed items starting with a backslash that are
> better indexed under a letter following the backslash (an example from
> Texinfo's manual is \mathopsup, better indexed under "M").
I suppose this decision is already made, but I feel compelled to kibitz,
sorry: it
On 2015-10-09 02:06, Eli Zaretskii wrote:
Btw, my usual problem with such new features is that it's impossible
(AFAIK) to use them in a manual in a backward-compatible way,
i.e. while making sure older versions of makeinfo will process the
manual without errors. That's because there's no way (ag
> Date: Fri, 9 Oct 2015 11:48:44 +0100
> From: Gavin Smith
> Cc: Aharon Robbins , Texinfo
>
> On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> > Btw, my usual problem with such new features is that it's impossible
> > (AFAIK) to use them in a manual in a backward-compatible way,
> > i.e. whil
On 9 October 2015 at 08:00, Aharon Robbins wrote:
> Hi. THanks for the mail. I moved to current development code for
> texindex and braces are working. I note that hyphens and < signs
> also get removed from the key for the index. Is that on purpose?
>
> I can go ahead and add @sortas, but I'm w
On 9 October 2015 at 08:06, Eli Zaretskii wrote:
> Btw, my usual problem with such new features is that it's impossible
> (AFAIK) to use them in a manual in a backward-compatible way,
> i.e. while making sure older versions of makeinfo will process the
> manual without errors. That's because ther
On 8 October 2015 at 20:06, Aharon Robbins wrote:
> Hi.
>
> I added
>
> @tex
> \global\usebracesinindexestrue
> @end tex
>
> to gawktexi.in in the gawk dist and built a pdf with the tools from
> texinfo 6.0. Something's weird. First, there is no initial for \.
> Second, braces come out under bac
13 matches
Mail list logo
