Mathias Michaelis wrote:
If I do :!dir a console opens and says:
C:\WINNT\system32\CMD.EXE /c dir
shell returned -1
2) If 1) doesn't help, you may want to produce the phenomena outside
of vim. Open a cmd-window and type something like
path\to\vim\vimrun.exe
Bram
I'm not sure perror() can be used in general after system().
Otherwise it makes sense.
Thanks. Indeed I only checked the documentation of
Visual Studio 2005
Visual Studio .NET
Visual Studio 6.0
When making the patch. But by googling a little bit, I find firther
indications that
Juan Lanus wrote:
On 6/16/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Mathias Michaelis wrote:
If I do :!dir a console opens and says:
C:\WINNT\system32\CMD.EXE /c dir
shell returned -1
2) If 1) doesn't help, you may want to produce the phenomena outside
Hi all
If I do :!dir a console opens and says:
C:\WINNT\system32\CMD.EXE /c dir
shell returned -1
2) If 1) doesn't help, you may want to produce the phenomena outside
of vim. Open a cmd-window and type something like
path\to\vim\vimrun.exe %windir%\system32\cmd.exe /c dir
Hello Juan
The problem is that any ! command returns, for example !!dir returns (after a
couple seconds):
E485: Can't read file x.tmp
If I do :!dir a console opens and says:
C:\WINNT\system32\CMD.EXE /c dir
shell returned -1
Just some thoughts ...
1) In my _vimrc file, I
Juan Lanus wrote:
On 5/27/06, Suresh Govindachar wrote:
Start gvim using the command
p:\ath\to\gvim.exe -u NONE -U NONE --noplugin
In the resulting gvim, do
:set shellcmdflag=3D/k
Then :!ver
The name of the window is D:\vim\vim70\vimrun.exe and the
Suresh Govindachar wrote:
Juan Lanus wrote:
On 5/27/06, Suresh Govindachar wrote:
Start gvim using the command
p:\ath\to\gvim.exe -u NONE -U NONE --noplugin
In the resulting gvim, do
:set shellcmdflag=3D/k
Then :!ver
The name of the window is
On Fri, 26 May 2006, Juan Lanus wrote:
[snip]
The problem is that any ! command returns, for example !!dir returns (after a
couple seconds):
E485: Can't read file x.tmp
If I do :!dir a console opens and says:
C:\WINNT\system32\CMD.EXE /c dir
shell returned -1
Hit any key to close
On 5/26/06, Gerald Lai [EMAIL PROTECTED] wrote:
My first assessment would be to check if
C:\WINNT\system32\CMD.EXE
does exist. Does it?
Yes it does. I'm not at that PC now, but I assume it's there because I
can open DOS windows with the usual shortcut that points to
On Fri, 26 May 2006, Juan Lanus wrote:
On 5/26/06, Gerald Lai [EMAIL PROTECTED] wrote:
My first assessment would be to check if
C:\WINNT\system32\CMD.EXE
does exist. Does it?
Yes it does. I'm not at that PC now, but I assume it's there because I
can open DOS windows with the usual shortcut
Juan Lanus wrote:
... when I use the :! syntax a DOS window
containing the error shows.
Issue the : !dir and in the resulting DOS window,
issue the path command. The output will be what this
_particular_ dos window has for the path environment
variable.
Then directly open a
11 matches
Mail list logo
