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

bnext switching problem #62

Open
llinfeng opened this issue Dec 9, 2014 · 2 comments
Open

bnext switching problem #62

llinfeng opened this issue Dec 9, 2014 · 2 comments

Comments

@llinfeng
Copy link

llinfeng commented Dec 9, 2014

It seems that the bnext will always call the new buffer to be the "primary buffer", which is fixed to the left edge and occupies the entire vertical split.
Is there a way to tune this? Yet maintaining the functionality of the primary buffer?

For detailed description, please refer to my posting on this link:
http://stackoverflow.com/questions/27381436/buffernext-is-distorting-the-window-layout

All the best,

Linfeng

@TimoDritschler
Copy link

Hey @llinfeng !
I was struggling with the same issue and investigated a little bit. I have the strong suspicion that this line is missing an ! operator right at the beginning of the if-statement.
Changing the line to:

au BufWinEnter * if !&l:buflisted || &l:filetype == 'help' | call DWM_AutoEnter() | endif

seemed to fix the problem for me.

Hope this helps!

@llinfeng
Copy link
Author

@TimoDritschler: Fantastic! What an elegant solution! I have updated the .vim file and have it available through Vundle as the following Github repo:
https://github.com/llinfeng/dwm.vim/

Thanks again!

raphael-proust pushed a commit to raphael-proust/dwm.vim that referenced this issue Dec 16, 2016
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