[Vimoutliner] Fwd: vimoutliner patch

[Steve Litt]

On Thursday 31 August 2006 05:04 am, Peter Princz wrote:
> On 31/08/06, Peter Princz <princzp at gmail.com> wrote:
> > On 31/08/06, Steve Litt <slitt at troubleshooters.com> wrote:
> > > Hi all,
> > >
> > > I just got this. I don't understand what a quiet execution is, or how
> > > it differs from normal executable lines. Any ideas?
> > >
> > > SteveT
> > >
> > > ----------  Forwarded Message  ----------
> > >
> > > Subject: vimoutliner patch
> > > Date: Wednesday 30 August 2006 08:05 pm
> > > From: Brian Lewis <bsl04 at uark.edu>
> > > To: slitt at troubleshooters.com
> > >
> > > I submitted something like this a long time ago, but it didn't get
> > > accepted. It adds _exeq_ (quiet execution) support.
> >
> > ...
> >
> > Hi Steve,
> >
> > I got it.
> > It prepends :silent before the !, when recognises the _exeq_ token
> > instead of _exe_.
> >
> > This is the key:
> > original: let command="!".command
> > patch:  let command="silent !".command
> >
> > Consult  :help :silent to see what exactly it does.
> > Makes sense on Windows at least when you don't want windows to bubble
> > up just to be closed. :)
> >
> > Have a nice day,
> >   Peter
>
> Steve and list,
>
> I just applied the patch (had to do it by hand, because I already did
> some tinkering on the file), and it works fine. Now I have _exe_ and
> _exeq_.
>
> To Brian, the OP: good idea, thank you!
>
> Have a nice day,
>   Peter

Hi Peter,

Did you use it on Windows, or Linux? On my Mandriva 2006 machine, I get no 
popup OK box, but instead get a little message at the bottom of the graphical 
Vim window.

I assume Brian's idea is to have ,,e work on either _exe_ or _exeq_. I like 
the idea that it doesn't require another comma comma command.

If we include it, one thing we need to be sure of is that, on Windows, Linux 
graphical (gvim) and Linux CLI (vim),  that _exeq_ does the right thing when 
confronted with ,,e.

I implemented the patch on my machine, and tested both an _exe_ and an _exeq_. 
They both appeared to work just right in gvim and vim in a gui terminal when 
spawning a graphical program. When spawning a CLI program (umenu or ls | 
less), gvim hung (looked like an infinite loop from the way it was blinking) 
on gvim, and worked reasonably well with vim in a gui terminal, but upon 
exiting the CLI program, it looked like you hadn't exited -- you need to know 
to press Ctrl+L to refresh the screen.

In pure CLI mode (no X), obviously spawning a gui program didn't work, but 
spawning a CLI program didn't infinite loop. The lack of feedback after 
exiting the CLI program was still an issue.

If we implement this, I think it should be as an option, with the default 
option being to treat _exeq_ exactly like _exe_, and only if someone flips a 
bit does it behave quietly. This will prevent a lot of confusion when people 
pass outlines back and forth. Of course, on the other hand, if we do that 
people might think of _exe_ and _exeq_ as synonomous, which we REALLY don't 
want.

Having never used VO in Windows, I haven't gotten to see this patch in the 
environment where it really does good.

Other feedback?

Thanks

SteveT

Steve Litt
Author: 
   * Universal Troubleshooting Process courseware
   * Troubleshooting Techniques of the Successful Technologist
   * Manager's Guide to Technical Troubleshooting
   * Twenty Eight Tales of Troubleshooting
   * Rapid Learning: Secret Weapon of the Successful Technologist

http://www.troubleshooters.com/bookstore
http://www.troubleshooters.com/utp/tcourses.htm