Hi,
Andy Wokula wrote:
> Am 15.02.2012 19:36, schrieb Andy Wokula:
>> Am 15.02.2012 17:22, schrieb Ben Fritz:
>>>> New settings:
>>>> shellcmdflag: /c
>>>> shellxquote: (
>>>> and escape special chars with `^'.
>>>
>>> So you're saying, we must escape all special characters, INCLUDING
>>> QUOTES, and surround in parentheses?
>>
>> Yes, including quotes!
>>
>>> That's...special.
>>
>> But solves all problems so far.
>
> Please, somebody with a Windows 7 / Vista / Win 2003 machine:
>
> Does the following edit new&file.txt ?
>
> cmd /c (notepad ^"new^&file.txt^")
>
> It works here on good ol XP.
on a German Windows 7 64-bit it does, too. Notepad opens, showing a
dialog with
Die Datei new&file.txt kann nicht gefunden werden.
Möchten Sie eine neue Datei erstellen?
Ja Nein Abbrechen
which translates to
The file new&file.txt could not be found.
Do you want to create a new file?
Yes No Cancel
Answering "Ja" puts a new file named new&file.txt in the current
directory.
> I suspect that shell quoting has changed since:
> Is it ok to escape the double quotes?
>
> And, similar,
> Does the following output the contents of new&file.txt ?
> cmd /c (type ^"new^&file.txt^")
>
> or does it output something like
> Error, not a command: "file.txt")"
>
> The error case would be awful.
No error here, the file is correctly displayed. Also deleting it with
cmd /c (del ^"new^&file.txt^")
works.
Regards,
Jürgen
--
Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe is that none of it has tried to contact us. (Calvin)
--
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
