Re: AW: opening filename beginning with # - win32
- Wednesday, March 28, 2001, 06:43:14 PM, you wrote:
csdd> Thus wrote Alvin (lvn@...) on :
>> Hello ...csdd> Iirc this is a Windows standard sfile selection bix of a kind, right?
>> 1) :browse e works ok
csdd> If so, I think the picking of the file (name) is handled by the OS
csdd> and, I assume, vim treats the filename literally.
not sure what you mean but this is a `.log` file. if you mean that
`.log` file is handled by windows, then i think its yes.
>> 2) :e <drive>:\directory\#filename.ext does not work. i.e. samecsdd> Note that # is treated specially in filenames (expands to name of
csdd> alternate buffer, if set). Thus you need to escape it, which is done
csdd> with '\#' above. So the above command should edit a literally file
>> problem _but_ if <drive>:\directory\\\#filename.ext, its ok.csdd> Yep. You correctly escaped the # and added a '\\' for the single '\'
csdd> path seperator. Not sure, but I think you can use '\\' for '\' at any
csdd> time, but vim, on OS'es that use '\' as path seperator, will help you
csdd> a bit and assume that an unescaped '\' should usually be a seperator.
csdd> In some cases, like % and #, these may have to be escaped, so the
csdd> helpfulness before such a character is not good and you don't get it
csdd> (get it? :-).
ok... on using '\\\#filename.log, its ok. on using
'\\#filename.log, its not. i just now know that if i do:
it also works; which i think is the equivalent of '\\\'.
>> 3) oops... no `alias`csdd> ??
>> 4) double-click and/or `edit` from explorer does not work either withcsdd> Here the file name is handed to vim as a parameter on start up and it
>> same problem
csdd> will do the expansion.