olsak / OpTeX

OpTeX - LuaTeX format with extended Plain TeX macros
http://petr.olsak.net/optex/
35 stars 13 forks source link

Move `f-<fontfam>` files to their own directory #70

Closed vlasakm closed 3 years ago

vlasakm commented 3 years ago

I know that the font family files are part of the "base", but maybe they would deserve a separate directory. There are alot of them and they are not really preloaded, but loaded on demand at runtime.

Not sure about the name, though. families or fontfamilies or fonts like in csplain? Should fams-ini.opm be moved too, as its just the index of them?

EDIT: Maybe the same thing for hisyntax?

olsak commented 3 years ago

All mentioned files are in the TEXINPUT pool. I don't see advantages. The tree needn't to be more complicated, IMHO.

vlasakm commented 3 years ago

I also forgot bib-X files.

My motivation:

Everything under $TEXMF/tex/optex is in TEXINPUT, so there also aren't any disadvantages.

olsak commented 3 years ago

I dislike too bushy trees. My current directory includes testing files for OpTeX and single symlink to the base/ of OpTeX which is named base. I am doing (with Tab completion, of course):

joe base/f-lmfonts.opm
joe base/fonts-select.opm
joe base/optex.ini
grep something base/*
etc.

My work will be more complicated if there is more than single point where all TEXINPUT files for OpTeX are. This is disadvantage of your idea from my point of view.

vlasakm commented 3 years ago

OK, maybe a comprise with optex/base/hisyntax, etc. could be made. Otherwise feel free to close the issue, it was just an idea.