From: Carsten Dominik <carsten.dominik@gmail.com>
To: Andreas Seltenreich <seltenreich@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [patch] org-agenda-goto should push mark before moving point
Date: Tue, 27 Apr 2010 12:00:26 +0200 [thread overview]
Message-ID: <CC9A2C74-AD13-4E5D-8228-BDD6EAC01833@gmail.com> (raw)
In-Reply-To: <87ljce1rvx.fsf@gate450.dyndns.org>
Hi Andreas,
I have applied your patch.
Thanks.
- Carsten
On Apr 23, 2010, at 10:42 AM, Andreas Seltenreich wrote:
> Carsten Dominik writes:
>
>> On Apr 22, 2010, at 10:57 PM, Andreas Seltenreich wrote:
>>> (switch-to-buffer-other-window buffer)
>>> (widen)
>>> + (push-mark)
>>> (goto-char pos)
>>
>> I am no sure this is the right thing to do. Because, often you will
>> show *many* places from the agenda before going back to the buffer.
>> Org-agenda-goto is called by many other functions like org-agenda-
>> show, org-agenda-recenter etc.
>
> Well, I'd prefer too many marks over too few. Popping multiple marks
> off the local mark ring is still faster than moving point around
> manually.
>
>> This might work better:
>>
>> (defun my-org-agenda ()
>> (interactive)
>> (push-mark)
>> (call-interactively 'org-agenda))
>>
>> (define-key global-map "\C-ca" 'my-org-agenda)
>>
>> Maybe you can test this and report back?
>
> Won't work for me since most of the time I don't call the Agenda from
> the affected buffers. I guess advising goto-char and checking the
> backtrace for org-agenda-goto isn't a good idea either since goto-char
> is a C function... I'm afraid having git merge along that change
> indefinitely is the only option for me as long as I'm the only one
> deeming it a good thing.
>
> Thanks,
> andreas
- Carsten
prev parent reply other threads:[~2010-04-27 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 20:57 [patch] org-agenda-goto should push mark before moving point Andreas Seltenreich
2010-04-23 6:35 ` Carsten Dominik
2010-04-23 8:42 ` Andreas Seltenreich
2010-04-27 10:00 ` Carsten Dominik [this message]
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=CC9A2C74-AD13-4E5D-8228-BDD6EAC01833@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=seltenreich@gmx.de \
/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).