Hi, thanks, Markus, for this patch.
Jason Ryan <[email protected]> wrote: > > I've taken Hannes' patch for the external editor and changed it to > > emply the handler mechanism. Basically, you say > > > > handler vimprobableedit vim -gf %s > > > > in your vimprobablerc, and when hitting ^t in a text field, you'll > > get a gvim window. > > > I don't have gvim installed, so I used: > handler vimprobableedit urxvtc -e vim %s > > and the term opens, I compose my message and then, when I exit the > term, the file exists in /tmp/vimprobableXXXX but nothing is printed > to the text field in vimprobable. This is exactly the problem I've sketched in the conclusion post of the old thread: The symmetric spawn operation which I initially wrote is probably not suited for quite a number of editors which will return after the opening operation immediately. Hence my plan/suggestion to use an asymmetric operation and watch the file for changes through another process instead. Which, of course, would be much more complex to implement. The major question for me here (which I think should be decided before any further coding) is whether we do need asymmetric operation or not. If not, we will need to document this in the wiki as well as possible which editors will work and which won't. Hannes
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________ Vimprobable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vimprobable-users
