Discussion:
[tex-k] kpsewhich --help is unwieldy
Julian Gilbey
2014-12-04 13:34:23 UTC
Permalink
I just typed kpsewhich --help and the output reached (on my
80-character width screen) 522 lines, which is unhelpful.

Could the list of recognised suffixes be made available through a
separate command such as kpsewhich --help-suffixes (with a note to
this effect at the end of the ordinary help)? And maybe not list the
expanded paths, as they take up most of the screen space, and are
available through other easy-to-use documented means if required?

Best wishes,

Julian
Karl Berry
2014-12-04 22:15:20 UTC
Permalink
Julian,

I just typed kpsewhich --help and the output reached (on my
80-character width screen) 522 lines, which is unhelpful.

What's the --version output? I don't get that. My output is 94 lines
and does not include any expanded paths, just recognized suffixes.

I do seem to recall outputting the expanded paths at some point, but I
checked back and it doesn't seem to be in any release going back many
years. Are you using a distro's kpsewhich, or original TL?

Best,
Karl
Norbert Preining
2014-12-04 22:44:20 UTC
Permalink
Post by Karl Berry
What's the --version output? I don't get that. My output is 94 lines
I guess he is using kpsewhich from TeX Live on Debian/sid, which
is the 2015dev version

Norbert

------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
Julian Gilbey
2014-12-04 23:35:02 UTC
Permalink
Post by Norbert Preining
Post by Karl Berry
What's the --version output? I don't get that. My output is 94 lines
I guess he is using kpsewhich from TeX Live on Debian/sid, which
is the 2015dev version
Indeed.

Julian

Karl Berry
2014-12-04 23:07:07 UTC
Permalink
I guess he is using kpsewhich from TeX Live on Debian/sid, which
is the 2015dev version

No wonder it seemed familiar.
Ok, I think I'll about splitting up the output.

k
Loading...