Hi, Bram I hope your working for this topic. I guess that some or many people in the world who use vim on windows are confusing.
Thanks. - Yasuhiro Matsumoto On Thu, Jan 15, 2009 at 8:06 AM, Yasuhiro MATSUMOTO <mattn...@gmail.com> wrote: > Yes thats all. thanks > > On 1/15/09, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: >> On 14/01/09 22:13, Bram Moolenaar wrote: >>> >>> Yasuhiro Matsumoto wrote: >>> >>>> On Wed, Jan 14, 2009 at 6:51 PM, Yasuhiro MATSUMOTO<mattn...@gmail.com> >>>> wrote: >>>>> On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck >>>>> <antoine.mechely...@gmail.com> wrote: >>>>>> On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote: >>>>>>> Hi all. >>>>>>> >>>>>>> It seems that quoting arguments of shebang command depend on >>>>>>> shellslash. >>>>>>> but on windows, cmd.exe or command.com can't treat single quote. >>>>>>> >>>>>>> --- test.vimrc --- >>>>>>> set nocompatible >>>>>>> set shellslash >>>>>>> ---------------------- >>>>>>> >>>>>> cmd.exe and command.com also can't handle the forward slash as a path >>>>>> separator, so you shouldn't set 'sellslash' if you're using them. The >>>>>> single quote is to be used when using a Unix-like shell on Windows >>>>>> (and, >>>>>> unlike what you seem to be assuming, a Unix-like shell can be used on >>>>>> top of cmd.exe or command.com, in which case $COMSPEC will be set to >>>>>> the >>>>>> Dos/Windows shell, not the Unix-like shell). >>>>> Hmm. >>>>> No. cmd.exe can treat the forward slash as path separator. And >>>>> shellslash had working good on windows with older version. >>>>> I guess this is a bug or grade down. >>>>> still more, netrw can't treat shellshash correctly on latest version. >>>>> >>>>> :e http://www.google.com/ >>>>> >>>>> the buffer name will be broken like a following with noshellslash. >>>>> >>>>> http:\\www.google.com\ >>>>> >>>>> Many users hope to use shellslash on windows. >>>> Or how about below? >>> >>> We didn't think of people using 'shell' set to "cmd.exe" and also >>> setting 'shellslash'. OK, so some people do use that. >>> >>> I wonder why you get the value of COMSPEC? Isn't it sufficient to >>> compare the tail of 'shell' to "cmd.exe"? We could also check >>> "command.com", just in case. And I think "cmd", without ".exe", also >>> works. >>> >> >> Then there are third-party shells like 4NT.EXE etc. Couldn't you just >> check that the value of $SHELL (minus a possible case-insentitive .exe >> or .com at the end if there is one) ends in "sh" (indicating a Unix-like >> shell) or in anything else (indicating a Dos-like shell), and maybe >> fallback to $COMSPEC if $SHELL is unset? >> >> >> Best regards, >> Tony. >> -- >> Dear Mister Language Person: What is the purpose of the apostrophe? >> >> Answer: The apostrophe is used mainly in hand-lettered small business >> signs to alert the reader than an "S" is coming up at the end of a >> word, as in: WE DO NOT EXCEPT PERSONAL CHECK'S, or: NOT RESPONSIBLE FOR >> ANY ITEM'S. Another important grammar concept to bear in mind when >> creating hand- lettered small-business signs is that you should put >> quotation marks around random words for decoration, as in "TRY" OUR HOT >> DOG'S, or even TRY "OUR" HOT DOG'S. >> -- Dave Barry, "Tips for Writer's" >> > > > -- > - Yasuhiro Matsumoto > -- - Yasuhiro Matsumoto --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---