zsh-workers
 help / color / mirror / code / Atom feed
* Zsh info index problems
@ 2000-04-05 11:27 Andrej Borsenkow
  2000-04-05 15:09 ` Bart Schaefer
  0 siblings, 1 reply; 2+ messages in thread
From: Andrej Borsenkow @ 2000-04-05 11:27 UTC (permalink / raw)
  To: ZSH workers mailing list

Thanks to Bart for pointing to info i command; one always learns
something :-)

Still, something strange.

i zcompile

gives me the first lines of shell builtins (description of autoload,
where zcompile is mentioned) and _not_ zcompile itself.

i globbing, qualifiers

ends here:

X~Y
     (Requires EXTENDED_GLOB to be set.)  Match anything that matches
     the pattern X but does not match Y.  This has lower precedence
...
     treated specially the way they usually are in globbing.
                                                   ^^^^^ this word

Is it the problem of info or something wrong with our info files?

-andrej

Have a nice DOS!
B >>


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Zsh info index problems
  2000-04-05 11:27 Zsh info index problems Andrej Borsenkow
@ 2000-04-05 15:09 ` Bart Schaefer
  0 siblings, 0 replies; 2+ messages in thread
From: Bart Schaefer @ 2000-04-05 15:09 UTC (permalink / raw)
  To: Andrej Borsenkow, ZSH workers mailing list

On Apr 5,  3:27pm, Andrej Borsenkow wrote:
} Subject: Zsh info index problems
}
} i zcompile
} 
} gives me the first lines of shell builtins (description of autoload,
} where zcompile is mentioned) and _not_ zcompile itself.
} 
} i globbing, qualifiers
} 
} ends here:
} 
}      treated specially the way they usually are in globbing.
}                                                    ^^^^^ this word
} 
} Is it the problem of info or something wrong with our info files?

It's the problem of info.  In the printed index, the page numbers will
be much more accurate.

The way indexing is implemented is by jumping to the referenced node and
then searching for the first word (actually, the string up to the first
comma, or the whole string if there isn't any comma) in the index entry.

E.g. if you look in the Concept Index (m Concept Index RET) at the
"aliases, completion of" entry, you'll see "Description of Options" as
the node reference.  So `i aliases, completion RET' first searches the
index and finds "aliases, completion of"; it grabs the first word (up
to the comma) and the node reference; and then jumps to "Description
of Options" searches forward for "aliases".

In that particular case, that gets it to the right spot.  In the case of
zcompile, it finds the first use rather than the definition.  I generally
follow `i' with a search (in emacs info mode, that's just `C-s C-w C-s'
but in standalone info you have to actually type the word).

There are a few cases where we could force the search to be more accurate
by using less-human-friendly strings in the part up to the comma, but not
very many.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-04-05 15:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-04-05 11:27 Zsh info index problems Andrej Borsenkow
2000-04-05 15:09 ` Bart Schaefer

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).