Suresh Govindachar yahoo.com> writes:
> Juan,
>
> When you wrote:
>
> > The string "C:\WINNT\system32\cmd.exe \e:8192"
> > is my COMSPEC variable, ...
>
> Is the \e (rather than /e) an email typo or real typo?
It's a DOS flag indicator, a forward slash "/".
I think that using this no
lly how gvim is failing to select the shell option
before anything else. Now I'll be able to sleep.
Thanks Gerald.
--
Juan Lanus
TECNOSOL
Argentina
Test case, for Windows NT:
gvim fails to use the shell option in ! commands
1- Add a flag to the COMSPEC system variable, for example /E:8192
2
owledge. I blame
vimrun.exe (sorry Vince) but it's so innocent, so simple that even I can read it
(I'm a VB/SQL/COBOL/FORTRAN/JS/Java programmer). I just needed a subject.
Saludos! And many thanks to all.
--
Juan Lanus
TECNOSOL
Argentina
file with gvim I can do
:set encoding=cp850
and all gibberish becomes what it should be, on screen.
Upon saving, the file will be written with DOS encoding.
Peter, this is all my knowledge and beyond. Maybe it's useful for you to start a
research.
Good luck!
--
Juan Lanus
TECNOSOL
Argentina
move around the line, I find it much safer than repeated
arrows or spacebar touchs because these commands take me safely to the desired
point "programmatically" instead of "by hand".
--
Juan Lanus
TECNOSOL
Argentina
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
%SystemRoot%\system32
Hi,
Need help, after so many time I still can't fix this.
http://permalink.gmane.org/gmane.editors.vim/22144
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
