I have this line in my vimrc nnoremap :sp ~/.vimrc
#VIM DEVICNOS AFTER SOURCE VIMR UPDATE#
However, it still doesn't seem to update my vimrc. Now I've tried running source within Vim and it worked without errors. So as all of you have pointed out, I mixed up the Vim source and Bash source commands - Thanks. Linking: gcc -arch i386 -arch x86_64 -o vim -lncursesĬould anybody give me a hand here? Thanks so much! D_FORTIFY_SOURCE=0 -Iproto -DHAVE_CONFIG_H -arch i386 -arch x86_64 -g -Os -pipe +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmpĬompilation: gcc -c -I. toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title sniff +startuptime +statusline -sun_workshop +syntax +tag_binary python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent +path_extra -perl +persistent_undo +postscript +printer -profile -python +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape +insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent +find_in_path +float +folding -footer +fork() -gettext -hangul_input +iconv dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent
#VIM DEVICNOS AFTER SOURCE VIMR MAC OS X#
vimrc: line 7: ` call vundle#rc()'Īnd here's my Vim info (I'm running Mac OS X 10.7.3): VIM - Vi IMproved 7.3 (2010 Aug 15, compiled 19:27:29)Ĭompiled by version without GUI. vimrc: line 7: syntax error near unexpected token `(' So I followed the instructions at Vimcast which basically source vimrc every time you hit save.īut that doesn't work for some reason (when I save my vimrc it doesn't give any errors), so I decided to run source $HOME/.vimrc manually and here's what I got: -bash: Configuration file for vim Here I used the VimEnter event but you could also try the SessionLoadPost event :Īutocmd SessionLoadPost * source /path/to/custom_colors.I'm trying to get my Vim to update on the fly after editing vimrc. Since this file should be sourced after Session.vim, its settings should not be overwritten. There are many methods to disable it 0: Temporarily Disable To turn off highlight until next search, in exe mode: :noh1: Persistent Disable If you want to disable it completely: 1.0: For existing session/buffer: In exe mode: :set nohlsearch1.1: For all sessions/buffers: Put this in your. It may be a unwanted or even annoying thing. For example, something like this :Īutocmd VimEnter * source /path/to/custom_colors.vim After searching in Vim with / all occurences highlighted and this stays for a while. Write your custom highlight groups into a dedicated file (let's say custom_colors.vim) and then, inside your vimrc, add an autocmd that automatically source this file at the end of the startup. Saving the session or include it inside your vimrc : set sessionoptions-=optionsĪs a result, your sessionsoptions value will beīlank,buffers,curdir,folds,help,tabpages,winsize and your options You could use the following command before The options part is responsible for saving options (including the It's blank,buffers,curdir,folds,help,options,tabpages,winsize. Now, but you will have to do it again every time you create a newĬhange the value of the sessionoptions option. I don't know if it will work, but here are a few suggestions you could try :ĭelete this line from your Session.vim. So I suppose that when the set background=dark from your Session.vim is executed, your default theme is reloaded but not your custom colors because they are defined in a different place (your vimrc). Setting 'background' will cause the color scheme to be reloaded. When a color scheme is loaded (the "g:colors_name" variable is set) I think the reason why your default theme is loaded a second time when you source your Session.vim, is because the latter includes this line (83) : set background=dark The second time it's loaded, your custom highlight groups must be overwritten. Your last comment says that your default colorscheme is sourced twice : once before your custom highlight groups, and once after. Hi StatuslineWarning cterm=inverse ctermfg=210 gui=inverse guifg=#ff8787 Hi Modifier cterm=inverse ctermfg=118 gui=inverse guifg=#87ff00 Hi PmenuSel ctermfg=16 ctermbg=179 cterm=NONE Hi Visual ctermfg=186 ctermbg=64 cterm=NONE Hi StatusLineNC ctermfg=244 ctermbg=144 cterm=NONE Hi StatusLine ctermfg=16 ctermbg=179 cterm=NONE Hi Search term=reverse ctermfg=229 ctermbg=136 Hi CursorLine term=NONE cterm=NONE ctermbg=238 Hi PmenuSel guifg=black guibg=LightGoldenrod3 Hi StatusLine guifg=black guibg=LightGoldenrod3 The sessionoptions is blank,buffers,curdir,folds,help,options,tabpages,winsize. However after I mksession and sourced it back, I found that some (maybe all) of the custom highlights were lost and vim used the default settings of the colorscheme. I defined some highlights in the vimrc file and it works well in gvim.
0 kommentar(er)
