Advanced exit status handling? about neoformat HOT 6 CLOSED

I think it would be best to make PHP_CodeSniffer use the generally accepted Posix exit codes: http://tldp.org/LDP/abs/html/exitcodes.html

However, I would be open to adding an option for formatters that decide to go rogue with their exit codes.

from neoformat.

I totally agree with you. I opened issue on PHP_CodeSniffer squizlabs/PHP_CodeSniffer#1359

from neoformat.

They are not interested in fixing it.

How about adding an optional callback function which validates the exit codes?

from neoformat.

An optional callback could be created, but it will require some work since Neoformat currently uses v:shell_error after calling system() to check if the command error.

Here is the relevant doc:

v:shell_error Result of the last shell command. When non-zero, the last
shell command had an error. When zero, there was no problem.
This only works when the shell returns the error code to Vim.
The value -1 is often used when the command could not be
executed. Read-only.
Example:

:!mv foo bar
:if v:shell_error
:  echo 'could not rename "foo" to "bar"!'
:endif

from neoformat.

The v:shell_error does seem to contain the command exit code

:call system("exit 4")
:echo v:shell_error
4

so it should not be too much work.

from neoformat.

See new config variables:

https://github.com/sbdchd/neoformat#config-optional

from neoformat.