TaDaa / vimade

An eye friendly plugin that fades your inactive buffers and preserves your syntax highlighting!
MIT License
486 stars 8 forks source link

Increased startup time and breaking V-Block mode #21

Closed evserykh closed 5 years ago

evserykh commented 5 years ago

Hello. First of all thanks a lot for the plugin. I really like it.

Recently I noticed vim startup time increased and I can't go into visual block mode by pressing Ctlr-v. After some research I found that activated vimade plugin makes vim starting about two times longer.

Moreover, activated vimade plugin prevents enter visual block mode. I can activate that mode by pressing Ctrl-v twice although.

When I run vim without vimade plugin I don't notice those side effects.

Here is my Vim's version:

$ vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jun  9 2019 07:24:39)
macOS version
Included patches: 1-1500
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               +extra_search      +mouse_netterm     -tag_old_static
+arabic            -farsi             +mouse_sgr         -tag_any_white
+autocmd           +file_in_path      -mouse_sysmouse    -tcl
+autochdir         +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
-balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
-browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           +netbeans_intg     +textprop
+byte_offset       -hangul_input      +num64             +timers
+channel           +iconv             +packages          +title
+cindent           +insert_expand     +path_extra        -toolbar
-clientserver      +job               +perl              +user_commands
+clipboard         +jumplist          +persistent_undo   +vartabs
+cmdline_compl     +keymap            +postscript        +vertsplit
+cmdline_hist      +lambda            +printer           +virtualedit
+cmdline_info      +langmap           +profile           +visual
+comments          +libcall           -python            +visualextra
+conceal           +linebreak         +python3           +viminfo
+cryptv            +lispindent        +quickfix          +vreplace
+cscope            +listcmds          +reltime           +wildignore
+cursorbind        +localmap          +rightleft         +wildmenu
+cursorshape       +lua               +ruby              +windows
+dialog_con        +menu              +scrollbind        +writebackup
+diff              +mksession         +signs             -X11
+digraphs          +modify_fname      +smartindent       -xfontset
-dnd               +mouse             +startuptime       -xim
-ebcdic            -mouseshape        +statusline        -xpm
+emacs_tags        +mouse_dec         -sun_workshop      -xsmp
+eval              -mouse_gpm         +syntax            -xterm_clipboard
+ex_extra          -mouse_jsbterm     +tag_binary        -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1       
Linking: clang   -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim        -lncurses -liconv -lintl -framework AppKit  -L/usr/local/opt/lua/lib -llua5.3 -mmacosx-version-min=10.13 -fstack-protector-strong -L/usr/local/lib  -L/usr/local/Cellar/perl/5.30.0/lib/perl5/5.30.0/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc  -L/usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/lib/python3.7/config-3.7m-darwin -lpython3.7m -framework CoreFoundation  -lruby.2.6
TaDaa commented 5 years ago

I’m thinking this may be related to #18

I need to spend some time improving detecttermcolors as it’s causing too many side effects.

Try configuring vimade with

let g:vimade={}
let g:vimade.detecttermcolors=0
TaDaa commented 5 years ago

Didn't intend to close, let me know if the latest fixes the issue for you

evserykh commented 5 years ago

I’m thinking this may be related to #18

I need to spend some time improving detecttermcolors as it’s causing too many side effects.

Try configuring vimade with

let g:vimade={}
let g:vimade.detecttermcolors=0

I use Vim on Linux and on Mac. Your solution reduces start up time on both system. BTW on Linux there is no an issue with preventing visual block mode. I'll check the fix on Mac and let you know later

Updated that fixed the issues on mac too

TaDaa commented 5 years ago

Just an update on this detecttermcolors is now disabled by default, shouldn't need extra configuration in your vimrc to disable it.

Closing this for now, but feel free to reopen if you encounter related issues