Hi Bram, On Wed, Apr 4, 2018 at 12:20 PM, Bram Moolenaar <[email protected]> wrote: > > Yegappan wrote: > >> Currently the job_info() function returns information about a specific job >> and there is no function available to return information about all the jobs. >> The attached patch modifies the job_info() function to return information >> about all the jobs in a List when an argument is not supplied. > > I thought it might be better to get a list of all jobs, but then what > else can someone do with that list than loop over the items to get their > info? Still, from the entries that job_info() returns it should be > possible to get the job object itself. >
Do you think returning a list of Job objects instead of information about the jobs will be useful? > > It's still difficult to recognize a specific job. It was mentioned > before to add the command that was used to start the job. Only then > does it make sense to get the list. > Should we modify the job_T structure to include the command used to start a job? - Yegappan -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
