You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m running into a bit of a friction point with the Agenda regarding accidental key presses.
The Scenario:
i open the Agenda
Navigate the list
Accidentally press t on a recurring task
Now because the task is recurring t doesn't mark it as DONE (which I could find by filtering for completed tasks). Instead, it immediately reschedules the task to the future.
If I wasn't looking directly at the line when I fat-fingered the key, I now have zero context on what task just disappeared and where it went (which future date).
My immediate instinct is to press u, but that gives me an error that the agenda buffer is not modifiable
To recover from this single accidental keystroke, I currently have to exit the agenda view and i guess grep all my notes for logbook entries with some sort of regex that matches the time of transition to the current time +-5 minutes? maybe there is a better way than this but still
Is there a known workflow or configuration to make the Agenda "undo-aware"? Ideally, pressing u inside the Agenda view would trigger an undo action in the underlying file that was just modified or maybe is there a way to make the agenda display the logbook entries too? so i could press t on them?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I’m running into a bit of a friction point with the Agenda regarding accidental key presses.
The Scenario:
i open the Agenda
Navigate the list
Accidentally press t on a recurring task
Now because the task is recurring t doesn't mark it as DONE (which I could find by filtering for completed tasks). Instead, it immediately reschedules the task to the future.
If I wasn't looking directly at the line when I fat-fingered the key, I now have zero context on what task just disappeared and where it went (which future date).
My immediate instinct is to press u, but that gives me an error that the agenda buffer is not modifiable
To recover from this single accidental keystroke, I currently have to exit the agenda view and i guess grep all my notes for logbook entries with some sort of regex that matches the time of transition to the current time +-5 minutes? maybe there is a better way than this but still
Is there a known workflow or configuration to make the Agenda "undo-aware"? Ideally, pressing u inside the Agenda view would trigger an undo action in the underlying file that was just modified or maybe is there a way to make the agenda display the logbook entries too? so i could press t on them?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions