emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jan Malakhovski <oxij@oxij.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint
Date: Sun, 25 Oct 2015 15:29:43 +0000	[thread overview]
Message-ID: <8737wz2cgo.fsf@yin.lan> (raw)
In-Reply-To: <87r3kj9ese.fsf@nicolasgoaziou.fr>

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

>> * Pressing <Tab> on an entry in org-agenda-list moves the cursor to the
>>   corresponding node.
>>
>>   Previously it moved the cursor to the corresponding CLOCK: line and I
>>   used that a lot.
>
> According to `org-agenda-goto''s docstring, this doesn't look like
> a feature. Besides, there is a function to jump to the running clock
> already: `org-clock-goto'.

I mean this sequence:

* Press `M-x org-agenda-list`
* Press `v l`
  (or `v c`)
* Select an entry (interval)
* Press `<Tab>`

Previously it opened a window with the cursor on the CLOCK: line of the
corresponding entry (interval), now it jumps to the header of the task
this interval is an element of.

I'm sure this is a misfeature because now it's pretty much impossible to
quickly find CLOCK: entries that correspond to current org-agenda-list
items. For me this is critical, because I clock everything, have
megabytes of CLOCK: entries and edit them a lot.

Cheers,
  Jan

  reply	other threads:[~2015-10-25 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-25 14:39 Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus) to master/maint Jan Malakhovski
2015-10-25 14:57 ` Nicolas Goaziou
2015-10-25 15:29   ` Jan Malakhovski [this message]
2015-10-25 17:25     ` Nicolas Goaziou
2015-10-25 18:27       ` Jan Malakhovski
2015-10-28 10:34         ` Jan Malakhovski
2015-10-28 13:37           ` Nicolas Goaziou
2015-10-28 13:41           ` Matt Lundin
2015-10-28 14:29             ` Jan Malakhovski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737wz2cgo.fsf@yin.lan \
    --to=oxij@oxij.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).