Skip to content
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.

Sign up for GitHub

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

Jump to bottom

allow file-relative path completion for \input and add \subimport to path-completion #1227

Closed
stakaz opened this issue Mar 12, 2019 · 2 comments
Closed

allow file-relative path completion for \input and add \subimport to path-completion #1227

stakaz opened this issue Mar 12, 2019 · 2 comments
Assignees
@jlelong
Labels
feature request Feature request

Comments

@stakaz
Copy link

stakaz commented Mar 12, 2019

Hello, I wounder if it could be possible to have an option on how to complete paths in commands like \include, \input and \import. In particular I would like to have paths relative to the file and not the root of the project as my figures and tables are located per-file wise. Currently it is inconsistent anyway as I get the file-relative path for \include but root-relative for \includegraphics and \input.

In this context it would also be great to have completion of paths for \subimport and the other commands from this family.
@stakaz stakaz added the feature request Feature request label Mar 12, 2019
@jlelong
Copy link
Collaborator

jlelong commented Mar 20, 2019

I agree the current behaviour is not consistent.
To make it clear, file completion for \include, \input and \includegraphics should be root-relative by default, except when these commands are used inside an \import or \subimport file, in which case file completion should be relative to the current file directory.

To be complete, the import package also defines : \inputfrom, \subinputfrom, \includefrom, \subincludefrom and their * variants.

The completion for \includegraphics is a bit more delicate as we should also take into account paths defined by \graphicspath, see #1237.

I will work on this and make a PR in due course and keep this post updated.

@jlelong jlelong self-assigned this Mar 20, 2019
@jlelong
Copy link
Collaborator

jlelong commented Mar 28, 2019

New entry in the wiki

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jlelong jlelong

Labels
feature request Feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stakaz @jlelong