-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
:bdelete
does not trigger lcd
#59
Comments
Thanks for opening this issue! To clarify the expected behavior here, let’s say you have two buffers, A and B. You want
I don’t think it would cause problems, that’s a good idea! |
That is exactly the expected behaviour! From what I have tried, making that change seems to be resolving the issue. I am also planning on making a PR to add a feature (switch between opened projects), which would also rely on that. |
* Fix default settings that were improperly set * Use wider autocmd events (fixes #59) for `lcp` * add rooter integration (if vim-rooter is present, it’ll be reconfigured to play nicely with telescope-repo)
* Fix default settings that were improperly set * Use wider autocmd events (fixes #59) for `lcp` * add rooter integration (if vim-rooter is present, it’ll be reconfigured to play nicely with telescope-repo)
Good day to you,
When closing a buffer via
:bdelete
, thelcd
command does not trigger due to theautocmd
being{ "BufNewFile", "BufRead" }
. Would it cause problems if it wereBufEnter
(like as in vim-rooter) instead ofBufRead
?Regards.
The text was updated successfully, but these errors were encountered: