#2 Add and input of local .sty and .tex files fails

[Robert Petry]

BUG
When creating figs I often have symbol definitions unique to my document that I include in figures. These I keep in a localsymbols.sty file in the directory with the fig files. Their inclusion in a regular tex file works because kpswhich will look in the current directory by default. However when I use the --add option to fig2pdf it fails to find the file. The reason this is occurring is because fig2pdf is compiling in a subdirectory of /tmp and is no longer able to find the included file in the current directory because that file is not copied over and no longer sits anywhere on the search tree. A workaround is to define the TEXINPUTS path variable as follows:

TEXINPUTS=$PWD//: fig2pdf --add=localsymbols myfig.fig

so that the current directory is passed along to where the compilation is occurring. Obviously I could just install my localsymbols.sty file "properly" on my system and things would work, but I share my files with others and this is something I wouldn't want to expect them to have to do. Also it would be problematic if I use this file naming convention across different projects. So fixing this is desirable.

FEATURE REQUEST
Finally (as a feature request) it would be convenient if the --add option would allow you to also specify a file with a .tex extension like localsymbols.tex . Currently is uses \usepackage{} which will fail on such a file. Ideally the --add option could just check the file extension and if it was .tex it could just use an \input at the appropriate preamble location. I realize there is a --input option that fig2pdf has but this is for introducing a separate template which is not what is desired. Currently I create a symbolic link from localsymbols.sty to localsymbols.tex, but it would be nice if this just worked.

Thanks for listening!

Sincerely,
Robert Petry