-
Notifications
You must be signed in to change notification settings - Fork 73
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
possible autochdir workaround #36
Comments
Looks scary ;) but yeah, CtrlP is a truly storehouse of knowledge. Do you think should we refer to this in the docs? Any pull requests will be appreciated :) |
I think so. I could merge it in there. This resolves the problem with the doubling of file paths when loading CtrlSpace Workspace described in my earlier posts (you should check this yourself with The problem now only reoccurs, naturally, when the project root set by CtrlSpace is one specified by the user, without any VCS markers. |
Yeah, that would be great :). |
Ok, autochdir should be working from now. Let me know if more issues occur. |
Perfeito. I stick to my CtrlP RootDir autochdir function and let you know of any irregularities, perhaps others will report if other autochdir functionalities go along as well. As a sidenote: there is a check for swapped files missing when loading a workspace. If there is a swap file, the work space simply won't load and you have to cancel by Control-C. |
1 similar comment
Perfeito. I stick to my CtrlP RootDir autochdir function and let you know of any irregularities, perhaps others will report if other autochdir functionalities go along as well. As a sidenote: there is a check for swapped files missing when loading a workspace. If there is a swap file, the work space simply won't load and you have to cancel by Control-C. |
This should be fixed too (#16). :) |
Oh, just in time. Already cloned your new master. |
Hello,
Just found the following lines in the documentation to CtrlP.vim, and they seem to behave well with respect to ctrlspace, better than
set autochdir
or the workaround proposed here. The autocmd sets thecwd
to the current project root, similar to what ctrlspace does when opening it first time.The text was updated successfully, but these errors were encountered: