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
Add telescope picker to choose to start a new clock timer. Lets you choose from headlines to quickly start a timer. If you already have a timer / clock running it will first stop your other timer to start the new one (orgmode may do this automatically, i am not sure).
@lyz-code if any of these features I start proposing adding become out of scope to what you want this plugin to be, just let me know... i will not take any offense to it, haha ;-)
The text was updated successfully, but these errors were encountered:
Actually, I imagine a lot more features, I would love to have. Regarding clocking I currently would prioritize more a timestamp search, because I often need this to reveal, when I worked on what - which I currently do with live_grep, but the UX could be better. But this feature also sounds interesting - but it probably would need an extension of the OrgApi.
Now that the clock is fixed in nvim-orgmode and I started to use it more frequently, this could be actually an interesting feature. Question is: how to access clocking via API? @kristijanhusak do you have any take on this?
@seflue we can expose it in a way. Ideally, we would have a separate OrgApiClock class that does the generic stuff, similar to what orgmode/clock/init.lua exposes, and also some clocking methods on the OrgApiHeadline.
Let me know what structure would work for you and we can discuss further.
Add telescope picker to choose to start a new clock timer. Lets you choose from headlines to quickly start a timer. If you already have a timer / clock running it will first stop your other timer to start the new one (orgmode may do this automatically, i am not sure).
@lyz-code if any of these features I start proposing adding become out of scope to what you want this plugin to be, just let me know... i will not take any offense to it, haha ;-)
The text was updated successfully, but these errors were encountered: