Glad to hear it! Enjoy.
Arnold
Raymond Toy wrote:
> On Sun, May 19, 2019 at 8:44 AM Raymond Toy wrote:
>
> > Thanks for looking into this. I think I'm getting confused on which
> > version of makeinfo and texindex.tex is getting used. (I have 3 version on
> > my system).
> >
>
> Redid this o
On Sun, May 19, 2019 at 8:44 AM Raymond Toy wrote:
> Thanks for looking into this. I think I'm getting confused on which
> version of makeinfo and texindex.tex is getting used. (I have 3 version on
> my system).
>
Redid this on a different system which had just one installed texinfo. I
install
Thanks for looking into this. I think I'm getting confused on which
version of makeinfo and texindex.tex is getting used. (I have 3 version on
my system).
I think the issue I reported here is that I was using pdftex to create the
doc. Using makeinfo --pdf doesn't have that problem. But it compla
On 5/18/19, Raymond Toy wrote:
> With my old hack. With the new texinfo, I changed the macro to say
>
> @cindex \topic\ @subentry \subtopic\
>
> makeinfo --pdf foo.texi
>
> has errors like:
>
> Unde
> fined control sequence.
> \temp ->\xeatspaces {unix} \subentry
>
Hi.
Gavin is the TeXpert, but
> It's easy enough for me to work around this by just globally replacing
> @cpsubindex{foo, bar} with @cindex foo @subentry bar
Doing that is probably your best bet, IMHO.
Arnold
Raymond Toy wrote:
> Found a small issue and I'm not sure of the cause. I can easi
Found a small issue and I'm not sure of the cause. I can easily workaround
this since @subentry works for all output formats that I care about (pdf,
html, info).
Before @subentry was available I used this macro:
@macro cpsubindex {topic,subtopic}
@iftex
@cindex \topic\!\subtopic\
@end iftex
@ifno
On Thu, Mar 07, 2019 at 01:57:08PM -0700, arn...@skeeve.com wrote:
> Gavin Smith wrote:
>
> > On Mon, Mar 04, 2019 at 12:34:42AM -0700, arn...@skeeve.com wrote:
> > > No. As per the mail you discovered, Karl just said "make it work with
> > > both"
> > > so I did. But we're five years later, let
You're welcome. Gavin did most of the work.
I've revised (but not yet merged) the index for the gawk manual to take
advantage of the new features, and it too looks wonderful. I'm pleased
with the new features and am glad other people are using them too.
Regards,
Arnold
Raymond Toy wrote:
> Th
Thanks so much for implementing this! I can get rid of the hacks I had and
make use of it in other docs.
I did use this new version to generate Maxima's manual in pdf. The index
entries and subentries look fine for the most part, but there are a few
oddities. I don't know if I messed up or if i
On Sun, Apr 28, 2019 at 02:33:25AM -0600, arn...@skeeve.com wrote:
> Gavin Smith wrote:
>
> > On Sat, Mar 02, 2019 at 04:33:30PM +, Gavin Smith wrote:
> > > Implemented as @subentry in git commit 372cfab.
> > >
> > > A test file is attached. Please feel free to experiment.
> > >
> > > It st
Gavin Smith wrote:
> On Sat, Mar 02, 2019 at 04:33:30PM +, Gavin Smith wrote:
> > Implemented as @subentry in git commit 372cfab.
> >
> > A test file is attached. Please feel free to experiment.
> >
> > It still needs to be implemented in texi2any, once the syntax is
> > finalised. Voluntee
On Sat, Mar 02, 2019 at 04:33:30PM +, Gavin Smith wrote:
> Implemented as @subentry in git commit 372cfab.
>
> A test file is attached. Please feel free to experiment.
>
> It still needs to be implemented in texi2any, once the syntax is
> finalised. Volunteers are welcome.
I've added some su
Hi.
Gavin Smith wrote:
> I found that text in the number field would have to be surrounded in
> braces, like this:
No problem dealing with that.
> I am not sure about the regex for matching Roman numerals is a good
> idea. There are more features for index formatting that we haven't
> cons
On Thu, Mar 07, 2019 at 01:57:08PM -0700, arn...@skeeve.com wrote:
> OK. No problem. The number field must match /^([ivxdlcm]+|([0-9]+)$/
> to be a number. Otherwise it's a see/see also.
I found that text in the number field would have to be surrounded in
braces, like this:
@entry{bbb}{{see also
On Thu, Mar 07, 2019 at 01:57:08PM -0700, arn...@skeeve.com wrote:
> > Is the "see also" feature something that anybody
> > wants or is it just theoretical?
>
> I want it. The gawk manual has both See and See Also in its index.
>
> Hmm... Here are two entries in the current manual:
>
> @c
Gavin Smith wrote:
> On Mon, Mar 04, 2019 at 12:34:42AM -0700, arn...@skeeve.com wrote:
> > No. As per the mail you discovered, Karl just said "make it work with both"
> > so I did. But we're five years later, let's just make the change, please.
>
> Made in commit 2405caa.
Awesome!
> texindex s
On Mon, Mar 04, 2019 at 12:34:42AM -0700, arn...@skeeve.com wrote:
> No. As per the mail you discovered, Karl just said "make it work with both"
> so I did. But we're five years later, let's just make the change, please.
Made in commit 2405caa. Provided the latest revision of texi2dvi is
being u
On 3/3/19, Gavin Smith wrote:
> I went looking for past emails about the reasoning behind the choices
> of escape char but found nothing. Did you look into this when you
> wrote texindex?
Karl wanted the escape character to change for index files:
http://lists.gnu.org/archive/html/bug-texinfo/20
On 3/3/19, arn...@skeeve.com wrote:
> If that's the case, then texindex could also special case stuff like
>
> \entry {espresso makers, see coffee makers}{23}{espresso makers, see
> coffee
> makers}
>
> as input and and turn it into
>
> \entry {espresso makers, see coffee makers}{}
>
On 3/3/19, arn...@skeeve.com wrote:
> A few questions.
>
> 1. texindex.awk has provision for both \ and @ to be the command character
> (\entry vs. @entry). Do we still need that? Or will it always be backslash?
I think it could change to @ at some point. The toc and aux files do
use @ as the esc
Hi.
> Maybe it will just have to be accepted that out-of-date versions of
> texindex shouldn't be used with multi-level index entries, otherwise
> the index will appear somewhat mangled.
I think we just have to say that.
> Implemented as @subentry in git commit 372cfab.
>
> A test file is attach
I'm excited to see this supported in texinfo/texindex.
In the attachment, is @cindex the only way to get this or is this expected
to work with any user-defined index command?
Maxima will use a couple of user-defined indices to produce a nice
cross-reference of categories, so this is important.
O
Yes, any index command.
On Sat, 2 Mar 2019, 18:04 Raymond Toy, wrote:
> I'm excited to see this supported in texinfo/texindex.
>
> In the attachment, is @cindex the only way to get this or is this expected
> to work with any user-defined index command?
>
> Maxima will use a couple of user-define
On 3/1/19, arn...@skeeve.com wrote:
> @indent makes sense, since that's what happens on the page, but I
> can live with @tab also, or something like @subind might be good too.
> I don't have strong feelings, as long as it makes reasonable sense
> and is easy to convert an existing entry to it.
Im
On 3/1/19, Gavin Smith wrote:
> Whatever output is chosen, it would be good to check how existing
> versions of texindex deal with it: we should avoid completely breaking
> them if at all possible.
So awk texindex, given the input indextab.cp:
\entry{one}{1}{one}
\entry{one\subind two}{1}{one}{t
On Fri, Mar 01, 2019 at 02:25:29AM -0700, arn...@skeeve.com wrote:
> > Maybe a special marker character could be output that texindex treats
> > specially: e.g. the above would be output as
> >
> > \entry{aa^_a}{1}{aa}{a}
> > \entry{aa^_z}{3}{aa}{z}
> > \entry{aah}{5}{aah}
> >
> > where ^_ is a 0x
On Fri, Mar 01, 2019 at 02:25:29AM -0700, arn...@skeeve.com wrote:
>
> @indent makes sense, since that's what happens on the page, but I
> can live with @tab also, or something like @subind might be good too.
> I don't have strong feelings, as long as it makes reasonable sense
> and is easy to con
Hi.
> * What happens if there is an index entry with no secondary term and an
> identical index entry with a secondary term, e.g.
>
> @cindex foo
> @cindex foo @sub bar
>
> I think that both should be kept. When I tested it with C texindex, one
> of them was lost in the output.
I agree. We nee
On Thu, Feb 28, 2019 at 04:50:38AM -0700, arn...@skeeve.com wrote:
> > I remember there were problems with the positioning of @sortas: I'd like
> > to see if they could be fixed.
>
> Can you elaborate?
@cindex aaa @sortas{bbb}
didn't work completely properly as it output the index entry as "bbb
Hi. Sorry for the slow reply.
Gavin Smith wrote:
> The existing \primary macro does not take a page argument. This could
> be used to give you:
>
> coffee makers
> electric ... 32
>
> To get
>
> coffee makers . 15, 21
> electric ... 32
>
> you would use \entry
On Mon, Feb 25, 2019 at 07:01:04AM -0700, arn...@skeeve.com wrote:
> So why not just make it work with @cindex? Or do we really need
> a new command?
Existing index entries may have commas in them.
The existing \primary macro does not take a page argument. This could
be used to give you:
co
Hi. Thanks for the answer.
Gavin Smith wrote:
> On Thu, Feb 21, 2019 at 03:08:30AM -0700, arn...@skeeve.com wrote:
> > I have a feature request, please. It relates to indexing in texinfo.tex.
> > Packages like LaTeX and professional publishing packages provide for
> > multiple levels of index en
On Thu, Feb 21, 2019 at 03:08:30AM -0700, arn...@skeeve.com wrote:
> I have a feature request, please. It relates to indexing in texinfo.tex.
> Packages like LaTeX and professional publishing packages provide for
> multiple levels of index entries, usually up to three keys. For example
>
> c
Hi.
I have a feature request, please. It relates to indexing in texinfo.tex.
Packages like LaTeX and professional publishing packages provide for
multiple levels of index entries, usually up to three keys. For example
coffee makers . 15, 21
electric ... 32
34 matches
Mail list logo
