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

provide a command to insert a clocked task between two existing tasks #7

Open
dfeich opened this issue Nov 10, 2019 · 3 comments
Open

Comments

@dfeich
Copy link
Owner

dfeich commented Nov 10, 2019

This is a feature request.

It often happens that one forgot to clock a certain time range, because e.g. one
was not sitting in front of the computer. At the end of the day I usually go
over the clocked times (e.g. with the agenda clockcheck mode). I would like to
be able and move the cursor to a clocked task and then insert a clocked task
that fills the time of the previous task and the task under the cursor.

If the task under the cursor is the first task of that day, it should insert
a minimum clock interval (e.g. 5 min) before the current line. Task selection
can be implemented through helm, etc.

As all other commands, it should not force me to leave the agenda mode.

@c1-g
Copy link

c1-g commented Mar 3, 2022

This will be difficult to implement. I can think of a scenario which a user has multiple org-agenda-files it will be impossible to determine which file this new task should reside and where it should be in that file.

And even if org-agenda-files is just one big file then the where is still an issue since between these two existing tasks there could be many headings between them. Then what about sorting and filtering? When we add a new task how can we be sure that it will satisfy the filter and user can see them?

@dfeich
Copy link
Owner Author

dfeich commented Mar 5, 2022

Well, I am using several agenda files. But org-clock-convenience is actually leveraging the work that the agenda mode already has done, i.e. it just parses the current agenda view for clock lines, and that has been composed from all agenda files in the =org-agenda-files= list. The entries reference the tasks/source files. So, this would actually work.

@unhammer
Copy link
Contributor

To me it would make sense to use org-capture here (which already does the work of picking the org file and writing the task heading), and then just adding the logbook entry to the newly captured task.

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

No branches or pull requests

3 participants