no printing trace in console

[Tom.Zhang]

I occurred this issue again: Error: The volume change journal is being deleted. as the experience last time, I just need to wait. since there are more than 200M files in server, it took more than 3 days to recreate the journal. I came back this morning, saw all journals had been recreated and Everything was scanning the drives. I used Crl + ~ to enable the console but see nothing in it. after Everything UI resumed and worked fine, the console still had nothing in it. I tried Ctrl + ~ many times, it was the same. I believe it is some corner case. Everything version is 1.5.0.1271a (x64).

I also suspect the cause of "The volume change journal is being deleted. " Everything was running fine with "-instance T" and i am going to start another instance, but you know once I double click the Everything64.exe, I have no chance to stop the scanning so I closed it from task manager. might at that time the journal was deleted. i have no clue but this is the same activities I did for two times. just for your reference.

[void]

Please try increasing your USN Journal Size:

• In Everything 1.5, from the Tools menu, click Options.
• Click the NTFS tab on the left.
• Select your drive where the USN Journal was deleted.
• Change Maximum Size to: 262144 KB (256 MB)
  (recommended for 200 million+ files -set higher if you make millions of changes often)
• Click OK.

Are you redirecting standard output? (launching Everything with redirect: > or pipe: |)
Everything writes debug output to the standard output handle.

Please try debug logging instead:

• In Everything 1.5, from the Tools menu, under the Debug submenu, click Start Debug Logging.
  To stop debug logging:
• From the Tools menu, under the Debug submenu, click Stop Debug Logging.
  ---Your %TEMP%\Everything Debug Log.txt will open in Notepad.

[Tom.Zhang]

Thanks.

the value is already at 524288.

Yes i can get the debug.txt, the problem is why i can't see debug trace in console. it was there before.

[void]

The standard output handle has most likely been redirected.

Everything will never redirect standard output.
However, a shell extension can or it can be done externally.

I'll look into always printing to the console, even when there's a redirect.

[Tom.Zhang]

Thank you, this topic is complete.

[void]

Just making a note here: Everything 1.5.0.1360a will now always write to console even when redirecting output.