I got the executable from http://www.vim.org/download.php, the PC: MS-
DOS and MS-Windows Self-installing executable.
Here's the ":version" output from my console vim:
:version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Aug 9 2008 18:40:30)
MS-Windows 32-bit console version
Compiled by b...@kibaale
Big version without 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 +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra
+extra_search +farsi
+file_in_path +find_in_path +float +folding -footer +gettext/dyn -
hangul_input +iconv/dyn
+insert_expand +jumplist +keymap +langmap +libcall +linebreak
+lispindent +listcmds +localmap +menu
+mksession +modify_fname +mouse -mouseshape +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 -tgetent -termresponse
+textobjects +title -toolbar
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore
+wildmenu +windows +writebackup -xfontset -xim -xterm_save -xpm_w32
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"
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -
DFEAT_CSCOPE /Wp64 -DWIN
VER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjC/ /Ox -DNDEBUG /Zl /MT -
DDYNAMIC_ICONV -DDYNAMIC_GETTEXT
-DFEAT_BIG /Fd.\ObjC/ /Zi
Linking: link /RELEASE /nologo /subsystem:console oldnames.lib
kernel32.lib advapi32.lib shell32.lib
gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /
nodefaultlib libcmt.lib user32.lib
/PDB:vim.pdb -debug
Thanks,
Ben
On Nov 17, 6:09 am, Bram Moolenaar <[email protected]> wrote:
> bgold12 wrote:
>
> What is your name?
>
>
>
> > I recently added a couple of directories to my path and then found
> > that the command-line shell command (i.e. ":!ls") stopped working.
> > More specifically, the shell didn't seem to be able to find any of my
> > cygwin or otherwise utilities. I have been able to identify that when
> > my $PATH is 259 characters or less in length, there is no problem, but
> > when I add that 260th character, suddenly the $PATH variable becomes
> > empty in the spawned shell. In other words, when I run the command ":!
> > echo $PATH", I see a blank line (only when $PATH is 260 characters or
> > greater).
>
> > This problem only seems to be present when I use the MS-Windows 32-bit
> > console version of vim with bash as my shell. I'm currently using the
> > following settings:
>
> > set shell=/bin/bash
> > set shellcmdflag=-c
> > set shellslash
> > set shellredir=>%s\ 2>&1
>
> > This seems like a bug to me, but correct me if I'm wrong.
>
> It probably depends on the compiler, what maximum path length it
> supports. Where did you get the executable? The ":version" output
> would be useful.
>
> --
> Hanson's Treatment of Time:
> There are never enough hours in a day, but always too
> many days before Saturday.
>
> /// Bram Moolenaar -- [email protected] --http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features --http://www.Vim.org/sponsor/\\\
> \\\ download, build and distribute --http://www.A-A-P.org ///
> \\\ help me help AIDS victims --http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
