-
Notifications
You must be signed in to change notification settings - Fork 374
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 Request - Save my marked items #168
Comments
+1 It would be nice to reopen a file and have the marked items persisted, instead of having to search and mark everything again. |
Currently implementing this. Should marks be restored only on first file load or on any subsequent reload? |
I my opinion it would be better if the marks persist also after subsequent reloads. |
Created PR. Marks are saved in session data. @arthurspa until merged you can test it in klogg dev builds: edit: updated links to new build with fixed filters dialog |
Thanks - this is greate. |
This is development build from master branch. I've done a lot of refactoring, and unfortunately there are only bare minimum automatic tests, so some features got broken (e.g. Quick Find). I've created an issue for this. |
@Moshe81 I've identified bad commit and reverted changes for filters dialog and quickfind. New build is ready: |
I did not have time to test it, but I hope it gets merged and released. Thank you @variar for implementing this. |
Thanks @variar, will merge that. Is keeping marks on closing/re-opening glogg the use case discussed here? Or are we talking about keeping marks for each file, even if the file is closed and reopened (like vim does for marks)? |
@nickbnf I've implemented saving marks only for opened files. Storing marks for all closed files forever might produce big configuration file with no way to clean it up. |
Hi,
I love Glogg.
I wish that the item I mark in blow will remain if I close the log and reopen it.
I found my self doing the same operation again and again for one log.
Thanks
Moshe
The text was updated successfully, but these errors were encountered: