On 06/12/09 05:30, Ben Goldberg wrote:
> On Sat, Dec 5, 2009 at 6:01 AM, Tony Mechelynck
> <[email protected] <mailto:[email protected]>> wrote:
>
> On 17/11/09 19:52, bgold12 wrote:
>
>
> 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
>
>
> That's the 7.2.000 build, compiled (IIUC) with Microsoft Visual C.
>
> - $PATH is an environment variable, limited only by the size of the
> environment memory. Do you see the same problem with other programs
> than Vim?
> - There have been more than 300 bugfixes since that version of Vim
> was published. Do you still have the problem with the latest Vim
> distribution at http://sourceforge.net/projects/cream/files/ ?
>
>
> Best regards,
> Tony.
> --
> Prof: So the American government went to IBM to come up with a data
> encryption standard and they came up with ...
> Student: EBCDIC!"
>
>
> I haven't seen this problem with programs other than vim, and I just
> installed the latest distribution, and it didn't fix it.
>
> However, I have found that the problem only shows itself when I set
> $PATH from within vim to a list of unix-style paths separated by colons.
> The curious thing is that everything works fine until the length of
> $PATH exceeds 259 characters. The problem is fixed if I use
> windows-style paths. I'm not sure why.
I don't know why native-Windows [g]vim would honor (short) Unix-style
$PATH settings, but you shouldn't have expected that it would. On
native-Windows Vim, $PATH should use native-Windows conventions, i.e.,
semicolon-separated list. (Cygwin Vim would be expected to follow Unix
conventions, of course.)
>
> On a mostly unrelated point, I ran into a brief difficulty while testing
> this problem, which turned out to be the fact that shellxquote is
> apparently not "adjusted according the value of 'shell'" (as indicated
> in the documentation) if you set 'shell' from the vim command line, as
> opposed to setting it through the vimrc file. To compound the problem,
> when shellxquote is actually adjusted according to the value of 'shell',
> the adjusted value doesn't show up in the :set command. I'm assuming
> this is because the actual "default" of the shellxquote option is
> adjusted, so the adjusted value actually doesn't differ from the
> (adjusted) default. This is confusing, in my humble opinion. The end
> result was that I was running :! commands for a while with an incorrect
> shellxquote value, without realizing it. May I tentatively suggest that
> it would be simpler and less confusing to never adjust the defaults for
> options?
The value will show, but I'm not sure Vim will say where it was set, if
you use
:verbose set sxq?
It will also be displayed along with all other settings, if you do
:set all
The fact that the _default_ is adjusted according to the value of
'shell', is documented. If this adjustment only occurs at startup, I
don't know if I must call this a bug or a feature -- you aren't expected
to change your shell "under Vim", so to speak, and if it wrongly guesses
what you got, the right time to tell Vim the right value is at startup,
in your vimrc.
>
> Thanks for looking into this,
>
> Ben
BTW, please start a different thread when talking about a different
problem next time.
Best regards,
Tony.
--
The STAR WARS Song
Sung to the tune of "Lola", by the Kinks:
I met him in a swamp down in Dagobah
Where it bubbles all the time like a giant cabinet soda
S-O-D-A soda
I saw the little runt sitting there on a log
I asked him his name and in a raspy voice he said Yoda
Y-O-D-A Yoda, Yo-Yo-Yo-Yo Yoda
Well I've been around but I ain't never seen
A guy who looks like a Muppet but he's wrinkled and green
Oh my Yoda, Yo-Yo-Yo-Yo Yoda
Well I'm not dumb but I can't understand
How he can raise me in the air just by raising his hand
Oh my Yoda, Yo-Yo-Yo-Yo Yoda, Yo-Yo-Yo-Yo Yoda
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
