-
Notifications
You must be signed in to change notification settings - Fork 5
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
Question about your statusline #1
Comments
Hello kshenoy, I've actually moved to using Emacs + Evil (basically Emacs + Vim), so it's been a while since I've played around with my vim configuration. If I recall correctly, there's nothing special about how I configure CtrlP to make it exhibit the behavior you're referencing. Instead, I think it naturally falls out of the fact (?) that CtrlP is a separate window, and like you said, when you move to a different window the statuslines change, in general, to emphasize the currently active one. That behavior is something I implemented myself. Have you had a chance to read through my blog post which goes over my custom statusline? The specific section I linked to covers the behavior of keeping track of which window is the active one. |
Hey Blaenk, I needed to RTFM a couple of times before I realized what my mistake was. I came across your blog post first and like the simplicity of the statusline. Thanks for writing a detailed post. |
No problem. Glad you were able to figure it out. |
Hi, I copied over these lines pertaining to your statusline code to my vimrc. I had to comment the section about Fugitive since I don't use it but other than that everything works well. I also copied your solarized colorscheme since you seem to have added custom highlight groups to it.
When I pull up CtrlP the statusline changes like I've moved to another window eg. arrows around the filename invert. I can't figure out how this is done. I don't know which autocmd gets triggered when opening CtrlP that causes s:RefreshStatus() which calls Status().
The text was updated successfully, but these errors were encountered: