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
The support of multiple files is great, but it seems like that the detection algorithm is vague in terms of projects with multiple entries. E.g., we have two main files (like our article and beamer) sharing a common dependency (like a tikz diagram), in this case, how do I control which (or both) root file(s) to build / forward search when editing the dependency file?
In my opinion, a prompt (that can remember user's choice via project-scoped cache) or a project config file is fine. 👀
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The support of multiple files is great, but it seems like that the detection algorithm is vague in terms of projects with multiple entries. E.g., we have two main files (like our article and beamer) sharing a common dependency (like a tikz diagram), in this case, how do I control which (or both) root file(s) to build / forward search when editing the dependency file?
In my opinion, a prompt (that can remember user's choice via project-scoped cache) or a project config file is fine. 👀
% dep.tex A common dependency like a diagram.
Beta Was this translation helpful? Give feedback.
All reactions