Page 1 of 1

ES error messages

Posted: Sun Jul 14, 2019 7:24 pm
by NotNull
Just noticed that ES writes it's error message to console (or stdout?) instead of the stderr output stream ( link for more information)
Using this stdout and stdin makes it easier to redirect the output to a file / to 'void' (nul) / to a remote session or terminal.

Example: When Everything is not running:

Code: Select all

es.exe something 2>nul
Everything IPC window not found, IPC unavailable.
I expected this command to produce no output.
But not all console applications follow that ''rule'. Might even be by design.

Anyway, very low priority suggestion.

Re: ES error messages

Posted: Mon Jul 15, 2019 3:15 am
by void
ES 1.1.0.13:
  • Moved error output to stderr.
https://www.voidtools.com/ES-1.1.0.13.zip

Re: ES error messages

Posted: Mon Jul 15, 2019 7:53 pm
by NotNull
:shock: That's fast!

By low priority I had something in mind between M&M’s Color Distribution Analysis and hiring someone to iron your shoelaces ....


Will test and report back ... with medium priority ;)

Re: ES error messages

Posted: Tue Jul 16, 2019 12:03 am
by therube
Would this have not accomplished it?

Code: Select all

es.exe  something  2>&1 >nul
Oh, that's going to send everything (Everything ;-)) to nul, & you just wanted stderr.

Re: ES error messages

Posted: Tue Jul 16, 2019 4:00 pm
by NotNull
Testing version 1.1.0.13 brought to light a couple of issues that were already (dormant) in older versions of ES (*):
  • options /? , -? , -h and -help generate errorcode 6: Unknown switch (but show the help text)
  • options /h and /help don't show any help at all.
But I'm happy with the new version :)


(*)Tested with 1.1.0.11. No errorcodes, but it sets %errorlevel% to 6.

Re: ES error messages

Posted: Wed Jul 17, 2019 1:47 am
by void
Thanks for the issue report.

ES 1.1.0.14:
  • Updated help text thanks to NotNull.
  • Fixed error reported by -? -h -help.
  • -h -help now shows help.
https://www.voidtools.com/ES-1.1.0.14.zip