Problem: When debugging, I often need to isolate new log entries from previous output. Currently, there’s no way to clear the log display without restarting the entire debugging session, making it difficult to focus on just the latest information.
Proposed Solution: Implement a “Clear Logs” button or keyboard shortcut (similar to cmd-K in terminal) to clear the current log display without affecting the ongoing debugging session.
Benefits:
- Improved focus on new log entries
- Cleaner debugging workflow
- Reduced cognitive load when working with verbose logging
- Faster iteration during debugging sessions
Implementation Details:
- Add a visible “Clear” button in the log viewer toolbar
- Support a keyboard shortcut (e.g.,
cmd-Korctrl-K) - Option to automatically clear logs when specific breakpoints are hit
- Potentially add a time-based indicator showing when logs were cleared
User Experience: This feature would maintain the current debugging state while providing a fresh view of new log entries, helping developers quickly identify cause-and-effect relationships during troubleshooting.