search

UnikMask / iroh-vim

A dark color scheme volcanic / ceramic style
MIT License
15 stars 0 forks source link

iroh possibly not playing nice with syntastic #1

Closed criswell closed 4 years ago

criswell commented 4 years ago

I've got a weird issue with iroh that I suspect might be it's not playing nice with another plugin I use (not a vimscript guy, so I'm not certain how to completely diagnose it).

When I fire up vim with iroh, it always gives me the following errors:

IrohFg
IrohIron0
IrohIron1
IrohIron2
IrohClay0
IrohClay1
IrohClay2
IrohClay3
IrohCopper0
IrohCopper1
IrohBrush0
IrohBrush1
IrohAntimony0
IrohAntimony1
IrohGold0
IrohGold1
IrohGold2
IrohCobalt0
IrohCobalt1
IrohMetal0
Cursor
SyntasticError
SyntasticWarning
Press ENTER or type command to continue

This only happens when I enable iroh. Looking at that error, I suspect it's some conflict with syntastic. After this error, everything seems to work fine (iroh colorscheme looks fine, and syntastic seems to work fine).

My vim version info:

VIM - Vi IMproved 8.2 (2019 Dec 12)
Included patches: 1-701
Compiled by 'http://www.opensuse.org/'
Huge version without GUI.  Features included (+) or not (-):
+acl               -farsi             +mouse_sgr         +tag_binary
+arabic            +file_in_path      -mouse_sysmouse    -tag_old_static
+autocmd           +find_in_path      +mouse_urxvt       -tag_any_white
+autochdir         +float             +mouse_xterm       -tcl
-autoservername    +folding           +multi_byte        +termguicolors
-balloon_eval      -footer            +multi_lang        +terminal
+balloon_eval_term +fork()            -mzscheme          +terminfo
-browse            +gettext           +netbeans_intg     +termresponse
++builtin_terms    -hangul_input      +num64             +textobjects
+byte_offset       +iconv             +packages          +textprop
+channel           +insert_expand     +path_extra        +timers
+cindent           +ipv6              +perl              +title
-clientserver      +job               +persistent_undo   -toolbar
-clipboard         +jumplist          +popupwin          +user_commands
+cmdline_compl     +keymap            +postscript        +vartabs
+cmdline_hist      +lambda            +printer           +vertsplit
+cmdline_info      +langmap           +profile           +virtualedit
+comments          +libcall           -python            +visual
+conceal           +linebreak         +python3/dyn       +visualextra
+cryptv            +lispindent        +quickfix          +viminfo
+cscope            +listcmds          +reltime           +vreplace
+cursorbind        +localmap          +rightleft         +wildignore
+cursorshape       +lua/dyn           +ruby/dyn          +wildmenu
+dialog_con        +menu              +scrollbind        +windows
+diff              +mksession         +signs             +writebackup
+digraphs          +modify_fname      +smartindent       -X11
-dnd               +mouse             -sound             -xfontset
-ebcdic            -mouseshape        +spell             -xim
+emacs_tags        +mouse_dec         +startuptime       -xpm
+eval              -mouse_gpm         +statusline        -xsmp
+ex_extra          -mouse_jsbterm     -sun_workshop      -xterm_clipboard
+extra_search      +mouse_netterm     +syntax            -xterm_save
   system vimrc file: "/etc/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/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -Wall -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -Wall -pipe -fno-strict-aliasing -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1       
Linking: gcc   -L. -flto=auto -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE  -flto=auto -L/usr/local/lib -Wl,--as-needed -o vim        -lm  -lselinux  -ltinfo -lacl -ldl   -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE  -L/usr/local/lib64 -fstack-protector-strong  -L/usr/lib/perl5/5.30.1/x86_64-linux-thread-multi/CORE -lperl -lm -ldl -lcrypt -lpthread

and my dot-files for all my vim config can be found here https://github.com/criswell/meh (in case the syntastic thing is a red-herring and the real culprit is elsewhere).

Let me know if there's any other information needed, or want me to try anything.

UnikMask commented 4 years ago

Ok, I found the root of the issue! The message that is shown is in fact not an error but a debugging message which I had left here but doesn't seem to show on my side. 

if bg[1] ~= 'n'
    echomsg a:group
endif

I removed it, so if you pull the latest version to vim, the message should disappear.

I can't seem to reproduce the bug, but that line seemed to obviously be the cause for all the trouble. So I'll close the issue once you can confirm to me the message doesn't appear anymore.

In any case, thank you for the heads up!

criswell commented 4 years ago

Sweet! Yep, that solved it!

Awesome color scheme, btw.