On 2016-01-20, James McCoy wrote: > On Tue, Jan 19, 2016 at 10:52:07AM -0800, Gary Johnson wrote: > > On 2016-01-19, Bram Moolenaar wrote: > > > James McCoy wrote: > > > > > > Why does the behavior differ? Shouldn't it be consistent? > > > > > > > > Both Windows and UNIX asked you to have a file with a space in the name. > > > > In fact, :argedit's help calls out that only one filename is allowed. > > > > > > Yeah, this has a long history. On Unix: > > > :edit a b > > > Gives an error. On MS-Windows you edit the file "a b". > > > This is explained above ":he wildcard". > > > > > > We can't change it on MS-Windows without breaking things. > > > > > > Could we change this on Unix? Currently it's an error, so one might > > > think it would not cause a problem. It's as simple as removing the check > > > for SPACE_IN_FILENAME. Although there is some other code when searching > > > for NOSPC. > > > > > > The main problem will be trying to use ":edit one.c two.c", expecting to > > > edit two files. Now you get an error, after the change you just edit a > > > file with a weird name. > > > > On Unix, a space is a separator. Spaces in file names require > > quoting. I don't think Vim should violate that convention here just > > because it can. It would be horribly inconsistent. > > Isn't it already inconsistent? ':edit' and ':argedit' only accept a > single argument. On UNIX builds of Vim, the spaces in in that single > argument have to be escaped but on Windows they don't.
Yes, but there's a difference between the number of arguments accepted and how those arguments are parsed. I don't see any problem with different commands accepting different numbers of arguments, but different commands parsing their file name arguments differently is not a good idea. I think that making that exception for Windows was a mistake. It's too late to change that now, but we can avoid making the situation worse. Regards, Gary -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
