From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: jumping from Agenda/Timeline to .org source file
Date: Sat, 18 Mar 2017 10:55:45 +0100 [thread overview]
Message-ID: <874lyq52ou.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2bmtapr2a.fsf@charm-ecran.irisa.fr> (Alan Schmitt's message of "Thu, 09 Mar 2017 13:34:05 +0100")
Hello,
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> Hello Eric,
>
> On 2017-03-09 07:23, Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Wednesday, 8 Mar 2017 at 12:55, Alan Schmitt wrote:
>>
>> [...]
>>
>>> I would like to use `org-agenda-goto', but without splitting the frame.
>>> In other words, I want to destination to be the one of
>>> `org-agenda-goto', but the window handling to be the one of
>>> `org-agenda-switch-to'.
>>
>> You could "advice" (advise in English :-) org-agenda-goto to delete other
>> windows after invocation?
>>
>> Or, create a new function which invokes org-agenda-goto and then
>> delete-other-windows and bind that to the key you want?
>
> Yes, these are solutions. I was just trying to understand why the
> functions had different behaviors.
I tried the same, without much success.
I think we could factor out both functions into a single one with
a control argument.
Any taker?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-03-18 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 8:17 jumping from Agenda/Timeline to .org source file Alan Schmitt
2017-03-08 11:02 ` Nicolas Goaziou
2017-03-08 12:55 ` Alan Schmitt
2017-03-08 20:56 ` Samuel Wales
[not found] ` <f5a37059cdb04043a6eae3e740e1eb0b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-09 7:23 ` Eric S Fraga
2017-03-09 12:34 ` Alan Schmitt
2017-03-18 9:55 ` Nicolas Goaziou [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-01 12:28 uselpa
2017-03-01 12:28 uselpa
2017-09-13 10:39 ` Nicolas Goaziou
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=874lyq52ou.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.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).