vim_runtime: does someone use this...

[Sebastian Gödecke]

Hi, 

and could help me in clearify: i should have jedi.vim in the "plugins" folder "sourced_non_forked". so i think it should be running, but how could i check this? 

I get an error when opening e.g python files:

jedi-vim: Error when loading the jedi python module (module 'jedi' has no attribute '__version__'). Please ensure that Jedi is installed correctly (see Installation in the README.

How to handle with this?

regards Sebastian

--

Mit freundlichen Grüßen
Sebastian Gödecke

[Sebastian Gödecke]

Hi, 

nobody there?

I checked this twice, in my_config.vim are my default settings, but the settings wouldn't load. Additional in in the file i "set rnu" but this also wouldn't be set up. 

So how to start to "debug" this?

[Gary Johnson]

On 2023-02-09, 'Sebastian Gödecke' via vim_use wrote:
> Hi, 
> nobody there?
> I checked this twice, in my_config.vim are my default settings, but the
> settings wouldn't load. Additional in in the file i "set rnu" but this also
> wouldn't be set up. 
> So how to start to "debug" this?
>
>
> Am Di., 7. Feb. 2023 um 16:27 Uhr schrieb Sebastian Gödecke:
>
> Hi, 
> and could help me in clearify: i should have jedi.vim in the "plugins"
> folder "sourced_non_forked". so i think it should be running, but how could
> i check this? 
> I get an error when opening e.g python files:
> jedi-vim: Error when loading the jedi python module (module 'jedi' has no
> attribute '__version__'). Please ensure that Jedi is installed correctly
> (see Installation in the README.
>
> How to handle with this?
> regards Sebastian

I'm glad to help, but there's a lot in your explanation I don't
understand.

In my installation of Vim, there are no folders named "plugings" or
"sourced_non_forked". I don't know what folders you are referring
to.

What "config.vim" file are you referring to? The only files named
"config.vim" that I find in my Vim installation are these:

/usr/local/share/vim/vim90/ftplugin/config.vim
/usr/local/share/vim/vim90/indent/config.vim
/usr/local/share/vim/vim90/syntax/config.vim

Those are used to aid with editing files for configure scripts--they
are not used for configuring Vim. Vim's primary configuration file
is one of these:

On Unix:
~/.vimrc
~/.vim/vimrc

On Windows:
~/_vimrc
~/vimfiles/vimrc

See:

:help vimrc

Where exactly did you put jedi.vim? The traditional location for
plugins is the folder ~/.vim/plugin on Unix or ~/vimfiles/plugin on
Windows. See:

:help plugin

Recent versions of Vim and Vim plugin managers put plugins in
different directories, but I am not familiar with any of those. You
can find out more about Vim packages here:

:help packages

You can determine whether Vim has loaded your plugin by executing
the ":scriptnames" command and looking for config.vim and jedi.vim
in that list. See:

:help :scriptnames

That should get us started in figuring out what went wrong.

Regards,
Gary

[Sebastian Gödecke]

Hi Gary, yes you're right, my explanation wasn't as good as it had to be. 

I'm "trying" to use vim_runtime from here: 

https://github.com/amix/vimrc

so this adds the hole vim-files to ~/.vim_runtime/ and under this folder there are ALL-vimrelated files. There are plugins like the jedi-plug-in, ther NERDtree and many more are in ~/.vim_runtime/. Also there is a my_config.vim and in this there are my settings. So there is an option "set relativenumber" and other settings, but when i'm starting vim, the relativenumbers aren't shown, so i have to "set nu" and again "set rnu" than my rel-numbers are there. Closing vim, and starting it again my numbers are gone away. 

Further there is my jedi-vim and opening a python file there will be shown this message:

jedi-vim: Error when loading the jedi python module (module 'jedi' has no attribute '__version__'). Please ensure that Jedi is installed correctly (see Installation in the README.

But some words were highlighted and i don't know, why this were shown and where i have to search for solving this message. 

This is my vim"problem. I don't know, if my own ~/.vim-runtime/ related stuff would be used. the "regular" ~/.vimrc is linked to ~/.vim-runtime ....

Thanks Gary and regards Sebastian

--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230209211717.GH6446%40phoenix.

[Gary Johnson]

On 2023-02-09, 'Sebastian Gödecke' via vim_use wrote:
> Hi Gary, yes you're right, my explanation wasn't as good as it had to be. 
> I'm "trying" to use vim_runtime from here: 
> https://github.com/amix/vimrc
> so this adds the hole vim-files to ~/.vim_runtime/ and under this folder there
> are ALL-vimrelated files. There are plugins like the jedi-plug-in, ther
> NERDtree and many more are in ~/.vim_runtime/. Also there is a my_config.vim
> and in this there are my settings. So there is an option "set relativenumber"
> and other settings, but when i'm starting vim, the relativenumbers aren't
> shown, so i have to "set nu" and again "set rnu" than my rel-numbers are there.
> Closing vim, and starting it again my numbers are gone away. 
> Further there is my jedi-vim and opening a python file there will be shown this
> message:
> jedi-vim: Error when loading the jedi python module (module 'jedi' has no
> attribute '__version__'). Please ensure that Jedi is installed correctly (see
> Installation in the README.
>
> But some words were highlighted and i don't know, why this were shown and where
> i have to search for solving this message. 
>
> This is my vim"problem. I don't know, if my own ~/.vim-runtime/ related stuff
> would be used. the "regular" ~/.vimrc is linked to ~/.vim-runtime ....

Hi Sebastian,

Got it. Thanks for the explanation. I skimmed the README.md at
https://github.com/amix/vimrc, which included these commands under
"Install for your own user only":

git clone --depth=1 https://github.com/amix/vimrc.git ~/.vim_runtime
sh ~/.vim_runtime/install_awesome_vimrc.sh

I also read that script. Did you run the script? I see that it
overwrites your ~/.vimrc, which is a dumb thing for it to do without
warning the user. If you have your own ~/.vimrc, make sure you save
it before running that script.

The script creates a ~/.vimrc which adds the ~/.vim_runtime
directory to the end of your 'runtimepath', which will cause Vim to
source plugins from ~/.vim_runtime after it sources all the other
plugins in 'runtimepath'. That should be okay. The script also
causes Vim to source a number of Vim scripts before any others at
startup, including my_configs.vim, if it exists.

According to ":help vimrc", Vim will source $HOME/.vimrc before
$HOME/.vim/vimrc, so the ~/.vimrc that the install_awesome_vimrc.sh
created should indeed be the one that Vim sources at startup.

So, the first thing I would check would be to open your ~/.vimrc
file and verify that it is the one that the installation script
created.

Next, I would start Vim and execute :scriptnames to see what files
are actually being sourced. The files at the top of the list will
depend on which Linux distribution you're running (I am assuming
that you're running Linux) and whether you built Vim yourself. Near
or at the top of the list, you should see

~/.vimrc

followed immediately by

~/.vim_runtime/vimrcs/basic.vim
~/.vim_runtime/vimrcs/filetypes.vim
~/.vim_runtime/vimrcs/plugins_config.vim
~/.vim_runtime/vimrcs/extended.vim
~/.vim_runtime/my_configs.vim

and then by more files from the ~/.vim_runtime and /usr/share/vim or
perhaps /usr/local/share/vim directories.

Notice that your personal customizations should go into
my_configs.vim, spelled with an 's', not my_config.vim as you wrote
earlier.

Good luck, and let us know what you find out.

Regards,
Gary

[Gary Johnson]

On 2023-02-09, Gary Johnson wrote:

> Next, I would start Vim and execute :scriptnames to see what files
> are actually being sourced. The files at the top of the list will
> depend on which Linux distribution you're running (I am assuming
> that you're running Linux) and whether you built Vim yourself. Near
> or at the top of the list, you should see
>
> ~/.vimrc
>
> followed immediately by
>
> ~/.vim_runtime/vimrcs/basic.vim
> ~/.vim_runtime/vimrcs/filetypes.vim
> ~/.vim_runtime/vimrcs/plugins_config.vim
> ~/.vim_runtime/vimrcs/extended.vim
> ~/.vim_runtime/my_configs.vim
>
> and then by more files from the ~/.vim_runtime and /usr/share/vim or
> perhaps /usr/local/share/vim directories.

I didn't notice when I wrote that that the :scriptnames list may
also include plugins from your ~/.vim directory.

Regards,
Gary

[Enan Ajmain]

On Thu, 9 Feb 2023 22:36:37 +0100
'Sebastian Gödecke' via vim_use <vim...@googlegroups.com> wrote:
> Hi Gary, yes you're right, my explanation wasn't as good as it had to
> be. I'm "trying" to use vim_runtime from here:
> https://github.com/amix/vimrc

Better ask amix about amix's vimrc, no?

--
Enan
3nan....@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

[Sebastian Gödecke]

Am Fr., 10. Feb. 2023 um 06:43 Uhr schrieb Enan Ajmain <3nan....@gmail.com>:

On Thu, 9 Feb 2023 22:36:37 +0100
'Sebastian Gödecke' via vim_use <vim...@googlegroups.com> wrote:
> Hi Gary, yes you're right, my explanation wasn't as good as it had to
> be. I'm "trying" to use vim_runtime from here:
> https://github.com/amix/vimrc

Better ask amix about amix's vimrc, no?

For sure, i did it for about 3 Weeks? with no answer....

 

--
Enan
3nan....@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N

--
--
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+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230210114328.2f7d2e15%40cirdan.

[Sebastian Gödecke]

Hi, 

i read the README, but i didn't notice the s behind my_config.vim. I changend it now and when opening the python file, the Jedi message wasn't shown as big as befor, it were shown in the "footer", near statusbar.

But nevertheless when opening, it doesn't show me the linenumbers as configured...

i try to figure out ....

Regards Sebastian

 

Regards,
Gary

--
--
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+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230209230949.GI6446%40phoenix.