-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support addtoluatexpath package #3634
Comments
How does LaTeX know where these files are? TeXiFy will check TEXINPUTS, for example. |
@PHPirates hey thanks for the follow-up! I use a package that I wrote called addtoluatexpath, which adds paths to FWIW, I prefer not to modify the TEXINPUTS variable as I like to utilize the shared template sty and cls files while writing a report (and modify that master template files if need be), and then once the report is done, I copy the template files over to the project dir (to make a standalone folder). I believe if I modify TEXINPUTS, this workflow could get sticky. (I hope this makes sense). Open to other ideas, though. |
Then TeXiFy should simply look up all the I indeed don't understand, when you copy the template files to the project then you would need to remove the |
That would be great. I agree that ignoring the edge cases should be fine, the document author should know to avoid name conflicts. And yes, I basically do this:
AFAIK, settings texinputs should be avoided for luatex? I'm not too privy on that, though. The two commands that would be chechked are:
|
When entering a command, I see a nice list of suggested commands from packages (see image). I use shared sty and cls files (on a network drive) and would like to have the commands defined in these files appear in the drop-down code completion list. Any insight on how to get this working?
The text was updated successfully, but these errors were encountered: