emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Jan Malakhovski <oxij@oxij.org>
Cc: Bastien Guerry <bzg@altern.org>,
	emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug: Regressions from 8.2.10 (8.2.10-35-g19a7d6-elpaplus)	to master/maint
Date: Wed, 28 Oct 2015 08:41:21 -0500	[thread overview]
Message-ID: <87vb9rp0u6.fsf@fastmail.fm> (raw)
In-Reply-To: <878u6nnuxd.fsf@yin.lan> (Jan Malakhovski's message of "Wed, 28 Oct 2015 10:34:22 +0000")

Jan Malakhovski <oxij@oxij.org> writes:

> I'm pretty sure that there are other org-mode users that are weeping
> silently since that change. Suppose you have more than a screen of clock
> lines in LOGBOOK under a heading (I have headings that have thousands).
> (org-agenda-goto) before 9f5e698679aecbed872a2030e4157e5e2b1d87e0 is
> very helpful when moving CLOCK lines between headings (think "refile
> CLOCK line") or editing overlaps or gaps: you <Tab> or click on the
> heading and here you are at the CLOCK, but after
> 9f5e698679aecbed872a2030e4157e5e2b1d87e0 you have to *retype* the date
> and time into search, which is annoying to say the least.

Try typing RET in the agenda. That calls org-agenda-switch-to, which
brings you to the relevant clock information in the agenda. (However, if
the information is tucked away in a LOGBOOK, it remains somewhat
inconveniently hidden from view).

> I'm willing to listen, but I seriously doubt there's such a compelling
> argument defending the change. Even when out of `org-agenda-list` in
> plain `org-agenda`, jumping to SCHEDULED or DEADLINE lines is nicer than
> to the heading itself.

I disagree that jumping to the SCHEDULED or DEADLINE lines from a normal
agenda is always nicer than jumping to the headline. I can easily change
planning info from within the agenda. But I cannot change the text of
the headline itself -- that is usually why I jump from the agenda. If
nothing else, we should have both options, which we seem to currently
have with the difference between TAB (org-agenda-goto) and RET
(org-agenda-switch-to). However, I am not sure how intentional this is,
as I can find nothing highlighting this difference in the documentation.

Best,
Matt

  parent reply	other threads:[~2015-10-28 13:41 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
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 [this message]
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=87vb9rp0u6.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=oxij@oxij.org \
    /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).