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

Feature: open the logs in $EDITOR for easier navigation and copy #62

Open
sayanarijit opened this issue Oct 20, 2022 · 3 comments
Open

Comments

@sayanarijit
Copy link
Contributor

A key binding to open the logs in $EDITOR would be great. This will help easily navigate, select and copy logs.

@pvolok
Copy link
Owner

pvolok commented Oct 20, 2022

Can you describe your usecase for reading the logs? The problem with watching logs via mprocs is that rendering log updates can produce more logs and this process will loop.

@sayanarijit
Copy link
Contributor Author

sayanarijit commented Oct 21, 2022

Usecase: let's say I'm running a db service in mprocs. When debugging queries, I want to see the logs produced by the db service. I can easily scroll through it in mprocs itself, but searching isn't possible. Now let's say I found the bug, and I want to create an issue. For that I need to select a specific snippet of the logs, copy and paste on my browser. Isn't possible either.

This feature will let me open the logs in $EDITOR by a key press (e?) at any specific point in time, which will allow me to search, select and copy any part of the logs, and exit the editor to resume streaming of the logs.

@pvolok
Copy link
Owner

pvolok commented Oct 29, 2022

Sorry for a late reply. First I thought that you wanted to see mprocs.loc file, which will be created if there are some errors inside of mprocs. But you meant to open terminal contents in $EDITOR. I can see how I would use this feature a lot. I will add it, but a bit later since I want to do some refactoring and include good support for lua configs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants