Re: Vim70d map-to-func input prob? was Re: How to wake up getchar() ?

2006-04-15 Thread Eric Arnold
When I first saw thefeature, I thought it was a just a cleaner way of avoiding the :ex interaction in:call in map \a : call Tst() Since I'm still not really clear on why there is a difference with respect to recursion handling, I thought I should ask whether using the above is

Vim70d map-to-func input prob? was Re: How to wake up getchar() ?

2006-04-15 Thread Bram Moolenaar
Eric Arnold wrote: > I'm not sure what the intended fix for 70d was, but I can no longer > send a char to a function indirectly through an mapping, > meaning that in the example below, \b does not send a to > Tst(). Tst() waits for input directly from the user. > > Note: using >

Vim70d map-to-func input prob? was Re: How to wake up getchar() ?

2006-04-14 Thread Eric Arnold
I'm not sure what the intended fix for 70d was, but I can no longer send a char to a function indirectly through an mapping, meaning that in the example below, \b does not send a to Tst(). Tst() waits for input directly from the user. Note: using map \a : call Tst() works as e

Vim70d map-to-func input prob? was Re: How to wake up getchar() ?

2006-04-14 Thread Eric Arnold
I'm not sure what the intended fix for 70d was, but I can no longer send a char to a function indirectly through an mapping, meaning that in the example below, \b does not send a to Tst(). Tst() waits for input directly from the user. Note: using map \a : call Tst() works as e