terminal mode bracketed paste ?
Hi, It seems for me bracketed paste is not enabled in terminal mode. If I copy a few lines then paste into my zsh outside of vim (in tmux) then bracketed paste is enabled and the lines are not executed until I hit enter. But if in terminal mode I paste then each line is executed. Is this possible ? Is there a config setting I can enable ? Any help appreciated. thx, mark -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to insert text on current text position when I press key in vim in insert and normal mode?
On Tuesday 12 June 2018 10:36,
Gena Makhomed put forth the proposition:
> On 12.06.2018 2:22, Tony Mechelynck wrote:
>
> > On Mon, Jun 11, 2018 at 9:57 PM, Christian Brabandt wrote:
>
> > > :let @n=''
> > > :inoremap n
> > > :nmap a
>
> Christian, thank you! All works fine now!
>
> > > Note that I would not recommend mapping
>
> Why not? , as I understand, is always mapped to vim :help command.
> on keyboard located near key, it is very useful to press
>
> > Neither would I, because in Vim like in most other programs, F1 brings
> > you to the first page of help.
>
> And this is completely useless for me, I always can enter :help command
> from keyboard. Even more, typing just three keys :h is enough.
>
> It is more useful for me to read vim documentation via web-site,
> for example, site http://vimdoc.sourceforge.net/htmldoc/help.html
> contains documentation for vim 7.3, and I am use vim 7.4, it is Ok.
>
> Web site http://vimdoc.sourceforge.net/htmldoc/help.html
> was not updated from 2010 year - this is bug or feature?
>
> > Gena: What's wrong with Ctrl-R n (in Insert mode) or "np (in Normal
> > mode)?
>
> wrong #1: it is different keys in different modes,
> this is uncomfortable.
>
> wrong #2: I need to press more when one key on the keyboard,
> this is uncomfortable too.
>
> wrong #3: I use vim to edit text written on Russian language,
> and my keyboard frequently switched to Russian language layout.
> If keyboard in Russian language mode - vim just beep and do nothing.
>
> So, I need first switch keyboard from Russian to English,
> when find in which mode vim is currently, and select appropriate
> keyboard sequence, when enter this sequence on keyboard,
> when switch keyboard back from English to Russian mode.
>
> This is very uncomfortable for editing text.
> Just pressing is very fast and very useful.
>
> > Or if you're dead set on using only one keystroke, any F key
> > other than F1 (Help) and F10 (Menu) or any Shift-F key, would IMHO be
> > better than F1.
>
> I just don't want continually switch keyboard
> from Russian to English and from English to Russian.
>
> So, I can use only functional keys on keyboard or other
> key combinations which are available in VT100 terminal mode.
> (I use PuTTY, ssh and screen, so terminal is limited to VT100)
>
> P.S.
>
> One more question.
>
> Is it possible with vim:
>
> If I press and text under cursor is space - replace it with
> If I press and text under cursor is not space - generate beep
>
> I try to write this via function:
>
> ===
>
> function SpaceReplace()
> if getline(".")[col(".")-1] == ' '
> echo "replace under cursor with "
> else
> echo "beep"
> endif
> endfunction
>
> inoremap :call SpaceReplace()a
> nnoremap :call SpaceReplace()
>
> ===
>
> But I can't understand what I need to write instead "echo".
For the replacement you could try:
normal xi
For the 'beep' I guess echomsg "ERROR" for a visual message, or
something like:
silent ! printf "\a"
to make an ascii bell. Substitute the command after the ! to play a
sound if you want that. You will probably need to do a :redraw or a
:redrawstatus afterwards.
-Dave
> --
> Best regards,
> Gena
--
There are no threads in a.b.p.erotica, so there's no gain in using a
threaded news reader.
-- unknown source
.--. oo
()//
~'
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Custom key bindings to :Termdebug
Hi, The new :Termdebug in Vim 8.1 is great but it lacks usable key bindings like I used to have with VimGDB. For those unfamiliar, VimGDB introduced a GDB mode, which can be toggled with F7. When in GDB mode, the GDB shortcuts were mapped so "u" sent "up", "d" sent "down", "w" sent "where", "b" set a breakpoint and "B" unset the breakpoint, etc. How can I setup these same key bindings? Looks to me like the script provides some functions but not complete ones. Most importantly, the function/members necessary to send commands to the GDB buffer are inaccessible outside the script. Thanks, Uri -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to insert text on current text position when I press key in vim in insert and normal mode?
On 12.06.2018 2:22, Tony Mechelynck wrote:
On Mon, Jun 11, 2018 at 9:57 PM, Christian Brabandt wrote:
:let @n=''
:inoremap n
:nmap a
Christian, thank you! All works fine now!
Note that I would not recommend mapping
Why not? , as I understand, is always mapped to vim :help command.
on keyboard located near key, it is very useful to press
Neither would I, because in Vim like in most other programs, F1 brings
you to the first page of help.
And this is completely useless for me, I always can enter :help command
from keyboard. Even more, typing just three keys :h is enough.
It is more useful for me to read vim documentation via web-site,
for example, site http://vimdoc.sourceforge.net/htmldoc/help.html
contains documentation for vim 7.3, and I am use vim 7.4, it is Ok.
Web site http://vimdoc.sourceforge.net/htmldoc/help.html
was not updated from 2010 year - this is bug or feature?
Gena: What's wrong with Ctrl-R n (in Insert mode) or "np (in Normal
mode)?
wrong #1: it is different keys in different modes,
this is uncomfortable.
wrong #2: I need to press more when one key on the keyboard,
this is uncomfortable too.
wrong #3: I use vim to edit text written on Russian language,
and my keyboard frequently switched to Russian language layout.
If keyboard in Russian language mode - vim just beep and do nothing.
So, I need first switch keyboard from Russian to English,
when find in which mode vim is currently, and select appropriate
keyboard sequence, when enter this sequence on keyboard,
when switch keyboard back from English to Russian mode.
This is very uncomfortable for editing text.
Just pressing is very fast and very useful.
Or if you're dead set on using only one keystroke, any F key
other than F1 (Help) and F10 (Menu) or any Shift-F key, would IMHO be
better than F1.
I just don't want continually switch keyboard
from Russian to English and from English to Russian.
So, I can use only functional keys on keyboard or other
key combinations which are available in VT100 terminal mode.
(I use PuTTY, ssh and screen, so terminal is limited to VT100)
P.S.
One more question.
Is it possible with vim:
If I press and text under cursor is space - replace it with
If I press and text under cursor is not space - generate beep
I try to write this via function:
===
function SpaceReplace()
if getline(".")[col(".")-1] == ' '
echo "replace under cursor with "
else
echo "beep"
endif
endfunction
inoremap :call SpaceReplace()a
nnoremap :call SpaceReplace()
===
But I can't understand what I need to write instead "echo".
--
Best regards,
Gena
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim Patch broke pathogen?
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-maintain...@lists.alioth.debian.org > > Compiled by pkg-vim-maintain...@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
Re: [vim/vim] TeX file syntax: recognize "align" as math environment (#3010)
Andy Massimino wrote: Moved here: http://www.drchip.org/astronaut/vim/. Justification: Syntax/tex.vim should not support packages' macros, environments, etc.; I don't know about that.. but either way this PR would not be the right fix. Unfortunately, right now the user has no way of knowing they have to fetch packages from another website to support amsmath (an exceedingly common package). Well, the help (:help tex-morecommands) does mention that the user needs to fetch package support from another website. May I suggest looking at http://www.drchip.org/astronaut/vim/index.html#LATEXPKGS, for example. Regards, Chip Campbell -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Vim Patch broke pathogen?
On Thursday, June 14, 2018 at 11:50:17 AM UTC-7, Tony Mechelynck wrote: > 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. Turns out it was indeed related to compatible mode and the multiline blacklist line, which was fixed by a new release of pathogen in August. It is odd that an update to vim made this happen (where it definitely has not, for me, for years) but whatever. Good enough for me. Thanks folks. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Vim Patch broke pathogen?
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-maintain...@lists.alioth.debian.org > Compiled by pkg-vim-maintain...@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
Re: Vim Patch broke pathogen?
On Thursday, June 14, 2018 at 11:34:48 AM UTC-7, Christian Brabandt wrote: > On Do, 14 Jun 2018, Frew Schmidt wrote: > > > I use pathogen as my plugin manager and updated vim yesterday > > You know, that you don't need pathogen anymore since Vim 8? I am aware, but the vast majority of servers are still on 7, and I suspect that even if I used the built in packaging one of my many other issues would run into whatever regression this was. > > (via a PPA that is updated two or three times a week.) When I start > >vim I now get this error: > > And what was the previous version? The package version went from 8.1.0031-0york1~18.04 to 8.1.0037-0york1~18.04. > > Error detected while processing function > > pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled: > > line5: > > E15: Invalid expression: > > E15: Invalid expression: > > Is there perhaps a non-breaking space? I don't believe there is any non-breaking space in ascii, so this implies to me that there is *not* a non-breaking space: $ cat ~/.vim/bundle/pathogen/autoload/pathogen.vim | perl -pe 's/[[:ascii:]]//g' | wc -l 0 -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Vim Patch broke pathogen?
On Do, 14 Jun 2018, Frew Schmidt wrote: > I use pathogen as my plugin manager and updated vim yesterday You know, that you don't need pathogen anymore since Vim 8? > (via a PPA that is updated two or three times a week.) When I start >vim I now get this error: And what was the previous version? > Error detected while processing function > pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled: > line5: > E15: Invalid expression: > E15: Invalid expression: Is there perhaps a non-breaking space? Best, Christian -- Alle diktieren, außer Benno, der kann Steno. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Vim Patch broke pathogen?
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-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@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 >
Re: Vim Patch broke pathogen?
On Thu, Jun 14, 2018 at 4:50 PM, Frew Schmidt wrote: > I use pathogen as my plugin manager and updated vim yesterday (via a PPA that > is updated two or three times a week.) When I start vim I now get this error: > > Error detected while processing function > pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled: > line5: > E15: Invalid expression: > E15: Invalid expression: > Error detected while processing function > pathogen#infect[15]..pathogen#is_disabled: > line5: > E15: Invalid expression: > E15: Invalid expression: > Error detected while processing function > pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled: > line5: > E15: Invalid expression: > E15: Invalid expression: > Error detected while processing /home/frew/.vimrc: > line 142: > E185: Cannot find color scheme 'solarized8_dark_high' > Press ENTER or type command to continue > > My guess is that some parser thing broke. I don't think this has been > resolved in any of the last few patches. I'm on > > VIM - Vi IMproved 8.1 (2018 May 17, compiled Jun 13 2018 07:35:29) > Included patches: 1-53 > > Is this the right place to report something like this? > > Thanks. 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? 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 but that won't tell you where it was last set. 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). 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). Best regards, Tony. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Vim Patch broke pathogen?
I use pathogen as my plugin manager and updated vim yesterday (via a PPA that is updated two or three times a week.) When I start vim I now get this error: Error detected while processing function pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled: line5: E15: Invalid expression: E15: Invalid expression: Error detected while processing function pathogen#infect[15]..pathogen#is_disabled: line5: E15: Invalid expression: E15: Invalid expression: Error detected while processing function pathogen#infect[8]..pathogen#interpose[12]..pathogen#is_disabled: line5: E15: Invalid expression: E15: Invalid expression: Error detected while processing /home/frew/.vimrc: line 142: E185: Cannot find color scheme 'solarized8_dark_high' Press ENTER or type command to continue My guess is that some parser thing broke. I don't think this has been resolved in any of the last few patches. I'm on VIM - Vi IMproved 8.1 (2018 May 17, compiled Jun 13 2018 07:35:29) Included patches: 1-53 Is this the right place to report something like this? Thanks. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to replace edit command calling netrw by own function call
Le jeudi 14 juin 2018 06:59:09 UTC+2, Ken Takata a écrit : > Hi, > > 2018/6/13 Wed 19:54:54 UTC+9 Ni Va wrote: > > Hi, > > > > > > When you type :e it opens netrw explore command. > > > > Is it possible to replace it by my own function call. > > I think that the best way to know that is reading the code of netrw itself > or some other similar plugins (e.g. nerdtree). > > https://github.com/scrooloose/nerdtree/blob/cb9f4db6ffc98f055954801cfced9399a1da829a/plugin/NERD_tree.vim#L170-L175 > > Regards, > Ken Takata Ok thank you Ken -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
