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
--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230209230949.GI6446%40phoenix.
No comments:
Post a Comment