-
Notifications
You must be signed in to change notification settings - Fork 72
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
Respect user's &autochdir for not triggered buffer #120
base: master
Are you sure you want to change the base?
Conversation
For buffers that won't trigger rooter, we can respect user's &autochdir setting for them unchanged.
Can't you get the same behaviour by allowing rooter to run for all buffers and having |
No, I tried it. And the reason for it is that, your code will for In fact, I thought, it is a design mistake in your code. Because your I say so, since as you can recall Lines 68 to 70 in 544e701
your code skips non triggered files. |
But why not trigger rooter in all buffers then? |
Sorry, I was modifying my last comment since I realized I overlooked your first comment. I didn't see you mentioned enable for all buffers. I thought, as your README suggests, user has choice for which buffer to be triggered. Your suggestion sounds like a workaround. I think there is need to have control both over triggered buffers and project patterns. I suspect this is what users will expect. |
Your perspective is also reasonable. It is understandable for you to keep your opinion on how people think for project files. |
I think it all depends on which way you look at it. When I first wrote rooter it ran for every buffer and Later on Personally I find it easier to get rooter to run on every buffer (i.e. |
Thanks for your historical explanation, now I get more of your idea. |
For buffers that won't trigger rooter, we can respect user's &autochdir
setting for them unchanged.