You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Takuto. Would you consider having texdoc fall back to looking in the source/ tree (kpathsea search type "source") if no good matches are found in doc?
In current TL (Texdoc 4.1 (2024-03-10), texdoc fontscripts doesn't find anything. This is because I installed all files in the package in the source/ tree. It seemed more useful for users to keep everything together than to split off the pdf and README into doc. Since anyone actually considering using the package would want to see the source files.
Over the years, I've done this for a few other packages in a similar situation (apl, bibtexperllibs, bibtools, hyphenex, metatype1). For some of these, texdoc finds files in another package; for others, it finds nothing.
Thanks for considering.
The text was updated successfully, but these errors were encountered:
Hi Takuto. Would you consider having texdoc fall back to looking in the source/ tree (kpathsea search type "source") if no good matches are found in doc?
In current TL (Texdoc 4.1 (2024-03-10), texdoc fontscripts doesn't find anything. This is because I installed all files in the package in the source/ tree. It seemed more useful for users to keep everything together than to split off the pdf and README into doc. Since anyone actually considering using the package would want to see the source files.
Over the years, I've done this for a few other packages in a similar situation (apl, bibtexperllibs, bibtools, hyphenex, metatype1). For some of these, texdoc finds files in another package; for others, it finds nothing.
Thanks for considering.
The text was updated successfully, but these errors were encountered: