Skip to content
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

[minor] Prefix a new line after some secs idling in the debug log #1185

Open
newsve opened this issue Aug 7, 2024 · 2 comments
Open

[minor] Prefix a new line after some secs idling in the debug log #1185

newsve opened this issue Aug 7, 2024 · 2 comments
Labels
enhancement New feature or request gauging interest Looking for additional discussion and viewpoints

Comments

@newsve
Copy link

newsve commented Aug 7, 2024

Is your feature request related to a problem? Please describe.

Sometimes is isn't easy to spot the beginning of your key testing in the debug log. Trying to insert a manual enter doesn't work either because the enter will be interpreted as event.

Describe the solution you'd like.

There different possible solutions:

  • prefix after, e.g., 5sec idling (could be tedious to wait the time idling)
  • intro a new cmd line flag or defconfig parameter which takes the idling time, so users can set this pause themselves
  • add a mappable keycode which lets the user manually insert a new line on demand, without the need to have the terminal window focused

Describe alternatives you've considered.

Ending and restarting kanaata

Additional context

No response

@newsve newsve added the enhancement New feature or request label Aug 7, 2024
@jtroo
Copy link
Owner

jtroo commented Aug 9, 2024

Maybe you could try lrld as a log marker? It should have some unique logging. Adjacently, when I'm testing random new configurations I usually test it first in the simulator: https://jtroo.github.io/

@jtroo jtroo added the gauging interest Looking for additional discussion and viewpoints label Aug 9, 2024
@newsve
Copy link
Author

newsve commented Aug 9, 2024

This is a great idea, and what I found working too is just to focus on a bigger change of the seconds in the time stamps, they give a good hint where to look at:

11:17:47.1704 [DEBUG] 
11:17:47.1711 [DEBUG] 
11:17:53.2470 [DEBUG]  <-- 
11:17:53.2486 [DEBUG] 

Again, it's no dealbreaker by any means, we can close this issue again, was just some spontaneous idea...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request gauging interest Looking for additional discussion and viewpoints
Projects
None yet
Development

No branches or pull requests

2 participants