-
-
Notifications
You must be signed in to change notification settings - Fork 649
Add the ability to route stdout and stderr to different buffers based on regular expressions #1525
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
Comments
+1 |
Still dreaming of seeing the |
In general it seems that this is not really doable, as when I created the ticket I had forgotten that output is spread over multiple messages (each containing a chunk of the output). Matching the contents of any one of them with a regular expression doesn't make much sense as they'd often be partial messages. |
I'm working with a system in kubernetes that is generating a large amount of logs to STDOUT. The ability to blacklist certain log messages by regex so they get dropped and not printed to the REPL would be valuable to me. Would this be doable, since I assume partial messages have to be reassembled before being printed to the REPL? |
It would be useful if we had the ability to redirect certain type of output (e.g. logging output to dedicated buffers for quick inspection).
Adding support for this won't be hard - basically we need a mapping between regular expressions or functions, that will be used to check if some output is a match, a buffer name (or some function) that will be used when we have a match. We just have to figure out what to do in the unlikely scenario of multiple matches - should check all patterns & predicates or just stop after the first match.
This functionality should be exposed to the users in the form of a defcustom.
The text was updated successfully, but these errors were encountered: