On Sat, Jan 27, 2018 at 11:45 PM, Ken Moffat <[email protected]> wrote:
> Can you get an ID for trac (the wiki), please (ask Bruce) and raise a ticket > so I don't forget this ? > > At the moment my current systems don't have texlive installed, and I can't see > any point in me adding it to them - I'll be throwing them away soon because we > will soon be freezing and testing for 8.2. It is not a texlive issue. kpsewhich -var-value TEXMFCNF gives the correct paths. Evince uses TEXMFCNF from the environment (see evince-3.26.0/backend/dvi/texmfcnf.c). So now I have export TEXMFCNF=`kpsewhich -var-value TEXMFCNF` in .bash_profile > This will just be an optional link to tk, and anm optional runtime external > link, ( presumably to http://search.cpan.org/~srezic/Tk-804.034/ ?) so no big > deal to add those while we are tagging for 8.2. My bad, texdoc points to a script and hence does not need Tk. The perl module constructs a gui at runtime. > FWIW, I've never hear of texdoctk until today, There are wonderful things in the texlive documentation! > and personally I think evince has gone downhill since they revised the user > interface, but each to his own, and it (or perhaps okular, which is a much > heavier build) is probably the best way of looking at postscript files. The keyboard shortcuts are good once you discover them. There are more besides the ones listed in the help. F5, F9, / and w probably should be there.
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
