From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: thierry.volpiatto@gmail.com, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: bug in 23.2.92 with anything
Date: Sun, 16 Jan 2011 17:48:59 -0500 [thread overview]
Message-ID: <E1PebP9-0006hO-7b@fencepost.gnu.org> (raw)
In-Reply-To: <4D33301C.3080100@gmx.at> (message from martin rudalics on Sun, 16 Jan 2011 18:51:24 +0100)
> Date: Sun, 16 Jan 2011 18:51:24 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org,
> thierry.volpiatto@gmail.com
>
> > /* When running redisplay, we play a bit fast-and-loose and allow e.g.
> > selected_frame and selected_window to be temporarily out-of-sync so
> > when we come back here via `goto retry', we need to resync because we
> > may need to run Elisp code (via prepare_menu_bars). */
> > select_frame_for_redisplay (old_frame);
> >
> > It would be good to get rid of such risky code.
>
> Is there any reason why this should not select the window too?
By "this" you mean what? IOW, who or what should "select the window
too"?
next prev parent reply other threads:[~2011-01-16 22:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 19:05 bug in 23.2.92 with anything Thierry Volpiatto
2011-01-15 19:47 ` Chong Yidong
2011-01-15 20:27 ` Thierry Volpiatto
2011-01-15 20:05 ` martin rudalics
2011-01-15 21:00 ` Thierry Volpiatto
2011-01-15 21:35 ` Chong Yidong
2011-01-15 21:54 ` martin rudalics
2011-01-15 22:33 ` Thierry Volpiatto
2011-01-16 0:04 ` martin rudalics
2011-01-16 7:16 ` Thierry Volpiatto
2011-01-16 10:37 ` martin rudalics
2011-01-17 9:49 ` Thierry Volpiatto
2011-01-17 10:28 ` martin rudalics
2011-01-17 10:37 ` Thierry Volpiatto
2011-01-17 10:47 ` martin rudalics
2011-01-17 13:09 ` Thierry Volpiatto
2011-01-17 10:45 ` Thierry Volpiatto
2011-01-17 12:00 ` Thierry Volpiatto
2011-01-17 17:48 ` martin rudalics
2011-01-17 18:09 ` Thierry Volpiatto
2011-01-18 7:47 ` martin rudalics
2011-01-18 8:55 ` Thierry Volpiatto
2011-01-18 9:12 ` martin rudalics
2011-01-18 10:12 ` Thierry Volpiatto
2011-01-18 12:02 ` Simon Leinen
2011-01-22 2:45 ` Chong Yidong
2011-01-18 15:11 ` Eli Zaretskii
2011-01-18 15:50 ` Thierry Volpiatto
2011-01-18 15:52 ` Eli Zaretskii
2011-01-18 18:52 ` Thierry Volpiatto
2011-01-20 1:17 ` David De La Harpe Golden
2011-01-20 7:37 ` Thierry Volpiatto
2011-01-20 8:25 ` Eli Zaretskii
2011-01-20 11:07 ` Stephen J. Turnbull
2011-01-16 4:26 ` Stefan Monnier
2011-01-16 9:30 ` Eli Zaretskii
2011-01-16 11:35 ` martin rudalics
2011-01-16 13:48 ` Eli Zaretskii
2011-01-16 17:51 ` martin rudalics
2011-01-16 15:16 ` Stefan Monnier
2011-01-16 17:51 ` martin rudalics
2011-01-16 22:48 ` Eli Zaretskii [this message]
2011-01-16 23:23 ` martin rudalics
2011-01-17 12:52 ` Eli Zaretskii
2011-01-17 17:48 ` martin rudalics
2011-01-16 10:35 ` martin rudalics
2011-01-17 10:09 ` Thierry Volpiatto
2011-01-17 10:43 ` martin rudalics
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1PebP9-0006hO-7b@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
--cc=thierry.volpiatto@gmail.com \
/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.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).