On Thursday, June 14, 2018 at 2:50:17 PM UTC-4, Tony Mechelynck wrote:
> On Thu, Jun 14, 2018 at 8:20 PM, Frew Schmidt wrote:
> > On Thursday, June 14, 2018 at 8:49:44 AM UTC-7, Tony Mechelynck wrote:
> >> 1. Which featureset? That can be found from one of the next few lines
> >> in the :version output after the two you quoted; the line which ends
> >> with "Features included (+) or not (-)". What does that line say
> >> before that?
> >
> > VIM - Vi IMproved 8.1 (2018 May 17, compiled Jun 13 2018 07:35:29)
> > Included patches: 1-53
> > Modified by pkg-vim-maintainers@lists.alioth.debian.org
> > Compiled by pkg-vim-maintainers@lists.alioth.debian.org
> > Huge version with GTK3 GUI.  Features included (+) or not (-):
> > +acl               +farsi             +mouse_sgr         -tag_any_white
> > +arabic            +file_in_path      -mouse_sysmouse    +tcl
> > +autocmd           +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     +timers
> > +byte_offset       -hangul_input      +num64             +title
> > +channel           +iconv             +packages          +toolbar
> > +cindent           +insert_expand     +path_extra        +user_commands
> > +clientserver      +job               +perl              +vertsplit
> > +clipboard         +jumplist          +persistent_undo   +virtualedit
> > +cmdline_compl     +keymap            +postscript        +visual
> > +cmdline_hist      +lambda            +printer           +visualextra
> > +cmdline_info      +langmap           +profile           +viminfo
> > +comments          +libcall           -python            +vreplace
> > +conceal           +linebreak         +python3           +wildignore
> > +cryptv            +lispindent        +quickfix          +wildmenu
> > +cscope            +listcmds          +reltime           +windows
> > +cursorbind        +localmap          +rightleft         +writebackup
> > +cursorshape       +lua               +ruby              +X11
> > +dialog_con_gui    +menu              +scrollbind        -xfontset
> > +diff              +mksession         +signs             +xim
> > +digraphs          +modify_fname      +smartindent       +xpm
> > +dnd               +mouse             +startuptime       +xsmp_interact
> > -ebcdic            +mouseshape        +statusline        +xterm_clipboard
> > +emacs_tags        +mouse_dec         -sun_workshop      -xterm_save
> > +eval              +mouse_gpm         +syntax
> > +ex_extra          -mouse_jsbterm     +tag_binary
> > +extra_search      +mouse_netterm     +tag_old_static
> >    system vimrc file: "$VIM/vimrc"
> >      user vimrc file: "$HOME/.vimrc"
> >  2nd user vimrc file: "~/.vim/vimrc"
> >       user exrc file: "$HOME/.exrc"
> >   system gvimrc file: "$VIM/gvimrc"
> >     user gvimrc file: "$HOME/.gvimrc"
> > 2nd user gvimrc file: "~/.vim/gvimrc"
> >        defaults file: "$VIMRUNTIME/defaults.vim"
> >     system menu file: "$VIMRUNTIME/menu.vim"
> >   fall-back for $VIM: "/usr/share/vim"
> > Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time  -g -O2 -fdebug-prefix-map=/build/vim-Ku_8uM/vim-8.1.0037+v8.1.0053=. -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> > Linking: gcc   -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim   -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl  -L/usr/lib -llua5.2 -Wl,-E  -fstack-protector-strong -L/usr/local/lib  -L/usr/lib/x86_64-linux-gnu/perl/5.26/CORE -lperl -ldl -lm -lpthread -lcrypt  -L/usr/lib/python3.6/config-3.6m-x86_64-linux-gnu -lpython3.6m -lpthread -ldl -lutil -lm -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lm -lruby-2.5 -lpthread -lgmp -ldl -lcrypt -lm
> >
> >
> >> 2. Check the value of the 'runtimepath' option, as follows:
> >>                 :verbose set rtp?
> >> The answer will tell you the value (a comma-separated list of
> >> directories), and which script (if any) changed it last. If the value
> >> is too long it will get clipped; in that case you can see the full
> >> value with
> >>                 :echo &rtp
> >> but that won't tell you where it was last set.
> >
> > /home/frew/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim81,/usr/share/vim/vimfiles/after,/home/frew/.vim/after,/
> > home/frew/.fzf
> >
> >> 3. At least one of the directories mentioned in the 'runtimepath'
> >> value should, _at the time when the error is detected_, include a
> >> subdirectory named "autoload" with a file "pathogen.vim" in it. There
> >> is something wrong with the 5th line of function is_disabled() defined
> >> by that script. You should be able to see the code for that function
> >> by typing in Vim:
> >>                 :func pathogen#is_disabled
> >> (with no parentheses after it).
> >
> >    function pathogen#is_disabled(path) abort
> > 1    if a:path =~# '\~$'
> > 2      return 1
> > 3    endif
> > 4    let sep = pathogen#slash()
> > 5    let blacklist =
> > 6          \ get(g:, 'pathogen_blacklist', get(g:, 'pathogen_disabled', [])) +
> > 7          \ pathogen#split($VIMBLACKLIST)
> > 8    if !empty(blacklist)
> > 9      call map(blacklist, 'substitute(v:val, "[\\/]$", "", "")')
> > 10   endif
> > 11   return index(blacklist, fnamemodify(a:path, ':t')) != -1 || index(blacklist, a:path) != -1
> >    endfunction
> >
> >
> >> Also, Vim cannot find a script named
> >> "solarized8_dark_high.vim" in the "colors" subdirectory of any
> >> directory in 'runtimepath', with the value 'runtimepath' had when
> >> processing line 142 of your vimrc, a line which (I suppose) contains a
> >> :colorscheme command (probably without the leading colon). If you are
> >> in gvim, you can see which colorschemes are known by means of the menu
> >> "Edit → Color Scheme". In both gvim and Console Vim, you can also see
> >> them by typing :colorscheme followed by a space, then Ctrl-D rather
> >> than Enter (assuming your Vim was compiled with +cmdlline_compl).
> >
> > Yeah, the above is because pathogen (which I'm a little surprised you aren't familiar wit, https://github.com/tpope/vim-pathogen/blob/master/autoload/pathogen.vimh) *manages* runtime path, and if it fails to run inevitably one or more plugins will not load.
> >
> > Thanks, let me know if there is more I can do to dig this up.
> 
> Be familiar with it? Why should I? Not everybody uses the same plugins
> you do. I don't use that many plugins, and those I do are either (a)
> distributed with Vim (e.g. matchit, netrw, …), (b) found on the
> vim.org site (CSApprox, Unicode, CloseTag), or (c) by Dr. Chip
> (MathMenu, and some that are now dostributed with Vim started in that
> category too).
> 
> BTW, on that github link you gave I get a "404 Not Found" error.
> 
> So Vim seems to choke on the line
> 
>     let blacklist =
>           \ get(g:, 'pathogen_blacklist', get(g:, 'pathogen_disabled', [])) +
>           \ pathogen#split($VIMBLACKLIST)
> 
> Maybe $VIMBLACKLIST is undefined? Or maybe you are trying to run this
> in 'compatible' mode (or with the C flag set in 'cpoptions'), where
> continuation lines (i.e. lines whose first nonblank is a slash) cannot
> be used?
> 
> 
> Best regards,
> Tony.
Hmm,
The latest update I installed "broke" a plugin for me also, and I found a similar report on stackoverflow: https://stackoverflow.com/questions/50866748/vim-8-1-0037-update-breaks-multiple-plugins
I'm running Linux Mint 18.3 KDE and looking at the Synaptic history it looks like this update [- vim-gtk3 (2:8.1.0037-0york1~16.04) to 2:8.1.0037+v8.1.0053-0~ubuntu16.04.1 -] from jonathonf/vim PPA -- (and associated related packages) is when things broke.
I'm getting a dialog when I start gvim which has the following (truncated):
Error detected while processing /home/user/.vim/pack/my-plugins/start/vim-colors-solarized/colors/solarized.vim: 
line  138: 
E697: Missing end of List ']':  
E15: Invalid expression: [ 
line  139: 
E10: \ should be followed by /, ? or & 
line  140: 
You mention compatible mode, which I din't think I've got set?
running :verbose set cpoptions?
cpoptions=aAbBcCdDeEfFgHiIjJkKlLmMnoOpPqrRsStuvwWxXyZ$!%*-+<>;
        Last set from /usr/share/vim/vim81/menu.vim
I happen to have a VM which hadn't installed the update and running :verbose set cpoptions? gave:
cpoptions=aABceFs
Last set from /usr/share/vim/vim81/menu.vim
any ideas why the update caused this?
-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thursday, June 14, 2018
Subscribe to:
Post Comments (Atom)
 
No comments:
Post a Comment