Feature Request: Let AsyncRun accept range

[Konfekt]

AsyncRun is an asynchronous version of ! which accepts a range. For example, %!cmd % replaces the buffer by the output of cmd. How about including a -range parameter in command! ... AsyncRun .... ?

[skywind3000]

Sadly, <range> keyword is not supported in neovim, I can't distinguish the range is given or not in neovim.

[skywind3000]

Currently I detect whether range is given by:

if a:count > 0 && a:line1 <= a:line2
   "-- range is given
else
   "-- range is not given
endif

The command is defined with -range=0, a:count, a:line1 and a:line2 are assigned to <count>, <line1> and <line2>

a little flaky.

Is there a better way for this ?

[Konfekt]

Looks like a good way to go. Perhaps you missed

						*<range>*
	<range> The number of items in the command range: 0, 1 or 2

Perhaps you could check for a:range == 0?.

[skywind3000]

<range> comes with vim 8.0.1078 and neovim doesn't have <range> macro.

[skywind3000]

updated, you can try:

:%AsyncRun cat

now.

[Konfekt]

Oh, I am sorry, I did not get that your <range> referred to what I found in the doc.

Yes, tried it, but does not change anything in the buffer. Neither %AsyncRun echo "hello".

[skywind3000]

At least, it will take the selected text as stdin, but continue output to quickfix window.

It is hard to change previous buffer text because the task is running in the background, when it finished,
the buffer may be closed/deleted, selection may changed, current window/tabpage may closed.

Everything are different.

[Konfekt]

Ok, but [range]! does not take [range] as input, but as output!

Yes, it is hard, and the buffer may have changed. That's why, for example replacing a visual selection is more of a use case than the complete buffer. That does not make much sense.

I understand that it is not easy to accomplish, maybe not worth all the effort.