Hi Brett, unfortunately my programming skills is somewhat limited. How do I modify the Makefile to include the mentioned prepocessor macro? Would a selfcompiled vim include this macro? output from :ver VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Aug 24 2009 20:05:51) Included patches: 1-245 Compiled by <[email protected]> Huge version with GTK2 GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd - ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile +python +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/ include/gt k-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/ cairo -I/u sr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/ include -I/usr/i nclude/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 - O2 -D_FORTI FY_SOURCE=1 -D_REENTRANT -D_GNU_SOURCE -I/usr/local/include - D_LARGEFILE_SOUR CE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.10.0/i486-linux-thread- multi/CORE -I/usr/include/python2.6 -pthread Linking: gcc -Wl,-E -L/usr/lib -L/usr/local/lib -o vim -lgtk- x11-2.0 -lgdk-x 11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 - lpangocairo-1.0 -lcai ro -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 - lglib-2.0 - lXt -lncurses -lacl -lgpm -Wl,-E -L/usr/local/lib -L/usr/lib/ perl5/5.10.0/i48 6-linux-thread-multi/CORE -lperl -lcrypt -lutil -lc -L/usr/lib/ python2.6/config - lpython2.6 -lutil -lm -Xlinker -export-dynamic
regards Peter On 20 Jan, 14:21, Stahlman Family <[email protected]> wrote: > Peter Berntsen wrote: > > Running 7.2.245 under Slackware Linux 13.0 and I have noticed that > > my .vimrc file doesn't seem to be read. For example to not keep a > > backup file I comment out the code for that in the vimrc file like > > this. > > "if has("vms") > > " set nobackup " do not keep a backup file, use versions > > instead > > "else > > " set backup " keep a backup file > > "endif > > > this only works when it is done in the /usr/share/vimrc file and not > > if it is done in the ~/.vimrc file. > > Is there something I have overlooked or is this a bug in version > > 7.2.245? > > Peter, > I notice the following preprocessor macro in feature.h: USR_VIMRC_FILE. > A quick glance at the source seems to indicate that it will be set to > $HOME/.vimrc (for Unix anyway) if it's not overridden. This preprocessor > macro is not even mentioned in the Makefile, and the helpfile doesn't > indicate that $HOME/.vimrc is configurable, so I'm guessing that > USR_VIMRC_FILE is not intended to be overridden casually. Although it > seems a bit strange (at least for a distribution not designed to be used > in a corporate environment), I suppose it's possible that the creators > of your distribution overrode USR_VIMRC_FILE to point to a system-wide > .vimrc. If so, I would suspect (but haven't verified) that you could > tell it from the output of :version. > > Hope it helps... > Brett Stahlman > > > > > regards Peter
-- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
