When I'm using iTerm2 or Warp and fish (possibly other shells too) and run a command that takes a few seconds or longer, sometimes this is added to the logs of the command:
2024-01-03 09:11:16.515 terminal-notifier[86954:7853565] AfloatX loaded
I narrowed it down to the NSLog:
|
NSLog(@"AfloatX loaded"); |
I patched the binary, no-oping the NSLog call and it fixed the issue.
Maybe there's a way to still log it without it affecting terminals? I even tried adding iTerm2 and Warp to MacForge's blacklist and the message was still logged. My only guess is that it's due to what it says in NSLogv()'s docs (although I'm still unsure whose log it's collecting since if it is another app's then a random shell shouldn't be capturing it?):
If the STDERR_FILENO file descriptor has been redirected away from the default or is going to a tty, it will also be written there.
- macOS 13.6.2
- MacForge 1.2.2 (2)
- AfloatX 1.6
When I'm using iTerm2 or Warp and fish (possibly other shells too) and run a command that takes a few seconds or longer, sometimes this is added to the logs of the command:
I narrowed it down to the
NSLog:AfloatX/AfloatX/AfloatX.m
Line 150 in 8c6907e
I patched the binary, no-oping the
NSLogcall and it fixed the issue.Maybe there's a way to still log it without it affecting terminals? I even tried adding iTerm2 and Warp to MacForge's blacklist and the message was still logged. My only guess is that it's due to what it says in
NSLogv()'s docs (although I'm still unsure whose log it's collecting since if it is another app's then a random shell shouldn't be capturing it?):