-
Notifications
You must be signed in to change notification settings - Fork 35
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
Do not change/set switchbuf=useopen
#32
Comments
we could guard it with a config setting, which is on by default for backwards compatibility. Do you feel like giving that a try? |
I would not add a config option for this: after all this is a config that the user is meant to make (globally). If it was particular useful in special cases, it could be set/changed using a FileType autocommand for example. The docs could mention how to do this and provide a link to this setting's documentation. An idea might be to use autocommands to override it when the user enters a pydoc buffer (and restore it), but that's probably not worth it. |
It has been like this for roughly 12 years, so it should be backwards compatible IMO |
You have a point there, but I would consider it to be just an old bug then, especially given that it uses It took me quite some effort back then to figure out that pydoc was changing this setting, and I think that more users are being annoyed by this than being helped. Adding a setting for this just feels wrong, but you could start with the following patch:
I have just removed this line locally. |
It gets set using
setlocal
, but is a global setting.https://github.com/fs111/pydoc.vim/blob/master/ftplugin/python_pydoc.vim#L120
The text was updated successfully, but these errors were encountered: