I find it much better to view logs in a comint shell than through kubel-get-pod-logs (you facilitate this really well with the copy-to-clipboard option, thanks! I'm able to get what I want that way, so this is not high priority)
Features I like of viewing logs through comint:
- editable buffers is actually a benefit - I can cull old irrelevant lines, enter blank lines to demarcate interesting blocks
highlight-regexp family of functions works nicely with its font-lock-mode and other comint configuration that I have failed to replicate otherwise. This is a huge boon for live log viewing to highlight keywords, errors etc., shadow debug and other secondary info.- ANSI colors in log output work - I have to view logs that are otherwise a mess of control codes :(
I feel like the logging could really benefit from some of these features. I'm not sure exactly what the best and most appropriate way to facilitate this is unless it's to simply run the command through async-shell-command as I'm doing.
I find it much better to view logs in a comint shell than through
kubel-get-pod-logs(you facilitate this really well with the copy-to-clipboard option, thanks! I'm able to get what I want that way, so this is not high priority)Features I like of viewing logs through
comint:highlight-regexpfamily of functions works nicely with itsfont-lock-modeand other comint configuration that I have failed to replicate otherwise. This is a huge boon for live log viewing to highlight keywords, errors etc., shadow debug and other secondary info.I feel like the logging could really benefit from some of these features. I'm not sure exactly what the best and most appropriate way to facilitate this is unless it's to simply run the command through
async-shell-commandas I'm doing.