Errors installing and afterwards about vim-config HOT 9 CLOSED

Hi Omer, thanks for feedback.
I've changed the plugin manager because Shougo discontinued neobundle.vim development and started working exclusively on dein.vim, which is the most sophisticated plugin manager out there currently.

1. Are you using Vim or Neovim? What OS are you using? Indeed the initial setup is a drag. Hopefully I fixed the "More" issue in Vim.
2. The problem with color-scheme is annoying, I haven't been able to fix it yet. I'll come up with something, but as far as I tested, the 2nd time you run vim, it works without errors. Try running :call dein#clear_state() and restart vim to clean dein's state cache.
3. The issue with itchyny/vim-parenmatch is weird. You can try disabling it in config/plugins.vim and let me know.
4. This makes me feel your clone of my vim-config isn't up-to-date.
5. Autocomplete: For Neovim, I'm using the new feature-full deoplete.vim, and for Vim - neocomplete.vim. I fixed an issue that might have prevented neocomplete to work.
6. Copying text with mouse: This might not be related to Vim at all. What terminal emulator are you using?
7. The bottom area is truncated by design. You can configure how many characters max. to leave there with:

" Tabs: Maximum number of directories in file path
let g:blk_tab_display_max_dirs = 1
" Tabs: Maximum number of characters in each directory
let g:blk_tab_display_max_dir_chars = 8

" Statusline: Maximum number of directories in file path
let g:blk_filename_max_dirs = 3
" Statusline: Maximum number of characters in each directory
let g:blk_filename_max_dir_chars = 5

I've updated configuration and tested with a clean install in vim & neovim.

1. Please update my changes with git pull
2. Delete the ~/.cache/vim/dein directory, or run :call dein#clear_state() inside vim
3. Now run vim +q or nvim +q

I hope this solves all the issues you've experienced.

from vim-config.

Hi @rafi ,

Thanks for the detailed explanation.

First of all yeah, I should've mentioned it.

1- I'm using Debian Jessie but tested it on Ubuntu and Linux Mint as well. Same result.
I'm using plain vim but since it doesn't have Lua, I installed vim-nox package to satisfy the dependency.

2- Will try the command if I can get the newer version to run. The freshly updated installer greets us with a brand new error this time ^^

Though on one of the boxes I was trying which had the version I tried a few days ago, I didn't have the color scheme error anymore, so yeah maybe opening second time is the charm for that.

Update: I re-installed it again. It still didn't work. But on my Ubuntu system it started installing Shougo, pluginsand dein without errors, Also, I created a new user on my Debian Jessie, I even removed all the /etc/skel files copied there and removed every dotfile but the result was the same. Strange.

3- Since I can't make a fresh install anymore, I can't try fixing the parenmatch error either.

4- Nope, I do have an old copy of your config indeed but that's on another machine. All my tries were done after running the command rm -rf .cache/vim .vim*

And this message is persistent. Everytime I open a file to edit with vim, it's popping up before the display of the contents.

5- ...

6- On the terminal front, I'm using XShell5 to connect to my servers. But I doubt it has anything to do with it. But for some reason with your vim-config, I'm unable to select and copy text. With other configs I don't have this trouble.

PS: On the Ubuntu system I managed to install it, it did start without errors. I didn't have unite.vim and vimfiler.vim related errors either.

I'll tinker more when I have time.

Also, when I try to select text, your config does try to do searching and that results in unwanted text entries. Check the mp4 file in the zip for a better understanding and know that my Keyboard wasn't touched unless I typed some message which you can see. Also, when the search process starts, it keeps going for a while.

2016-05-02_12-02-23.zip

from vim-config.

Quick questions:

1. Do you have a root folder /vim?
2. Do you have $XDG_CONFIG_HOME environment variable set? Try running echo $XDG_CONFIG_HOME to see if there's any output.

from vim-config.

Quick reply:

1- Strange. One of the scripts I was trying mistakenly created a /vim folder I guess. Indeed I had one. I removed that and tried a fresh install. Makes me feel like stupid for not checking. ^^

Now it works. I don't get any --more-- screens either. I installed the plugins.
After the end I did get the hybrid message; as expected, at my next start it was gone.

But I still get this error:

Error detected while processing /root/.cache/vim/dein/.dein/plugin/parenmatch.vim:
line   21:
E216: No such group or event: OptionSet matchpairs call parenmatch#setup()
Press ENTER or type command to continue

After disabling it at config/plugins.vim file that message is gone as well.
Before your last update, I was getting unity.vim and vimfiler.vim errors now they're gone as well.

Can you try double clicking anywhere on screen when a file is open?
And try selecting any word. ^^

from vim-config.

Great. I'll change these lines to relate to current file path possibly..

Regarding the mouse issue, what terminal are you using? Can you try disabling this line?

from vim-config.

Yep.

Before removing /vim folder I managed a successful install by removing

if isdirectory($XDG_CONFIG_HOME.'/vim')
let $VIMPATH=expand('$XDG_CONFIG_HOME/vim')
let $VARPATH=expand('$XDG_CACHE_HOME/vim')
else

Fixing those might result in a better adaptibility.

As for the mouse issue,disabling that line did help prevent vim losing sanity.
Also unless I use :set mouse=v copy function doesn't work.

from vim-config.

Weird, that's the first thing being set in config/general.vim...

from vim-config.

@rafi ,

Well. :set mouse=vi or :set mouse=r does work but normal mode prevents copying when I'm remote connected.

Now I tried it with XShell5 and MobaXterm. XShell doesn't allow it when mode is set to nvi but MobaXterm doesn't care. I'm not sure which one is doing the right thing.

But on XShell5, nvi mode acts like I'm Shift+clicking text on word. Just in case, I notified them of the problem but...

from vim-config.

Fixed XDG_CONFIG_HOME when empty with b8d6544

from vim-config.