-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Better way to select specific historic entries to edit #677
Comments
Sounds like a great use-case for |
pyfzf hasn't been updated in 2 years. I'd avoid using it. |
I totally agree, but I haven't found one that seems better for this use-case. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This should not be closed. |
@alichtman Agreed. Going through now after the holidays to clean up the backlog a bit. Thanks for pointing this one out! |
We now have Still not sure about an interactive menu option, but I'll leave this open while we consider it. |
Jrnl really needs a better way to select which jrnl entries to view/open/edit.
The only way to filter the entries you want is by consecutive timestamps and tags. Tags are amazing but very often come up short. Time entries are useful only if you're using jrnl like a journal (heh).
In the following example I use
@notes
and@keyword
to filter down jrnl entries to only four items with the following titles. There's no way for me to easily narrow down on say item two and four. I can use-n 3
to see both but then I also get item three in the middle.A fuzzy search feature (
grep -i -E "Topic1|Topic3"
) where you could search on an entry's contents in addition to tags (either title only or anywhere in the entry) would be amazing. An interactive menu-system with--menu
would also be amazing.> jrnl @notes @keyword --short 2019-09-26 18:29 Lecture on Topic1 2019-09-27 19:27 Reading notes Topic2 2019-10-02 18:23 Topic3 2019-10-11 18:42 Project Design Topic4
The text was updated successfully, but these errors were encountered: