Giter Site home page Giter Site logo

vim-airline's Introduction

vim-airline

Say Thanks! reviewdog CI

Lean & mean status/tabline for vim that's light as air.

img

When the plugin is correctly loaded, there will be a nice statusline at the bottom of each vim window.

That line consists of several sections, each one displaying some piece of information. By default (without configuration) this line will look like this:

+-----------------------------------------------------------------------------+
|~                                                                            |
|~                                                                            |
|~                     VIM - Vi IMproved                                      |
|~                                                                            |
|~                       version 8.2                                          |
|~                    by Bram Moolenaar et al.                                |
|~           Vim is open source and freely distributable                      |
|~                                                                            |
|~           type :h :q<Enter>          to exit                               |
|~           type :help<Enter> or <F1>  for on-line help                      |
|~           type :help version8<Enter> for version info                      |
|~                                                                            |
|~                                                                            |
+-----------------------------------------------------------------------------+
| A | B |                     C                            X | Y | Z |  [...] |
+-----------------------------------------------------------------------------+

The statusline is the colored line at the bottom, which contains the sections (possibly in different colors):

section meaning (example)
A displays the mode + additional flags like crypt/spell/paste (INSERT)
B Environment status (VCS information - branch, hunk summary (master), battery level)
C filename + read-only flag (~/.vim/vimrc RO)
X filetype (vim)
Y file encoding[fileformat] (utf-8[unix])
Z current position in the file
[...] additional sections (warning/errors/statistics) from external plugins (e.g. YCM, syntastic, ...)

The information in Section Z looks like this:

10% ☰ 10/100 ln : 20

This means:

10%     - 10 percent down the top of the file
☰ 10    - current line 10
/100 ln - of 100 lines
: 20    - current column 20

For a better look, those sections can be colored differently, depending on various conditions (e.g. the mode or whether the current file is 'modified')

Features

Installation

This plugin follows the standard runtime path structure, and as such it can be installed with a variety of plugin managers:

Plugin Manager Install with...
Pathogen git clone https://github.com/vim-airline/vim-airline ~/.vim/bundle/vim-airline
Remember to run :Helptags to generate help tags
NeoBundle NeoBundle 'vim-airline/vim-airline'
Vundle Plugin 'vim-airline/vim-airline'
Plug Plug 'vim-airline/vim-airline'
VAM call vam#ActivateAddons([ 'vim-airline' ])
Dein call dein#add('vim-airline/vim-airline')
minpac call minpac#add('vim-airline/vim-airline')
pack feature (native Vim 8 package feature) git clone https://github.com/vim-airline/vim-airline ~/.vim/pack/dist/start/vim-airline
Remember to run :helptags ~/.vim/pack/dist/start/vim-airline/doc to generate help tags
manual copy all of the files into your ~/.vim directory

Straightforward customization

If you don't like the defaults, you can replace all sections with standard statusline syntax. Give your statusline that you've built over the years a face lift.

image

Themes

Themes have moved to another repository as of this commit.

Install the themes as you would this plugin (Vundle example):

Plugin 'vim-airline/vim-airline'
Plugin 'vim-airline/vim-airline-themes'

See vim-airline-themes for more.

Automatic truncation

Sections and parts within sections can be configured to automatically hide when the window size shrinks.

image

Smarter tab line

Automatically displays all buffers when there's only one tab open.

tabline

This is disabled by default; add the following to your vimrc to enable the extension:

let g:airline#extensions#tabline#enabled = 1

Separators can be configured independently for the tabline, so here is how you can define "straight" tabs:

let g:airline#extensions#tabline#left_sep = ' '
let g:airline#extensions#tabline#left_alt_sep = '|'

In addition, you can also choose which path formatter airline uses. This affects how file paths are displayed in each individual tab as well as the current buffer indicator in the upper right. To do so, set the formatter field with:

let g:airline#extensions#tabline#formatter = 'default'

Here is a complete list of formatters with screenshots:

default

image

jsformatter

image

unique_tail

image

unique_tail_improved

image

Seamless integration

vim-airline integrates with a variety of plugins out of the box. These extensions will be lazily loaded if and only if you have the other plugins installed (and of course you can turn them off).

image

image

image

image

image

image

image

vim-airline-vimagit-demo

vim-flog-airline-demo

image

image

airline-promptline-sc

papercolor_with_ctrlspace

image

image

image

image

image

image

Extras

vim-airline also supplies some supplementary stand-alone extensions. In addition to the tabline extension mentioned earlier, there is also:

whitespace

image

statusline on top

The statusline can alternatively be drawn on top, making room for other plugins to use the statusline: The example shows a custom statusline setting, that imitates Vims default statusline, while allowing to call custom functions. Use :let g:airline_statusline_ontop=1 to enable it.

image

Configurable and extensible

Fine-tuned configuration

Every section is composed of parts, and you can reorder and reconfigure them at will.

image

Sections can contain accents, which allows for very granular control of visuals (see configuration here).

image

Extensible pipeline

Completely transform the statusline to your liking. Build out the statusline as you see fit by extracting colors from the current colorscheme's highlight groups.

allyourbase

Rationale

There's already powerline, why yet another statusline?

  • 100% vimscript; no python needed.

What about vim-powerline?

  • vim-powerline has been deprecated in favor of the newer, unifying powerline, which is under active development; the new version is written in python at the core and exposes various bindings such that it can style statuslines not only in vim, but also tmux, bash, zsh, and others.

Where did the name come from?

I wrote the initial version on an airplane, and since it's light as air it turned out to be a good name. Thanks for flying vim!

Documentation

:help airline

Integrating with powerline fonts

For the nice looking powerline symbols to appear, you will need to install a patched font. Instructions can be found in the official powerline documentation. Prepatched fonts can be found in the powerline-fonts repository.

Finally, you can add the convenience variable let g:airline_powerline_fonts = 1 to your vimrc which will automatically populate the g:airline_symbols dictionary with the powerline symbols.

FAQ

Solutions to common problems can be found in the Wiki.

Performance

Whoa! Everything got slow all of a sudden...

vim-airline strives to make it easy to use out of the box, which means that by default it will look for all compatible plugins that you have installed and enable the relevant extension.

Many optimizations have been made such that the majority of users will not see any performance degradation, but it can still happen. For example, users who routinely open very large files may want to disable the tagbar extension, as it can be very expensive to scan for the name of the current function.

The minivimrc project has some helper mappings to troubleshoot performance related issues.

If you don't want all the bells and whistles enabled by default, you can define a value for g:airline_extensions. When this variable is defined, only the extensions listed will be loaded; an empty array would effectively disable all extensions (e.g. :let g:airline_extensions = []).

Also, you can enable caching of the various syntax highlighting groups. This will try to prevent some of the more expensive :hi calls in Vim, which seem to be expensive in the Vim core at the expense of possibly not being one hundred percent correct all the time (especially if you often change highlighting groups yourself using :hi commands). To set this up do :let g:airline_highlighting_cache = 1. A :AirlineRefresh will however clear the cache.

In addition you might want to check out the dark_minimal theme, which does not change highlighting groups once they are defined. Also please check the FAQ for more information on how to diagnose and fix the problem.

Screenshots

A full list of screenshots for various themes can be found in the Wiki.

Maintainers

The project is currently being maintained by Christian Brabandt and Bailey Ling.

If you are interested in becoming a maintainer (we always welcome more maintainers), please go here.

License

MIT License. Copyright (c) 2013-2021 Bailey Ling & Contributors.

vim-airline's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vim-airline's Issues

Documentation for integrating with powerline

Description page has no documentation of instruction part on how to use powerline symbols or fonts. As it is the simplicity of this plugin which prompted me to use it over powerline, hence I don't wish to install powerline. How then I am supposed to use just the fonts and symbols from the latter one?

Removing box when not in a git directory

I've been trying to think of a way to write this myself, but I've hit a wall.

How could I make airline remove the empty box when not editing a file in a git directory.

Disable vim-airline status line on certain buffers

Hello,

I just started using vim-airline and it is really good so far! I was wondering if it would be possible to disable the vim-airline statusline on certain buffers.

I currently use vdebug to debug PHP with vim and it opens a whole bunch of smaller split windows named:

5 %a "DebuggerWatch" line 74
6 #a "DebuggerStack" line 0
7 a "DebuggerStatus" line 0

Since these splits are very small I think it would be a good idea if you could disable vim-airline from showing the statusline on buffers with those names. I've attached a screenshot so you can see what I am talking about.

screenshot at jul 02 14-16-40

Hopefully that makes sense!

Take care,
Gary

Statusline rendering issues

Hi,
I'm using vim 703 through gnome-terminal and lxterminal. On first loading vim, the status bar is being rendered as;
^NORMAL^^^  ~/.vimrc ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ vim  utf-8[unix]  77%  69: 1
or without powerline fonts;
^NORMAL^>^ > ~/.vimrc ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ vim < utf-8[unix] < 77% : 69: 1
both with no colouring. The statusbar is rendered correctly (i.e. with colour and without the carets) as soon as the first command is run.

A perhaps separate issue is when a modification to a file is undone and redone then the modification symbol updates, but the background colour lags behind. I.E. if I modify a file I get a + symbol and the background goes purple. If I undo, the + disappears but the purple remains. It will update if I do another action, like trying to undo again. The same issue is present with redo.

This issues might have a common factor with updating the statusbar, but they can be split if not.

Many thanks, and great plugin!

Bizarre Error: E315 ml_get: invalid lnum

I just added vim-airline to my vimrc last night but am running into an error with it this morning.

I've determined it is something in airline because I commented out line 215 and restarted vim and the error disappeared. It only shows up when airline is running.

Here's what I do to reproduce the bug:

  • Open up a Java file (I can't reproduce it in an XML file)
  • Open up NERDTree
  • Enter Visual-line select mode
  • Try to select any number of lines and the error pops up

That's when the error shows up. One error shows up for every line that I try to select. It basically looks like this if I try to select the whole file: https://gist.github.com/tyru/455842

I'm on Vim 7.3 btw.

Let me know if you can think of any reason this is happening.

Crash linecolumn_prefix when editing file.

I'm using mac vim in iTerm2 with powerline patched font.
I set Double-Width Characters: on.

When open file >= 200 lines and scroll up and down, airline linecolumn_prefix crashes like following:

screen shot 2013-07-03 at 12 38 14 am

This doesn't occur in vim-powerline.
I like this lightweight plugin, so I would be very happily to use this if above issue was solved.
Thanks in advance.

tmux support???

Have airline-vim running perfectly on my vim, however I don't find it support my existing tmux. Is there anyway sort it out? lokaltog/powerline has tmux working out-of-box.

ctrl-p support

really like this and how lightweight it is. would be awesome if it had ctrl-p support, I'll look into it this weekend as well but thought I'd file this.

Paste mode support

Add support for set paste mode. Something similar to Powerline I guess, because right now it's pretty much impossible to tell except for the autoindent not working etc.

screen shot 2013-07-05 at 11 35 07

Error detected while starting vim

This is printed when running vim (7.3)

Error detected while processing function airline#update_statusline..<SNR>38_get_section:
line    1:
E121: Undefined variable: g:airline_section_a
E15: Invalid expression: exists('w:airline_section_{a:key}') ? w:airline_section_{a:key} : g:airline_section_{a:key}
E121: Undefined variable: g:airline_section_b
E15: Invalid expression: exists('w:airline_section_{a:key}') ? w:airline_section_{a:key} : g:airline_section_{a:key}
E121: Undefined variable: g:airline_section_x
E15: Invalid expression: exists('w:airline_section_{a:key}') ? w:airline_section_{a:key} : g:airline_section_{a:key}
E121: Undefined variable: g:airline_section_y
E15: Invalid expression: exists('w:airline_section_{a:key}') ? w:airline_section_{a:key} : g:airline_section_{a:key}
E121: Undefined variable: g:airline_section_z
E15: Invalid expression: exists('w:airline_section_{a:key}') ? w:airline_section_{a:key} : g:airline_section_{a:key}"~/.vimprojects" "~/.vimprojects" 147L, 3004C

Airline prevents splash screen

Hi,

I just noticed that airline prevents the vim splash screen from showing. This is probably due to some a screen refresh or redraw command.

This happens both for vim and gvim. I use the latest version of airline.

I am not sure, but I think this is a new "bug". That is, I don't think this happened a day or two ago.

(Oh, and btw: Thanks for making a superb alternative to powerline!)

Eighties support? :P

Hi, I really love this plugin, it's fast and easy configuration etc 😄

I really wished if there were an eighties theme for it, I'm not bright at vimL so thought if u could create one if it doesn't take that much time :O

Remove screenshots from repo

Uploading the images somewhere else (like imgur or whatever) would mean a smaller repo. The images only seem necessary for the README.

Thanks for this great plugin 👍

Disable airline in preview window

I use YouCompleteMe as code completion engine, which features preview of functions in a small window on the top of the current buffer. While using vim-airline, the statusline is also displayed on this preview window and causes a small slowdown each time this preview window is updated. It would be a solution, I think, to disable vim-airline specifically to workaround this small bug.
I hope I've explained my problem correctly.

Thanks in advance for your support.
This project is really awesome!

Giulio (random-cpp)

Create a template theme

I'd like to "port" a couple of popular vim-themes but I don't want to dig through the plugin file to figure out what each piece is. Can you comment the theme file to explain what each hex color will change?

UI Inconsistencies

screen shot 2013-07-05 at 11 00 54 am

Notice the arrow tip? Any idea why this happens?

I'm on MacVim on OS X 10.8.4

Errors opening vim

I installed spf13 for vim, where your vim-airline addon is included. Unfortunately it throws errors when I open vim, (it still starts the application) but everytime this happens:
screenshot from 2013-07-10 01 53 37

I also posted this on the spf13 issue page and I was told to file an issue here too.
spf13/spf13-vim#397

ctrl-p support

really like this and how lightweight it is. would be awesome if it had ctrl-p support, I'll look into it this weekend as well but thought I'd file this.

Support the font patched for old vim-powerline

I'm not the fan of python powerline. I still use the old vim-powerline. The font patched by the fontpatch in the repo of python powerline (not vim-powerline) looks ugly in vim-airline.

I managed to find out the corresponding symbols for the font patched by the fontpatch in the repo of vim-powerline.

" vim-powerline symbols
let g:airline_left_sep = '⮀'
let g:airline_left_alt_sep = '⮁'
let g:airline_right_sep = '⮂'
let g:airline_right_alt_sep = '⮃'
let g:airline_fugitive_prefix = '⭠'
let g:airline_readonly_symbol = '⭤'
let g:airline_linecolumn_prefix = '⭡'

These symbols are used in the fancy mode of vim-powerline

So how do you get it to start?

Do you write something in your vimrc file? I loaded it into my .vim/bundle folder through pathogen, but it doesn't auto load when I start vim, which I assumed it should... right?

Special symbols display is broken?

I've installed the plugin (together with bufferline). I've already got some powerline-patched fonts installed, so I've enabled corresponding option in my .vimrc. But instead of familiar "arrows" there was some squares with crosses inside.

image

At the same time, vim-powerline looks as expected. So I've opened plugin/airline.vim and saw the root of the problem - the entire line of powerline symbols looked wrong, and also the lines with separators setting:

image

If I open the plugin sources on github, this lines are also looking broken. Is it a problem on my side? Or, maybe, it's something with the script encoding?

Setting Themes Doesn't Work

let s:load_the_theme = g:airline#themes#{g:airline_theme}#normal is not a valid vim expression apparently.

Error detected while processing /usr/share/vim/vimfiles/plugin/airline.vim:
line   25:
E121: Undefined variable: g:airline#themes#default#normal
E15: Invalid expression: g:airline#themes#{g:airline_theme}#normal
Press ENTER or type command to continue

Add lawrencium support

Although not an avid mercurial user, I miss the current branch indicator in statusline. I've already forked the repo and am almost ready to send pull request after a bit more testing and updating the docs.

I've got one question - what do you think about reusing airline_enable_fugitive for lawrencium as well? I've added g:airline_enable_lawrencium but after rethinking it I'm starting to ask myself why add yet another variable when one could control both statusline indicators.

Is there a way limit size of bufferline?

The bufferline takes up too much space if many buffers are open, and then you can no longer see the current filename (or anything past the buffer list). Is there a way to limit the size so these other parts are still visible?

Branch only updates when changing window

Checking out master via the command line doesn't update the git branch (from fugitive) until I've switched window (or possibly some other action).

I'd expect it to update instantly, but understand if that's not doable.

Thanks!

Themes don't work for me

Somehow I get no colors.
I am using rxvt-unicode on Debian and the solarized color scheme is working fine (so it shouldn't be because I have no support for the colors).

vim

I tried all themes with let g:airline_theme='...'
None worked :(

Show file modification status for splits

The inactive window statusbar doesn't indicate if a buffer has been modified. Powerline adds a + to the buffer name, but it would be nice if airline could theme modified buffers.

I'll look into doing this if I have time, but it would be nice to see if I've saved everything at a glance.

Can't see the fancy unicode fonts.

Hi,

I just switched to your vim-airline and I noticed that even putting the powerline fonts into the .fonts and running fc-cache -vf ~/.fonts doesn't seem to make the chars show up.

Let me show you a screenshot of what I see:
http://i.imgur.com/kxgYWdI.png

Some help will be appreciated, thanks a bunch..

Oh also, in my .vimrc I did this:
let g:airline_theme='light'
let g:airline_powerline_fonts=0


Trying it with:

let g:airline_powerline_fonts=1

I get the same thing.

Unknown function: fugitive#head

Hi! I was testing vim-airline out but I couldn't manage to make it work with Fugitive.
vim-airline-error

I'm currently using the following setup:

  • Vundle 0.9
  • Fugitive 1.2

Thanks for this great plugin :)

Status line is updated in splits for unrelated buffers

When using multiple splits, the status line is updated incorrectly for all splits with information from the active one. In the following example, both splits were in normal mode but when changing to insert mode, the right, unrelated one is changed to insert mode too:

Update in right split

Unusably slow with multiple splits

Hey! Fantastic plugin, thanks for freeing me from Powerline.

I've noticed that with multiple splits, if I type with any speed Vim lags enough to make things totally unusable. I haven't investigated much (apologies) but getting it out there in case there's anything obvious to you. (Presumably a misbehaving autocmd?).

(My vimrc is here FWIW, but I tried with disabling all my plugins besides airline and still experienced the slowdown).

Statusline partially duplicates on splits

How to reproduce:

  • enable, for example, fugitive support in airiline;
  • go to directory contains repo;
  • open some file from it;
  • open help split (e.g. :h airline);
  • see, that statusline for help buffer also contains fugitive info;
  • go to insert mode;
  • see, that statusline for help buffer is in insert mode as well;

Screenshot to describe what I mean

E132: Function call depth is higher than 'maxfuncdepth'

When launching vim:

Error detected while processing function airline#update_statusline..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>
28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_
window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_ov
errides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..
<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_a
pply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_wind
ow_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overri
des..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR
>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply
_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_o
verrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides.
.<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_
apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_win
dow_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overr
ides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SN
R>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_appl
y_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_
overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides
..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28_apply_window_overrides..<SNR>28
_apply_window_overrides:
line   15:
E132: Function call depth is higher than 'maxfuncdepth'

my .vimrc:

execute pathogen#infect()
syntax on
filetype plugin indent on

set modeline
set ruler

set laststatus=2
let g:airline_powerline_fonts=1

Terminal is iTerm2 set to xterm-256colour

$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 14 2013 18:02:01)
Compiled by [email protected]
Normal version without GUI.  Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent 
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
-conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs 
-dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path 
+find_in_path +float +folding -footer +fork() -gettext -hangul_input +iconv 
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent 
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape 
-mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse 
+mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype 
+path_extra -perl +persistent_undo +postscript +printer -profile +python/dyn 
-python3 +quickfix +reltime -rightleft +ruby/dyn +scrollbind +signs 
+smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary 
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
 -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo 
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
 -xterm_clipboard -xterm_save 
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -D_FORTIFY_SOURCE=0 -Iproto -DHAVE_CONFIG_H -arch i386 -arch x86_64 -g -Os -pipe
Linking: gcc -arch i386 -arch x86_64 -o vim -lncurses

My colorscheme is being change

Hey ! After installing the plugin, I noticed that my colorscheme is not loaded by default anymore... Any thoughts on this ?

When Quickfix is the only window, the status never resets to reflect mode.

I use the Ack plugin which uses the quickfix list to display results in a new window, loading the first result in a new buffer in another window, creating a split view. When the top pane is closed (via :bd), the quickfix list is now the primary view. Closing the quickfix list with :bd displays an empty buffer but the status line still says "Quickfix". Opening a new buffer in the primary window still says "Quickfix".

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.