Error Detected While Processing /etc/vim/vimrc
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 594 Star 12,916 Fork 1,560 VundleVim/Vundle.vim Code Issues 90 Pull requests error detected while processing root vimrc 42 Projects 0 Wiki Pulse Graphs New issue I got Error
Vim Error Detected While Processing Function
detected while processing /root/.vimrc: when I use VI instead of VIM #656 Closed davidius81 opened this Issue
Vim Error Detected While Processing Modelines
Oct 23, 2015 · 1 comment Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 1 participant davidius81 commented Oct 23,
Error Detected While Processing Vimrc
2015 Hi, I get this error while I use vi instead of vim? Did i miss someting? vim work well with all my pluging. # vi Error detected while processing /root/.vimrc: line 15: E492: Not an editor command: Plugin 'gmarik/Vundle.vim' line 18: E492: Not an editor command: Plugin 'elzr/vim-json' line 21: E492: Not an editor command: Plugin syntax.vim download 'godlygeek/tabular' line 22: E492: Not an editor command: Plugin 'plasticboy/vim-markdown' line 25: E492: Not an editor command: Plugin 'rodjek/vim-puppet' line 27: E492: Not an editor command: Plugin 'scrooloose/Syntastic' Press ENTER or type command to continue .vimrc set nocompatible " be iMproved, required filetype off " required " set the runtime path to include Vundle and initialize set rtp+=~/.vim/bundle/Vundle.vim call vundle#begin() " alternatively, pass a path where Vundle should install plugins "call vundle#begin('~/some/path/here') " let Vundle manage Vundle, required Plugin 'gmarik/Vundle.vim' "Plugin to highlight json syntax Plugin 'elzr/vim-json' "Markdown plugin Plugin 'godlygeek/tabular' Plugin 'plasticboy/vim-markdown' " Puppet syntax Plugin 'rodjek/vim-puppet' " Puppet Syntax valiator Plugin 'scrooloose/Syntastic' " All of your Plugins must be added before the following line call vundle#end() " required filetype plugin indent on " required " To ignore plugin indent changes, instead use: "filetype plugin on " " Brief help " :PluginList - lists configured plugins " :PluginInstall - installs plugins; append `!` to update or just :PluginUpdate " :PluginSearch foo - searches for foo; append `
#1 2012-06-10 19:33:28 MicroJoe Member From: France Registered: 2012-06-10 Posts: 14 Website [Solved][VIM] E484: Can't open file syntax.vim Hi all,I've installed Archlinux few error detected while processing vim bundle newl9 plugin l9 vim days ago on my netbook and yesterday i decided to syntax.vim not found configure Vim using plugins.During plugins configuration, i messed up and i decided to revome all vim command already exists add to replace it Vim files in my ~ folder in order to restart configuration.However, since I've executed the `rm -R .vim .vimrc .viminfo` command, I can't re-activate Vim's syntax https://github.com/VundleVim/Vundle.vim/issues/656 coloration using `syntax on` into my .vimrc file nor into Vim directly.Here is the error message when I start Vim :Error detected while processing /home/romain/.vimrc: line 1: E484: Can't open file /home/romain/.vim/syntax/syntax.vim Press ENTER or type command to continueI've found this topic on BBS which seems to be the same problem as https://bbs.archlinux.org/viewtopic.php?id=143087 me but reinstalling vim or vi doesn't solve this problem.I've tried to copy this syntax.vim file from /usr/share/vim/vim73/syntax/syntax.vim but it doesn't solve the problem and I want a clean solution without hacking my ~ folder ; moreover, this bug also appears being root while I haven't configured vim with the root account so it may be a problem into Vim's installation folders or something.Thanks for your help and sorry I my english contains mistakes,MicroJoe. Last edited by MicroJoe (2012-06-14 16:16:45) Offline #2 2012-06-10 19:43:23 Trilby Forum Moderator From: Massachusetts, USA Registered: 2011-11-29 Posts: 14,324 Website Re: [Solved][VIM] E484: Can't open file syntax.vim That's odd - you shouldn't need anything in your home directory for syntax highlighting to work. I have an empty directory tree and it works fine.Can you post (or pastebin) your ~/.vimrc Interrobang • Slider• How's my coding? See this page.• How's my moderating? Feel free to email any concerns, complain
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://unix.stackexchange.com/questions/61799/utilize-a-different-users-vimrc-as-well-as-vim-folder workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; error detected it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Utilize a different user's vimrc as well as vim folder up vote 4 down vote favorite 3 First of all, to prevent an X/Y Problem, I'll just state that what I error detected while really want is: Run vim as the root user. Instruct vim to use my nice pretty color scheme and all my plugins. Do all this without contaminating the /root/.vimrc or the /root/.vim folder. Do all this without running sudo vim hopefully... I have my own account on each linux server with the following two files. /home/b/.vim My folder with my plugins etc. /home/b/.vimrc My dot vimrc file Here is my first try running with my custom vim settings: vim -u ~b/.vimrc Error detected while processing /root/.vimrc: line 33: E185: Cannot find color scheme railscasts line 82: E117: Unknown function: ... Press ENTER or type command to continue However, my .vimrc file is searching for a plugin which only exists in my /home/b/.vim folder. Up until now I have always copied my own /home/b/.vim folder to the root user's area like so: cp -r /home/b/.vim /root But unfortunately this contaminates the root account's home folder, and I want to stop doing that (if possible). Can anyone tell me an environment variable, or any trick at all, to run with my own COMP