Re: New c.interactive* methods

On Friday, May 4, 2018 at 7:58:09 AM UTC-5, Edward K. Ream wrote: > > I am going to change my mind generalize c.interactive for 5.7.2. That way > we won't break existing code later. > Done at 2b22c2b8cd in "devel" and merged to 5.7.2. This *will* be the last change to 5.7.2, barring serious

Re: New c.interactive* methods

On Thursday, May 3, 2018 at 6:35:10 PM UTC-5, Terry Brown wrote: > > I think a lot of people would find a non-callback version simpler, like > > thing1, thing2 = c.interactive(event, > prompts=['Find: ', ' Replace: ']) > Despite my earlier reply, that's not possible. c.interactive

Re: New c.interactive* methods

On Thu, May 3, 2018 at 6:35 PM, Terry Brown wrote: > > Someone's going to want interactive4() :-) > ​Hehe. I was going to write almost the same post.​ I think a lot of people would find a non-callback version simpler, lie > > thing1, thing2 = > ​​ >

Re: New c.interactive* methods

On Thu, 3 May 2018 15:02:46 -0700 (PDT) "Edward K. Ream" wrote: > @g.command('i2') > def i2_command(event): > c = event.get('c') > if not c: return > > def callback(arg1, arg2, c, event): > g.trace(arg1, arg2) > c.bodyWantsFocus() > >

New c.interactive* methods

The c.interactive, c.interactive2 and c.interactive3 methods prompt for 1, 2 or 3 arguments from the minibuffer. The docstrings for these methods show typical use. For example: @g.command('i2') def i2_command(event): c = event.get('c') if not c: return def callback(arg1,