"Jacob S. Gordon" <[email protected]> writes: > Suppose you have an agenda view with a task that appears more than > once (e.g. it’s repeated, log mode is on). If you clock into this > task and try to jump to it with ‘org-agenda-clock-goto’ (‘J’) the > point will go to the last entry in the agenda, which could be > off-screen. > > Similarly, if the task is filtered out of the agenda, it will jump > close to the last entry instead of running ‘org-clock-goto’ in another > window.
You are describing cases that might be common for some workflows, but not necessarily common for all use cases. Not everyone uses filtering, multi-day agenda, and J at the same time. I think `org-agenda-clock-goto' function itself did not change much since its initial implementation, apart from adding a feature to jump to org heading when it is clocked, but not displayed in the agenda. The described edge cases were likely not considered. > While neither behaviour is inconsistent with the documentation, I > don’t find them particularly intuitive. IMO it would be nicer if it > jumped to the nearest entry and/or preferred jumping within the date > at point. I suspect the intention behind the current behaviour is to > select deadlined > scheduled > log entries by selecting the last > clocking overlay (within a day view). > > Any thoughts on what this behaviour should be? This command has been introduced in https://list.orgmode.org/orgmode/[email protected]/ I do not see that selecting the last command is intentional there. Just a side effect of using 'mapc'. I do not see any problem augmenting org-agenda-clock-goto to jump to the nearest entry. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
