On 2017-10-26 21:12, Jose Caballero wrote:
> Quick question: when using the :g command, can I call a plugin
> function? Like
>
> :g//:call AFunction()
Yes (that 2nd colon is optional). It would require the function to
context-aware with regards to the current line, but otherwise, it
Should
2017-10-26 20:24 GMT-04:00 Tim Chase :
> On 2017-10-26 19:13, Jose Caballero wrote:
>> if I want to write a function that does something after every line
>> matching a given pattern (for example, for every python method
>> definition), what does the community prefer to
On 2017-10-26 19:13, Jose Caballero wrote:
> if I want to write a function that does something after every line
> matching a given pattern (for example, for every python method
> definition), what does the community prefer to handle it?
> Just iteratively?
The pattern you describe matches
Hello,
if I want to write a function that does something after every line
matching a given pattern (for example, for every python method
definition), what does the community prefer to handle it?
Just iteratively?
Or with a recursive function where the range changes from call to call?
I am just
Hi,
2017/10/25 Wed 21:28:50 UTC+9 Christian Brabandt wrote:
> Hi Ken,
> I briefly looked at your patch and have some feedback.
>
> On Mi, 25 Okt 2017, Ken Takata wrote:
>
> > Changes are:
> > * Merge the two patches into one.
> > * Update the document.
> > * Rename the global variable