job_start the make command

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

job_start the make command

Ni Va
Hi,

I am using a useful tool rigrep to search content through dirs and files.

Then I have applied it to makeprg and set errorformat to display found informations like this :


    let &makeprg     = expand("$VIM").'\vim80\rg.exe -n ' . l:args
    let &errorformat = '%f:%l:%m'
    make
    copen



It works perfectly and found items are well displayed with copen. Now I would like to job_start the command make and retrieve same display in the copened list.

How can I do that ?
Thanks by advance

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Bryan Richter
On Tue, Dec 13, 2016 at 10:04:53AM -0800, Ni Va wrote:

> Hi,
>
> I am using a useful tool rigrep to search content through dirs and
> files.
>
> Then I have applied it to makeprg and set errorformat to display found
> informations like this :
>
>
>     let &makeprg     = expand("$VIM").'\vim80\rg.exe -n ' . l:args
>     let &errorformat = '%f:%l:%m'
>     make
>     copen
>
> It works perfectly and found items are well displayed with copen. Now
> I would like to job_start the command make and retrieve same display
> in the copened list.
>
> How can I do that ?
> Thanks by advance
There are two bits of advice I have.

First, vim is very familiar with tools for searching through dirs and
files. The most well-known is called grep (perhaps you also know it).
vim has a command specifically for doing these searches: ":grep". You
can control it with 'grepprg' just like you can control ":make" with
'makeprg'. I suggest you get comfortable using those ones!

(I also use ripgrep. Here are the relevant configurations for me on
Linux):

    set grepprg=rg\ --vimgrep
    set grepformat=%f:%l:%c:%m

Second, you can use the AsyncRun plugin in order to run 'grepprg'
asynchronously. The syntax is a bit cumbersome, but it looks like:

    :AsyncRun -program=grep SEARCH_TERMS

That will run 'grepprg' in the background and populate the errorlist
as you desire.

https://github.com/skywind3000/asyncrun.vim

I hope someone has a better solution than this plugin. :) Maybe one
day :grep will automatically be async?

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Ni Va
Le mardi 13 décembre 2016 23:19:00 UTC+1, Bryan Richter a écrit :

> On Tue, Dec 13, 2016 at 10:04:53AM -0800, Ni Va wrote:
> > Hi,
> >
> > I am using a useful tool rigrep to search content through dirs and
> > files.
> >
> > Then I have applied it to makeprg and set errorformat to display found
> > informations like this :
> >
> >
> >     let &makeprg     = expand("$VIM").'\vim80\rg.exe -n ' . l:args
> >     let &errorformat = '%f:%l:%m'
> >     make
> >     copen
> >
> > It works perfectly and found items are well displayed with copen. Now
> > I would like to job_start the command make and retrieve same display
> > in the copened list.
> >
> > How can I do that ?
> > Thanks by advance
>
> There are two bits of advice I have.
>
> First, vim is very familiar with tools for searching through dirs and
> files. The most well-known is called grep (perhaps you also know it).
> vim has a command specifically for doing these searches: ":grep". You
> can control it with 'grepprg' just like you can control ":make" with
> 'makeprg'. I suggest you get comfortable using those ones!
>
> (I also use ripgrep. Here are the relevant configurations for me on
> Linux):
>
>     set grepprg=rg\ --vimgrep
>     set grepformat=%f:%l:%c:%m
>
> Second, you can use the AsyncRun plugin in order to run 'grepprg'
> asynchronously. The syntax is a bit cumbersome, but it looks like:
>
>     :AsyncRun -program=grep SEARCH_TERMS
>
> That will run 'grepprg' in the background and populate the errorlist
> as you desire.
>
> https://github.com/skywind3000/asyncrun.vim
>
> I hope someone has a better solution than this plugin. :) Maybe one
> day :grep will automatically be async?
Thank you Bryan for advices.

Applying that example
" From http://andrewvos.com/2016/09/14/writing-async-jobs-in-vim-8

I have done this code.
function! BackgroundCommandClose(channel)
  " Read the output from the command into the quickfix window
  execute "cfile! " . g:backgroundCommandOutput
  " Open the quickfix window
  copen
  unlet g:backgroundCommandOutput
endfunction

fun! utils#Search(args) "{{{
        "
        "
        "
        let prgPath = expand("$vimruntime")."/rg.exe"
        if !file_readable(prgPath)
                echoerr "rigrep tool not found in ".$vimruntime
                return -1
        endif

        let l:args   = empty(a:args) ? expand("<cword>") : a:args
        let cmd = prgPath . ' -n ' . l:args


    " Async func
    let g:backgroundCommandOutput = tempname()
    let j = job_start(cmd, {'close_cb': 'BackgroundCommandClose', 'out_io': 'file', 'out_name': g:backgroundCommandOutput})                
endfu
command! -bang -nargs=* -complete=file Search call utils#Search(<q-args>)


It works very well in background and copen the cfile well formatted.

Maybe you can advise me how optimizing BackgroundCommandClose func declaration in order to declare it within the utilsSearch func.

But thank for your advices.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Bram Moolenaar

Nivamail wrote:

> Le mardi 13 décembre 2016 23:19:00 UTC+1, Bryan Richter a écrit :
> > On Tue, Dec 13, 2016 at 10:04:53AM -0800, Ni Va wrote:
> > > Hi,
> > >
> > > I am using a useful tool rigrep to search content through dirs and
> > > files.
> > >
> > > Then I have applied it to makeprg and set errorformat to display found
> > > informations like this :
> > >
> > >
> > >     let &makeprg     = expand("$VIM").'\vim80\rg.exe -n ' . l:args
> > >     let &errorformat = '%f:%l:%m'
> > >     make
> > >     copen
> > >
> > > It works perfectly and found items are well displayed with copen. Now
> > > I would like to job_start the command make and retrieve same display
> > > in the copened list.
> > >
> > > How can I do that ?
> > > Thanks by advance
> >
> > There are two bits of advice I have.
> >
> > First, vim is very familiar with tools for searching through dirs and
> > files. The most well-known is called grep (perhaps you also know it).
> > vim has a command specifically for doing these searches: ":grep". You
> > can control it with 'grepprg' just like you can control ":make" with
> > 'makeprg'. I suggest you get comfortable using those ones!
> >
> > (I also use ripgrep. Here are the relevant configurations for me on
> > Linux):
> >
> >     set grepprg=rg\ --vimgrep
> >     set grepformat=%f:%l:%c:%m
> >
> > Second, you can use the AsyncRun plugin in order to run 'grepprg'
> > asynchronously. The syntax is a bit cumbersome, but it looks like:
> >
> >     :AsyncRun -program=grep SEARCH_TERMS
> >
> > That will run 'grepprg' in the background and populate the errorlist
> > as you desire.
> >
> > https://github.com/skywind3000/asyncrun.vim
> >
> > I hope someone has a better solution than this plugin. :) Maybe one
> > day :grep will automatically be async?
>
> Thank you Bryan for advices.
>
> Applying that example
> " From http://andrewvos.com/2016/09/14/writing-async-jobs-in-vim-8
>
> I have done this code.
> function! BackgroundCommandClose(channel)
>   " Read the output from the command into the quickfix window
>   execute "cfile! " . g:backgroundCommandOutput
>   " Open the quickfix window
>   copen
>   unlet g:backgroundCommandOutput
> endfunction
>
> fun! utils#Search(args) "{{{
> "
> "
> "
> let prgPath = expand("$vimruntime")."/rg.exe"
> if !file_readable(prgPath)
> echoerr "rigrep tool not found in ".$vimruntime
> return -1
> endif
>
> let l:args   = empty(a:args) ? expand("<cword>") : a:args
>         let cmd = prgPath . ' -n ' . l:args
>
>
>     " Async func
>     let g:backgroundCommandOutput = tempname()
>     let j = job_start(cmd, {'close_cb': 'BackgroundCommandClose', 'out_io': 'file', 'out_name': g:backgroundCommandOutput})                
> endfu
> command! -bang -nargs=* -complete=file Search call utils#Search(<q-args>)
>
>
> It works very well in background and copen the cfile well formatted.
>
> Maybe you can advise me how optimizing BackgroundCommandClose func declaration in order to declare it within the utilsSearch func.
>
> But thank for your advices.

This looks like a good start for a very useful plugin.  One that I would
like to include in Vim.

What I would prefer is something that works just like :make, but in the
background.  It would have the same arguments as :make and use the
'makeprg' option.  Only that the quickfix list is set much later.
Could call it :MakeBackground.

My wishlist:
- When using it again before the previous job is finished, prompt the
  user if he wants to abort the already running job.  I quite often run
  :make and than realize I forgot one change.
- Open the quickfix window when the --copen argument is given.
- Give a non-intrusive message when the work is done.

Anyone who would be willing to make this work and maintain it?

--
hundred-and-one symptoms of being an internet addict:
116. You are living with your boyfriend who networks your respective
     computers so you can sit in separate rooms and email each other

 /// Bram Moolenaar -- [hidden email] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Justin M. Keyes
On Wed, Dec 14, 2016 at 9:42 PM, Bram Moolenaar <[hidden email]> wrote:

>
> Nivamail wrote:
>
>> Le mardi 13 décembre 2016 23:19:00 UTC+1, Bryan Richter a écrit :
>> > On Tue, Dec 13, 2016 at 10:04:53AM -0800, Ni Va wrote:
>> > > Hi,
>> > >
>> > > I am using a useful tool rigrep to search content through dirs and
>> > > files.
>> > >
>> > > Then I have applied it to makeprg and set errorformat to display found
>> > > informations like this :
>> > >
>> > >
>> > >     let &makeprg     = expand("$VIM").'\vim80\rg.exe -n ' . l:args
>> > >     let &errorformat = '%f:%l:%m'
>> > >     make
>> > >     copen
>> > >
>> > > It works perfectly and found items are well displayed with copen. Now
>> > > I would like to job_start the command make and retrieve same display
>> > > in the copened list.
>> > >
>> > > How can I do that ?
>> > > Thanks by advance
>> >
>> > There are two bits of advice I have.
>> >
>> > First, vim is very familiar with tools for searching through dirs and
>> > files. The most well-known is called grep (perhaps you also know it).
>> > vim has a command specifically for doing these searches: ":grep". You
>> > can control it with 'grepprg' just like you can control ":make" with
>> > 'makeprg'. I suggest you get comfortable using those ones!
>> >
>> > (I also use ripgrep. Here are the relevant configurations for me on
>> > Linux):
>> >
>> >     set grepprg=rg\ --vimgrep
>> >     set grepformat=%f:%l:%c:%m
>> >
>> > Second, you can use the AsyncRun plugin in order to run 'grepprg'
>> > asynchronously. The syntax is a bit cumbersome, but it looks like:
>> >
>> >     :AsyncRun -program=grep SEARCH_TERMS
>> >
>> > That will run 'grepprg' in the background and populate the errorlist
>> > as you desire.
>> >
>> > https://github.com/skywind3000/asyncrun.vim
>> >
>> > I hope someone has a better solution than this plugin. :) Maybe one
>> > day :grep will automatically be async?
>>
>> Thank you Bryan for advices.
>>
>> Applying that example
>> " From http://andrewvos.com/2016/09/14/writing-async-jobs-in-vim-8
>>
>> I have done this code.
>> function! BackgroundCommandClose(channel)
>>   " Read the output from the command into the quickfix window
>>   execute "cfile! " . g:backgroundCommandOutput
>>   " Open the quickfix window
>>   copen
>>   unlet g:backgroundCommandOutput
>> endfunction
>>
>> fun! utils#Search(args) "{{{
>>       "
>>       "
>>       "
>>       let prgPath = expand("$vimruntime")."/rg.exe"
>>       if !file_readable(prgPath)
>>               echoerr "rigrep tool not found in ".$vimruntime
>>               return -1
>>       endif
>>
>>       let l:args   = empty(a:args) ? expand("<cword>") : a:args
>>         let cmd = prgPath . ' -n ' . l:args
>>
>>
>>     " Async func
>>     let g:backgroundCommandOutput = tempname()
>>     let j = job_start(cmd, {'close_cb': 'BackgroundCommandClose', 'out_io': 'file', 'out_name': g:backgroundCommandOutput})
>> endfu
>> command! -bang -nargs=* -complete=file Search call utils#Search(<q-args>)
>>
>>
>> It works very well in background and copen the cfile well formatted.
>>
>> Maybe you can advise me how optimizing BackgroundCommandClose func declaration in order to declare it within the utilsSearch func.
>>
>> But thank for your advices.
>
> This looks like a good start for a very useful plugin.  One that I would
> like to include in Vim.
>
> What I would prefer is something that works just like :make, but in the
> background.  It would have the same arguments as :make and use the
> 'makeprg' option.  Only that the quickfix list is set much later.
> Could call it :MakeBackground.
>
> My wishlist:
> - When using it again before the previous job is finished, prompt the
>   user if he wants to abort the already running job.  I quite often run
>   :make and than realize I forgot one change.
> - Open the quickfix window when the --copen argument is given.
> - Give a non-intrusive message when the work is done.
>
> Anyone who would be willing to make this work and maintain it?

In that case the dispatch.vim plugin should be updated to use job control:

https://github.com/tpope/vim-dispatch

It's a mature and already widely-used plugin. It would be very much
worth including, and it's backwards-compatible to older Vims.

Justin M. Keyes

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Andrew Vos
In reply to this post by Bram Moolenaar
On Wednesday, December 14, 2016 at 8:42:27 PM UTC, Bram Moolenaar wrote:

> Nivamail wrote:
>
> > Le mardi 13 décembre 2016 23:19:00 UTC+1, Bryan Richter a écrit :
> > > On Tue, Dec 13, 2016 at 10:04:53AM -0800, Ni Va wrote:
> > > > Hi,
> > > >
> > > > I am using a useful tool rigrep to search content through dirs and
> > > > files.
> > > >
> > > > Then I have applied it to makeprg and set errorformat to display found
> > > > informations like this :
> > > >
> > > >
> > > >     let &makeprg     = expand("$VIM").'\vim80\rg.exe -n ' . l:args
> > > >     let &errorformat = '%f:%l:%m'
> > > >     make
> > > >     copen
> > > >
> > > > It works perfectly and found items are well displayed with copen. Now
> > > > I would like to job_start the command make and retrieve same display
> > > > in the copened list.
> > > >
> > > > How can I do that ?
> > > > Thanks by advance
> > >
> > > There are two bits of advice I have.
> > >
> > > First, vim is very familiar with tools for searching through dirs and
> > > files. The most well-known is called grep (perhaps you also know it).
> > > vim has a command specifically for doing these searches: ":grep". You
> > > can control it with 'grepprg' just like you can control ":make" with
> > > 'makeprg'. I suggest you get comfortable using those ones!
> > >
> > > (I also use ripgrep. Here are the relevant configurations for me on
> > > Linux):
> > >
> > >     set grepprg=rg\ --vimgrep
> > >     set grepformat=%f:%l:%c:%m
> > >
> > > Second, you can use the AsyncRun plugin in order to run 'grepprg'
> > > asynchronously. The syntax is a bit cumbersome, but it looks like:
> > >
> > >     :AsyncRun -program=grep SEARCH_TERMS
> > >
> > > That will run 'grepprg' in the background and populate the errorlist
> > > as you desire.
> > >
> > > https://github.com/skywind3000/asyncrun.vim
> > >
> > > I hope someone has a better solution than this plugin. :) Maybe one
> > > day :grep will automatically be async?
> >
> > Thank you Bryan for advices.
> >
> > Applying that example
> > " From http://andrewvos.com/2016/09/14/writing-async-jobs-in-vim-8
> >
> > I have done this code.
> > function! BackgroundCommandClose(channel)
> >   " Read the output from the command into the quickfix window
> >   execute "cfile! " . g:backgroundCommandOutput
> >   " Open the quickfix window
> >   copen
> >   unlet g:backgroundCommandOutput
> > endfunction
> >
> > fun! utils#Search(args) "{{{
> > "
> > "
> > "
> > let prgPath = expand("$vimruntime")."/rg.exe"
> > if !file_readable(prgPath)
> > echoerr "rigrep tool not found in ".$vimruntime
> > return -1
> > endif
> >
> > let l:args   = empty(a:args) ? expand("<cword>") : a:args
> >         let cmd = prgPath . ' -n ' . l:args
> >
> >
> >     " Async func
> >     let g:backgroundCommandOutput = tempname()
> >     let j = job_start(cmd, {'close_cb': 'BackgroundCommandClose', 'out_io': 'file', 'out_name': g:backgroundCommandOutput})                
> > endfu
> > command! -bang -nargs=* -complete=file Search call utils#Search(<q-args>)
> >
> >
> > It works very well in background and copen the cfile well formatted.
> >
> > Maybe you can advise me how optimizing BackgroundCommandClose func declaration in order to declare it within the utilsSearch func.
> >
> > But thank for your advices.
>
> This looks like a good start for a very useful plugin.  One that I would
> like to include in Vim.
>
> What I would prefer is something that works just like :make, but in the
> background.  It would have the same arguments as :make and use the
> 'makeprg' option.  Only that the quickfix list is set much later.
> Could call it :MakeBackground.
>
> My wishlist:
> - When using it again before the previous job is finished, prompt the
>   user if he wants to abort the already running job.  I quite often run
>   :make and than realize I forgot one change.
> - Open the quickfix window when the --copen argument is given.
> - Give a non-intrusive message when the work is done.
>
> Anyone who would be willing to make this work and maintain it?
>
> --
> hundred-and-one symptoms of being an internet addict:
> 116. You are living with your boyfriend who networks your respective
>      computers so you can sit in separate rooms and email each other
>
>  /// Bram Moolenaar -- [hidden email] -- http://www.Moolenaar.net   \\\
> ///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org        ///
>  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///
I pushed this live if you wanna give it a try:

https://github.com/AndrewVos/vim-make-background

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Andrew Vos
In reply to this post by Bram Moolenaar
Bram, are you serious about possibly including something like this in Vim? If you are, then I would absolutely be interested in getting your wishlist all working and putting the time in to maintain it!

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Bram Moolenaar

Andrew Vos wrote:

> Bram, are you serious about possibly including something like this in
> Vim? If you are, then I would absolutely be interested in getting your
> wishlist all working and putting the time in to maintain it!

Yes, I think this is generally useful.

Would be good to review this, so that it fits the need of more than just
me.

--
hundred-and-one symptoms of being an internet addict:
123. You ask the car dealer to install an extra cigarette lighter
     on your new car to power your notebook.

 /// Bram Moolenaar -- [hidden email] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

skywind3000
Shameless self promotion:

https://github.com/skywind3000/asyncrun.vim

an asynchronous :Make command can be easily defined by using AsyncRun:

    :command! -bang -nargs=* -complete=file Make AsyncRun -program=make @ <args>

Now, :Make works just like old :make but runs in background, errors will be matched by &errorformat and displayed to quickfix window as well.

Any shell command (not limited to &makeprg, &grepprg) can be execute like

    :AsyncRun ls -la

Which is exactly the samething like old "!" command, but runs in background, errors will also be matched in quickfix window.

and many misc stuff:

1. macros like "%", "%<", ... in arguments can also be expanded.

2. autocommands about make or quickfix can be triggered before and after the job , your code in .vimrc can be triggered after before starting or after job finished (eg. you may want to connect the latest cscope file after it's been successfully generated in background).

3. global variable to indicate job status, which can be used to be displayed on your statusline.

4. Compatible from 7.4.1829 to the latest version.

5. Only one self-contained source file, asyncrun.vim.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: job_start the make command

Vincent Stone
Asynchrun is too heavy to be included in the vim just for make and grep. I prefer the vim-make-background plugin. Is there any plan to include it?

--Vincent Stone

On Friday, December 16, 2016 at 7:33:32 PM UTC+8, skywind3000 wrote:

> Shameless self promotion:
>
> https://github.com/skywind3000/asyncrun.vim
>
> an asynchronous :Make command can be easily defined by using AsyncRun:
>
>     :command! -bang -nargs=* -complete=file Make AsyncRun -program=make @ <args>
>
> Now, :Make works just like old :make but runs in background, errors will be matched by &errorformat and displayed to quickfix window as well.
>
> Any shell command (not limited to &makeprg, &grepprg) can be execute like
>
>     :AsyncRun ls -la
>
> Which is exactly the samething like old "!" command, but runs in background, errors will also be matched in quickfix window.
>
> and many misc stuff:
>
> 1. macros like "%", "%<", ... in arguments can also be expanded.
>
> 2. autocommands about make or quickfix can be triggered before and after the job , your code in .vimrc can be triggered after before starting or after job finished (eg. you may want to connect the latest cscope file after it's been successfully generated in background).
>
> 3. global variable to indicate job status, which can be used to be displayed on your statusline.
>
> 4. Compatible from 7.4.1829 to the latest version.
>
> 5. Only one self-contained source file, asyncrun.vim.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.