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.

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

As a user I would like to be able to configure Command-T to use Vim's default path #331

Closed
99arobe opened this issue Apr 21, 2018 · 1 comment

Comments

@99arobe
Copy link

99arobe commented Apr 21, 2018

From the docs I can see that when a user invokes :CommandT:

the project directory is determined according to the value of the |g:CommandTTraverseSCM| setting, which defaults to the SCM root of the current file

In order to modify this, a user can change either i) the options for the g:CommandTTraverseSCM setting or ii) invoke :CommandT with a path as an argument like this:

:CommandT ../path/to/other/files

Vim also has a built in path variable. The setting for this can be viewed using:

:set path?

The :find command can take a filename as an argument and it will then search for this file based on Vim's path setting. For example, if Vim's path variable was set to:

path=/fruits/apple,/drinks/water

then the find command will search through both the /fruits/apple and the /drinks/water directories without having to specify them as additional arguments to the find command. For example:

find foo.txt

will search in both the /fruits/apple and the /drinks/water directories.

Is there a way to change Command-T's settings to use Vim's path variable instead of trying to find the relevant directory by traversing the current files path for a SCM setup?

Alternatively, is there a way to specify multiple paths to invoke Command-T with?

@wincent
Copy link
Owner

wincent commented Aug 26, 2022

Given the big rewrite for v6.0.x, I'm closing all older issues as there is unlikely to be anything significant happening on the 5-x-devel branch from here on1. Feedback issue for 6.0.x is here:

Footnotes

  1. Patches and PRs would be welcome, but my personal efforts are going to be directed towards main.

@wincent wincent closed this as not planned Won't fix, can't repro, duplicate, stale Aug 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants