On Oct 6, 5:48 pm, Gary Johnson <[EMAIL PROTECTED]> wrote:
> On 2008-10-06, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
>
>
> > This doesn't seem to work. I've tried the following and the mouse
> > still jumps across the screen:
>
> > map <f3> :call system("time")<CR>
>
> > I believe the 'external' application I referred to in my original post
> > is called 'vimrun.exe'.
>
> > Other vimrc points of interest [which I forgot to include in the first
> > post]:
> > if has("win32")
> > set shell=c:\bin\bash
> > else
> > set shell=/bin/bash
> > endif
>
> > Cygwin is installed in the root [even though Cygwin screams about not
> > doing this... this was a mandated install location.]
>
> I tried a couple of experiments, too, including this:
>
> :set shell=C:\cygwin\bin\date.exe
> :set shellcmdflag=
> :echo system('')
>
> but the mouse pointer still moved. I found some discussion of the
> vimrun command here:
>
> :help win32-vimrun
>
> Here's an untested idea: Use Cygwin's run in place of Vim's vimrun.
> Rename vim's vimrun.exe to something else, then copy Cygwin's
> /bin/run.exe to where vimrun.exe was and name it vimrun.exe. I've
> used Cygwin's run command to start commands without the annoying DOS
> window in other situations--it just might work here.
>
> Regards,
> Gary
I tested copying the run.exe found in /usr/X11R6/bin/ over vimrun.exe
but this failed miserably. I didn't have a vimrun.exe anywhere else
[other than the win32 version]. I also tried compiling the
'vimrun.exe' as a 'gui' application using WinMain instead of the
simple 'main' but that doesn't seem to do anything [though I must
admit, I'm not familiar with 'windows' programming].
Does anyone know the history on why windows requires the 'vimrun.exe'
anyways? Something about handling Ctrl-C, but that's all I know.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
