emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-agenda-switch-to switches to weird place
Date: Tue, 11 Oct 2011 21:35:59 +0200	[thread overview]
Message-ID: <80hb3f5nj4.fsf@somewhere.org> (raw)
In-Reply-To: 87r52jqwju.fsf@gmail.com

Hi Antoine,

Antoine Levitt wrote:
> 11/10/11 18:45, Sebastien Vauban
>> Antoine Levitt wrote:
>>> I use org-capture to store information (such as appointments), then view
>>> them in the agenda. I use RET (org-agenda-switch-to) in the agenda view to
>>> modify them. For instance, for an entry like
>>>
>>> * TODO Some task
>>> SCHEDULED: !<2011-10-11 Tue>
>>>
>>> , point is at "!", which is inconvenient, because most of the time I want to
>>> modify the heading of the entry ("Some task"). A nice place to put the point
>>> would be at the %? specifier of org-capture-templates, if specified.
>>> Apparently, org-capture does the job of inserting a marker for
>>> org-agenda-switch-to to come back to, so it should be able to figure out if
>>> %? was specified, and if yes, where. I couldn't manage to do it, though.
>>> Could someone take a look at this?
>>
>> [...] I don't see how org-capture templates would come into play: your
>> different capture templates can have very different positions for %?, and
>> once captured, a note or TODO is no different than free text that the user
>> would have written manually.

Please consider what follows as doubtful, as I absolutely don't have enough
experience on this subject... but let's try...

> If I understand correctly, org-agenda-switch-to goes to the org-marker
> marker that is set by capture.

No, I absolutely don't think so. Org files are plain text files: what you
don't see in there, is simply not there. So, how could such markers be stored
in the Org file, when capturing something, and not be visible?

IIUC, the markers are simply some sort of regexp search to find certain
typical positions:

- org-marker matches the timestamp which is at the origin of the presence of
  the entry in the agenda

- org-hd-marker is the beginning of the heading.

> If capture inserts this marker right after the template insertion,
> org-agenda can then switch back to it. In theory at least. I can't make
> sense of org-capture's code.

So, no, capture does not insert any biscuit for later. It simply is the agenda
functions which scan all the agenda buffers, and remember where the important
elements are, to be used when jumping.

> Anyway, pretty much anything is better than the current behavior, which is
> not very user friendly when SCHEDULED info is present.

You say:

>>> , point is at "!", which is inconvenient, because most of the time I want to
>>> modify the heading of the entry ("Some task").

Do you really modify the title more often than the date? You have luck!
Because of procrastination, I'd say I much, much more often change the date, to
reprogram the entry at a later date, and so on, and so on.

Anyway, would you jump onto the beginning of the heading, just where the `***'
start, I think you can change the line:

    (org-get-at-bol 'org-marker))

with:

    (org-get-at-bol 'org-hd-marker))

to get another behavior. Now, from that, adding a constant number, or --
better -- moving forward a couple of times, or -- certainly there are still
better options -- ... would allow you to land on whichever component of the
heading.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2011-10-11 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 15:57 org-agenda-switch-to switches to weird place Antoine Levitt
2011-10-11 16:45 ` Sebastien Vauban
2011-10-11 17:15   ` Antoine Levitt
2011-10-11 19:35     ` Sebastien Vauban [this message]
2011-10-11 20:24       ` Antoine Levitt

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=80hb3f5nj4.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).