John Little wrote: > On Nov 10, 6:57 pm, Ben Schmidt <[EMAIL PROTECTED]> wrote: >> ... it should check if what it gets >> back is the same as what it sent, and assume no matches if it is. > > That wouldn't work, that assumption may be false, there might be a > match.
True. I thought it would only rarely if ever be false, but actually, now I think about it, it could be quite common. A question mark in particular often occurs in filenames. Though you could argue it is incorrect to use a pattern like filename? to search for the file that is rightly referenced as 'filename\?', it is possible, and I expect not all that unlikely, particularly on the commandline (as opposed to in a script where things are more likely to be properly escaped). I guess there's nothing for it but to check the output from the shell, and if it matches the input, check for existence of a file with exactly that name to decide whether to return it unchanged or return an empty list/string. Ben. > On Nov 10, 7:58 pm, StarWing <[EMAIL PROTECTED]> wrote: >> it's okay in windows..... > > Yes, I discovered it last year when I took a script working in Windows > to various unices. The script renames the backup file from x.y~ to > x.yy.mm.dd_hh.mm.ss.y in a BufWritePost auto command, giving VMS-like > warm fuzzies. > > Regards, John --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
