-
Notifications
You must be signed in to change notification settings - Fork 76
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
Idea: Simplify record keys #116
Comments
I had the exact same idea in mind since copying the record key can be a bit tedious. The only concern I have is that if you list the records, stop tracking and start again and then edit a record based on the output of The solution to this problem could be to numerate the records with a descending index (oldest is #1). |
Ah, nice! |
Okay, since the reverse of the records is (as it seems) just a one-line-change, I guess we don't need a special issue for it - unless you know of some other parts of the code that rely on the numeration. |
Yap, the numeration can be changed as a part of that issue. |
Currently, the only way to reference a record is its key: the specific time it has been started. This is laborious to write down number by number, or you need to copy paste it every time. We already have the latest alias, but maybe we could simplify this even more by letting the user reference a record of the current day by entering its "ID", that is already created on the fly via
I imagine it like this:
timetrace edit record #1 -p 5m
The text was updated successfully, but these errors were encountered: