From: Bastien <bastienguerry@googlemail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Carsten Dominik <dominik@science.uva.nl>,
Robert Goldman <rpgoldman@sift.info>
Subject: Re: save-frame-excursion?
Date: Sat, 25 Jul 2009 19:42:00 +0800 [thread overview]
Message-ID: <871vo5c7lj.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jwv63dh6g7d.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 24 Jul 2009 15:24:33 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> The calendar buffer was configured to be sticky in a particular frame,
>> so that when emacs wanted to show that calendar buffer, it showed it in
>> the different frame.
>
> That still doesn't explain the shift of focus.
Briefly, here is how org-read-date works:
- if org-read-date-popup-calendar is t, it pops up a calendar, either in
a different window, either in a different frame, depending on the user
configuration;
- it prompt the user for a date (and possibly more information like the
time, the repeater, etc.);
- it add new commands to the minibuffer-local-map: these commands modify
the calendar display. For example, M-S-<left> will call this command:
(org-eval-in-calendar '(calendar-backward-month 1))
- those minibuffer commands get a post-command hook which displays the
calendar according to the minibuffer prompt.
That's the basic mechanism.
For org-read-date to work when the calendar is displayed in another
frame, we need to prevent org-eval-in-calendar from losing the frame
focus.
I've just pushed a change to Org that spares us org-save-frame-excursion
by making `org-eval-in-calendar' DTRT about restauring the frame focus.
>> I don't entirely understand how the stickiness happens -- configuration
>> of the emacs calendar is far beyond me.
>
> Doesn't matter. If the code doesn't explicitly ask for a change in
> focus, then there's no reason (other than to work around a bug
> somewhere, probably) why we need to reset the focus via
> select-frame-set-input-focus when unwinding.
The code was indirectly asking for a change in focus by calling the
calendar from within a command.
>> Admittedly it's unlikely (at least now) to get into a state where you
>> will change the frame focus, but whenever you /do/ change the frame
>> focus, wouldn't you want it restored?
>
> Emacs almost never changes frame focus explicitly (for the good reason
> that it's mighty hard to do it reliably for all possible WMs).
I am not using frames so I was not aware of these issues until now,
and I agree changing frame focus explicitely is not very good.
Maybe we should have an option `org-calendar-force-display-in-window'
defaulting to t to prevent the calendar to be displayed in a separate
frame.
--
Bastien
next prev parent reply other threads:[~2009-07-25 11:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 17:30 save-frame-excursion? Bastien
2009-07-23 20:56 ` save-frame-excursion? Stefan Monnier
2009-07-24 2:24 ` save-frame-excursion? Robert Goldman
2009-07-24 3:16 ` save-frame-excursion? Stefan Monnier
2009-07-24 3:28 ` save-frame-excursion? Robert Goldman
2009-07-24 19:24 ` save-frame-excursion? Stefan Monnier
2009-07-24 21:18 ` save-frame-excursion? Robert Goldman
2009-07-25 14:39 ` save-frame-excursion? Stefan Monnier
2009-07-25 11:42 ` Bastien [this message]
2009-07-25 14:42 ` save-frame-excursion? Stefan Monnier
2009-07-25 22:11 ` save-frame-excursion? Bastien
2009-07-26 14:26 ` save-frame-excursion? Stefan Monnier
2009-07-26 17:00 ` save-frame-excursion? Drew Adams
2009-07-27 3:42 ` save-frame-excursion? Bastien
2009-07-27 4:50 ` save-frame-excursion? Stephen J. Turnbull
2009-07-27 4:58 ` save-frame-excursion? Bastien
2009-07-27 17:49 ` save-frame-excursion? Stefan Monnier
2009-07-27 21:05 ` save-frame-excursion? Bastien
2009-07-28 2:25 ` save-frame-excursion? Stefan Monnier
[not found] ` <87iqhhasm3.fsf@bzg.ath.cx>
2009-08-03 4:38 ` save-frame-excursion? Carsten Dominik
2009-08-03 12:50 ` save-frame-excursion? Robert Goldman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871vo5c7lj.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rpgoldman@sift.info \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.