> I'm trying to set up 'path', but it does not work as expected,
> I'd like to set it up to search in directories
> there is problem with **/ sequence, **\\ should be used instead.
> Is this a bug or a feature?
Vim should support using / as path separator everywhere. Backslashes
> I've found it in both Vim 6.3.86, and 7.0aa.
Please give details about the way Vim was compiled.
If the Universe is constantly expanding, why can't I ever find a parking space?
> Marian Csontos wrote:
>> I'm trying to set up 'path', but it does not work as expected,
>> I'd like to set it up to search in directories
>> there is problem with **/ sequence, **\\ should be used instead.
>> Is this a bug or a feature?
> Vim should support using / as path separator everywhere. Backslashes
> are confusing.
>> I've found it in both Vim 6.3.86, and 7.0aa.
> Please give details about the way Vim was compiled.
I'm using Tony's 6.3.86, my system is WinXP SP1:
VIM - Vi IMproved 6.3 (2004 June 7, compiled Jul 29 2005 16:23:08)
MS-Windows 32 bit GUI version with OLE support
Included patches: 1-86
Compiled by [hidden email] Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+comments +cryptv +cscope +dialog_con_gui +diff +digraphs -dnd -ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand
+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds
+menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn
+multi_lang +netbeans_intg +ole -osfiletype +path_extra +perl/dyn
+printer +python/dyn +quickfix +rightleft +ruby/dyn +scrollbind +signs
+smartindent -sniff +statusline -sun_workshop +syntax +tag_binary
-tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title
+toolbar +user_commands +vertsplit +virtualedit +visual +visualextra
+vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return
-malign-double -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG
-DWINVER=0x0400 -D_WIN32_WINNT=0x0400 -DFEAT_PERL -DDYNAMIC_PERL
-DDYNAMIC_PERL_DLL="perl58.dll" -DFEAT_PYTHON -DDYNAMIC_PYTHON
-DDYNAMIC_PYTHON_DLL="python24.dll" -DFEAT_RUBY -DDYNAMIC_RUBY
-DDYNAMIC_RUBY_DLL="msvcrt-ruby18.dll" -DDYNAMIC_RUBY_VER=18 -DFEAT_TCL
-DDYNAMIC_TCL -DDYNAMIC_TCL_DLL="tcl83.dll" -DDYNAMIC_GETTEXT
-DDYNAMIC_ICONV -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE
-DFEAT_NETBEANS_INTG -DFEAT_OLE -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -mcpu=i386
-march=i386 -Iproto -I/cygdrive/c/Perl/lib/CORE
-I/cygdrive/c/ruby/lib/ruby/1.8/i386-mswin32 -I/cygdrive/c/ruby/include -s
Linking: gcc -s -o gvim.exe -luuid -lole32
/cygdrive/c/ruby/lib/tclstub83.lib -lwsock32 -loleaut32 -lstdc++ -mwindows
Maybe I should be more verbose too:
When I try using
it end with message E343. It could be solved by using **\\, instead of
works well. But the first case should work too.
And it doesn't work neither with
gvim -u NONE -U NONE
________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.