-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors installing and afterwards #19
Comments
Hi Omer, thanks for feedback.
" 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.
I hope this solves all the issues you've experienced. |
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. 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 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. |
Quick questions:
|
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. But I still get this error:
After disabling it at Can you try double clicking anywhere on screen when a file is open? |
Yep. Before removing /vim folder I managed a successful install by removing
Fixing those might result in a better adaptibility. As for the mouse issue,disabling that line did help prevent vim losing sanity. |
Weird, that's the first thing being set in config/general.vim... |
@rafi , Well. 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... |
Fixed |
Hi,
I had a real old copy of your config and I wanted to upgrade it.
Turns out you changed the whole setup (:
But I'm having troubles with the new version.
First, I cleaned all .vim* and related files in my home and home/.cache folders.
Then I went with your installation steps
I had to replace vim with vim-nox since my repo-downloaded vim didn't have lua or python support in it.
1- Having to use SPACE + ENTER during installation due to "more" command is a drag.
2- Right after installing, even before using vim I have this error on my console:
3- Then I tried opening the file to check what's inside and got a brand new error.
4- When you click Enter to that message, you're presented with another one:
I did open that file afterwards.
Then I tried another file.
I must admit, it does have a a sleek theme and I liked it. But after a quick glance and compared to your old version, I found out that there's some stuff that's rather disturbing as well.
Autocomplete function does mess with using TAB.
When you double click mouse, it does insert random strings here and there AND it the search function went ballistic on me. Tried searching for whatever I don't know, added error lines in the file I was working on.
Again, with using mouse, I tried to copy some part of the text since I wanted to copy it.
Well, turns out I can't. I started seeing "Invalid register name" errors on the command section. Starting from whatever and continuing with many other error messages E354, E348 etc.
Furthermore, The bottom left area where you show the name of the file has an error where it shows the name of
config/vimrc as confi/vimrc
I think you should try a clean install and see all those errors for yourself.
I admit.... Right now it's not of much use to me and the old one seems safer to use.
The text was updated successfully, but these errors were encountered: