New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting exit status from job with job-control #1795
Comments
I believe it is planned. Also getting the PID. |
It was discussed having a blocking function that waits until a list of jobs has exited, and returns a list of status codes, but I think it would be cleaner having the status being passed in |
If this is good for a first-time contributor to tackle, I'd be happy to take it on myself. Let me know if there's any reason why I shouldn't. |
Fixes neovim#1795 by making v:job_data[2] be the exit status when the "activity" is "exit".
Fixes neovim#1795 by making v:job_data[2] be the exit status when the "activity" is "exit". Added test for non-zero job statuses and fixed another test Test error codes up to 255
Fixes neovim#1795 by making v:job_data[2] be the exit status when the "activity" is "exit". Added test for non-zero job statuses and fixed another test Test error codes up to 255
Fixes neovim#1795 by making v:job_data[2] be the exit status when the "activity" is "exit". Added test for non-zero job statuses and fixed another test Test error codes up to 255
Fixes neovim#1795 by making v:job_data[2] be the exit status when the "activity" is "exit". Added test for non-zero job statuses and fixed another test Test error codes up to 255
Fairly certain this was fixed a while ago, hence #1954 being closed, so I'll close this as well. |
I could be wrong about this, but it doesn't seem possible to get the exit status from a job with job-control. This seems like a pretty major limitation. Is there a reason for this? It would be nice to have either a function
jobstatus()
or havev:job_data[2]
be the exit status whenv:job_data[1]
is'exit'
. Thoughts?PS I apologize if this has been discussed before. I didn't find a previous discussion on it.
The text was updated successfully, but these errors were encountered: