How can I fix the reason for this error message

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

How can I fix the reason for this error message

tuxic
Hi,

I am using "bleeding-edge" vim (not gvim, not neovim) on GENTOO-Linux
and I emerge it via GENTOO package manager up to the newest possible.

vim --version gives me:

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May  1 2017 03:28:35)
Included patches: 1-594
Modified by Gentoo-9999
Compiled by mccramer@solfire
Huge version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     -tcl
-balloon_eval    +folding         +mouse_xterm     +termguicolors
-browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +gettext         -mzscheme        +textobjects
+channel         -hangul_input    +netbeans_intg   +timers
+cindent         +iconv           +num64           +title
+clientserver    +insert_expand   +packages        -toolbar
+clipboard       +job             +path_extra      +user_commands
+cmdline_compl   +jumplist        -perl            +vertsplit
+cmdline_hist    +keymap          +persistent_undo +virtualedit
+cmdline_info    +lambda          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       -python          +vreplace
-cscope          +lispindent      -python3         +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con      +lua             +rightleft       +writebackup
+diff            +menu            -ruby            +X11
+digraphs        +mksession       +scrollbind      +xfontset
-dnd             +modify_fname    +signs           -xim
-ebcdic          +mouse           +smartindent     -xpm
+emacs_tags      -mouseshape      +startuptime     +xsmp_interact
+eval            +mouse_dec       +statusline      +xterm_clipboard
+ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
+extra_search    -mouse_jsbterm   +syntax          
+farsi           +mouse_netterm   +tag_binary      
   system vimrc file: "/etc/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/share/vim"
Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H     -march=native -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
Linking: x86_64-pc-linux-gnu-gcc   -Wl,-O1 -L/usr/local/lib -Wl,--as-needed -o vim    -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -lncurses -lelf -lnsl  -lacl -lattr -lgpm -ldl  -L/usr/lib/x86_64-linux-gnu -lluajit-5.1        


I am using vim-plug as vims package manager.
I update vim-plug and all vim packages on regulary base.

All that has worked flawlessly before. Since yesterday (or so) I got
this message when starting vim:

[vim-plug] Invalid argument: OceanBlack256 (implicit `vim-scripts' expansion is deprecated)
Press ENTER or type command to continue


OceanBlack256 is a color scheme, which works before without problems.
As far as I can tell it was not updated since.

How can I fix this bug (the colorscheme is not working very well since
it give me this error)?
Was something related changed in vim?

Thanks for any help in advance!
Cheers
Meino



--
--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: How can I fix the reason for this error message

Christian Brabandt
Hi tuxic!

On Mi, 03 Mai 2017, [hidden email] wrote:

> Hi,
>
> I am using "bleeding-edge" vim (not gvim, not neovim) on GENTOO-Linux
> and I emerge it via GENTOO package manager up to the newest possible.
>
> vim --version gives me:
>
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May  1 2017 03:28:35)
> Included patches: 1-594
> Modified by Gentoo-9999
> Compiled by mccramer@solfire
> Huge version without GUI.  Features included (+) or not (-):
> +acl             +file_in_path    +mouse_sgr       +tag_old_static
> +arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
> +autocmd         +float           +mouse_urxvt     -tcl
> -balloon_eval    +folding         +mouse_xterm     +termguicolors
> -browse          -footer          +multi_byte      +terminfo
> ++builtin_terms  +fork()          +multi_lang      +termresponse
> +byte_offset     +gettext         -mzscheme        +textobjects
> +channel         -hangul_input    +netbeans_intg   +timers
> +cindent         +iconv           +num64           +title
> +clientserver    +insert_expand   +packages        -toolbar
> +clipboard       +job             +path_extra      +user_commands
> +cmdline_compl   +jumplist        -perl            +vertsplit
> +cmdline_hist    +keymap          +persistent_undo +virtualedit
> +cmdline_info    +lambda          +postscript      +visual
> +comments        +langmap         +printer         +visualextra
> +conceal         +libcall         +profile         +viminfo
> +cryptv          +linebreak       -python          +vreplace
> -cscope          +lispindent      -python3         +wildignore
> +cursorbind      +listcmds        +quickfix        +wildmenu
> +cursorshape     +localmap        +reltime         +windows
> +dialog_con      +lua             +rightleft       +writebackup
> +diff            +menu            -ruby            +X11
> +digraphs        +mksession       +scrollbind      +xfontset
> -dnd             +modify_fname    +signs           -xim
> -ebcdic          +mouse           +smartindent     -xpm
> +emacs_tags      -mouseshape      +startuptime     +xsmp_interact
> +eval            +mouse_dec       +statusline      +xterm_clipboard
> +ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
> +extra_search    -mouse_jsbterm   +syntax          
> +farsi           +mouse_netterm   +tag_binary      
>    system vimrc file: "/etc/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/share/vim"
> Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H     -march=native -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
> Linking: x86_64-pc-linux-gnu-gcc   -Wl,-O1 -L/usr/local/lib -Wl,--as-needed -o vim    -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -lncurses -lelf -lnsl  -lacl -lattr -lgpm -ldl  -L/usr/lib/x86_64-linux-gnu -lluajit-5.1        
>
>
> I am using vim-plug as vims package manager.
> I update vim-plug and all vim packages on regulary base.
>
> All that has worked flawlessly before. Since yesterday (or so) I got
> this message when starting vim:
>
> [vim-plug] Invalid argument: OceanBlack256 (implicit `vim-scripts' expansion is deprecated)
> Press ENTER or type command to continue
>
>
> OceanBlack256 is a color scheme, which works before without problems.
> As far as I can tell it was not updated since.
>
> How can I fix this bug (the colorscheme is not working very well since
> it give me this error)?
> Was something related changed in vim?

The error (or let me better call it warning) comes from vim-plug. It
looks like, you need to adjust your Plug call and add manually the
vim-scripts repo if there is no maintained repository for your color
scheme.

https://github.com/junegunn/vim-plug/issues/625
https://github.com/junegunn/vim-plug/commit/f7e6a86807a1f0be7257620a8c425e1a32f877bb

Best,
Christian
--
Man gebe manchem Selbstvertrauen, so ist er ein Weltmann.
                -- Jean Paul

--
--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: How can I fix the reason for this error message

tuxic
On 05/03 07:51, Christian Brabandt wrote:

> Hi tuxic!
>
> On Mi, 03 Mai 2017, [hidden email] wrote:
>
> > Hi,
> >
> > I am using "bleeding-edge" vim (not gvim, not neovim) on GENTOO-Linux
> > and I emerge it via GENTOO package manager up to the newest possible.
> >
> > vim --version gives me:
> >
> > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May  1 2017 03:28:35)
> > Included patches: 1-594
> > Modified by Gentoo-9999
> > Compiled by mccramer@solfire
> > Huge version without GUI.  Features included (+) or not (-):
> > +acl             +file_in_path    +mouse_sgr       +tag_old_static
> > +arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
> > +autocmd         +float           +mouse_urxvt     -tcl
> > -balloon_eval    +folding         +mouse_xterm     +termguicolors
> > -browse          -footer          +multi_byte      +terminfo
> > ++builtin_terms  +fork()          +multi_lang      +termresponse
> > +byte_offset     +gettext         -mzscheme        +textobjects
> > +channel         -hangul_input    +netbeans_intg   +timers
> > +cindent         +iconv           +num64           +title
> > +clientserver    +insert_expand   +packages        -toolbar
> > +clipboard       +job             +path_extra      +user_commands
> > +cmdline_compl   +jumplist        -perl            +vertsplit
> > +cmdline_hist    +keymap          +persistent_undo +virtualedit
> > +cmdline_info    +lambda          +postscript      +visual
> > +comments        +langmap         +printer         +visualextra
> > +conceal         +libcall         +profile         +viminfo
> > +cryptv          +linebreak       -python          +vreplace
> > -cscope          +lispindent      -python3         +wildignore
> > +cursorbind      +listcmds        +quickfix        +wildmenu
> > +cursorshape     +localmap        +reltime         +windows
> > +dialog_con      +lua             +rightleft       +writebackup
> > +diff            +menu            -ruby            +X11
> > +digraphs        +mksession       +scrollbind      +xfontset
> > -dnd             +modify_fname    +signs           -xim
> > -ebcdic          +mouse           +smartindent     -xpm
> > +emacs_tags      -mouseshape      +startuptime     +xsmp_interact
> > +eval            +mouse_dec       +statusline      +xterm_clipboard
> > +ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
> > +extra_search    -mouse_jsbterm   +syntax          
> > +farsi           +mouse_netterm   +tag_binary      
> >    system vimrc file: "/etc/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/share/vim"
> > Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H     -march=native -O2 -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
> > Linking: x86_64-pc-linux-gnu-gcc   -Wl,-O1 -L/usr/local/lib -Wl,--as-needed -o vim    -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -lncurses -lelf -lnsl  -lacl -lattr -lgpm -ldl  -L/usr/lib/x86_64-linux-gnu -lluajit-5.1        
> >
> >
> > I am using vim-plug as vims package manager.
> > I update vim-plug and all vim packages on regulary base.
> >
> > All that has worked flawlessly before. Since yesterday (or so) I got
> > this message when starting vim:
> >
> > [vim-plug] Invalid argument: OceanBlack256 (implicit `vim-scripts' expansion is deprecated)
> > Press ENTER or type command to continue
> >
> >
> > OceanBlack256 is a color scheme, which works before without problems.
> > As far as I can tell it was not updated since.
> >
> > How can I fix this bug (the colorscheme is not working very well since
> > it give me this error)?
> > Was something related changed in vim?
>
> The error (or let me better call it warning) comes from vim-plug. It
> looks like, you need to adjust your Plug call and add manually the
> vim-scripts repo if there is no maintained repository for your color
> scheme.
>
> https://github.com/junegunn/vim-plug/issues/625
> https://github.com/junegunn/vim-plug/commit/f7e6a86807a1f0be7257620a8c425e1a32f877bb
>
> Best,
> Christian
> --
> Man gebe manchem Selbstvertrauen, so ist er ein Weltmann.
> -- Jean Paul
>
> --
> --
> 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 [hidden email].
> For more options, visit https://groups.google.com/d/optout.
>

Hi Christian,

thanks for the links and the explanations!
I fixxxxed that -- but I dont know, why this become a problem...

The files in question are:
.vim/plugged/OceanBlack256
.vim/plugged/OceanBlack256/.git/(some files below this point...)
.vim/plugged/OceanBlack256/colors
.vim/plugged/OceanBlack256/colors/oceanblack256.vim
.vim/plugged/OceanBlack256/README

The Plug - command was:
Plug "OceanBlack256"

Now I have to do
Plug 'OceanBlack256/colors/oceanblack256.vim'

But this is nonetheless no problem:
.vim/plugged/.git/(some files below this point
.vim/plugged/README.rst
.vim/plugged/Makefile
.vim/plugged/autoload
.vim/plugged/autoload/screen.vim
.vim/plugged/plugin
.vim/plugged/plugin/screen.vim
.vim/plugged/doc
.vim/plugged/doc/tags
.vim/plugged/doc/screen.txt

Plugged with:
Plug 'ervandew/screen

(eeornously using 'ervandew' as folder.

When only using
Plug 'screen' as the folder suggests, the "deprecated" message
appears again.

May be it is a problem for vim-plug. if the folder has the
same name as the script inside?

Why is oceanblack256.vim is a script and screen.vim is none?
;) :)

The problem seems to

Cheers
Meino




--
--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: How can I fix the reason for this error message

Christian Brabandt
On Mi, 03 Mai 2017, [hidden email] wrote:

> thanks for the links and the explanations!
> I fixxxxed that -- but I dont know, why this become a problem...
>
> The files in question are:
> .vim/plugged/OceanBlack256
> .vim/plugged/OceanBlack256/.git/(some files below this point...)
> .vim/plugged/OceanBlack256/colors
> .vim/plugged/OceanBlack256/colors/oceanblack256.vim
> .vim/plugged/OceanBlack256/README

That is your local clone of the repository.

> The Plug - command was:
> Plug "OceanBlack256"
>
> Now I have to do
> Plug 'OceanBlack256/colors/oceanblack256.vim'

No that is wrong.

You need to give Plug the remote github repository from which it can
clone. Apparently, if no github username was given, vim-plug silently
used vim-scripts/name to clone from. That no stopped and that is what
the error message is about. So you could use Plug vim-scripts/OceanBlack256
or you simply clone the vim-colorscheme package, which also does include
OceanBlack256 e.g. Plug flazz/vim-colorschemes

>
> But this is nonetheless no problem:
> .vim/plugged/.git/(some files below this point
> .vim/plugged/README.rst
> .vim/plugged/Makefile
> .vim/plugged/autoload
> .vim/plugged/autoload/screen.vim
> .vim/plugged/plugin
> .vim/plugged/plugin/screen.vim
> .vim/plugged/doc
> .vim/plugged/doc/tags
> .vim/plugged/doc/screen.txt
>
> Plugged with:
> Plug 'ervandew/screen

So that corresponds to github.com/ervandew/screen

Best,
Christian
--
Es ist komisch, daß kein Mensch mit Esprit ein Glück möchte, das auf
Dummheit gegründet ist, und doch ist es klar, daß man dabei einen
guten Tausch machen würde.
                -- François Marie Voltaire

--
--
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.