From: Eli Zaretskii <eliz@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: lekktu@gmail.com, matsuan@ca2.so-net.ne.jp, emacs-devel@gnu.org
Subject: Re: Emacs pretest 22.1.91
Date: Wed, 27 Feb 2008 21:15:54 +0200 [thread overview]
Message-ID: <uir0aky6t.fsf@gnu.org> (raw)
In-Reply-To: <47C55A60.5010709@gnu.org> (message from Jason Rumney on Wed, 27 Feb 2008 12:41:04 +0000)
> Date: Wed, 27 Feb 2008 12:41:04 +0000
> From: Jason Rumney <jasonr@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, matsuan@ca2.so-net.ne.jp, emacs-devel@gnu.org
>
> Juanma Barranquero wrote:
> > The cleanest fix I can think of at this moment is moving the
> > tool-bar-setup call, from `x-create-frame-with-faces' to
> > `frame-notice-user-settings'
>
> I think the case that the previous change was trying to fix is where
> emacs is started as emacs -nw and a GUI frame is created later. AFAICT,
> frame-notice-user-settings is only called at startup, so I think moving
> the tool-bar setup there will cause this case to fail again.
Since Windows doesn't support multi-tty (and probably won't for an
observable future), how about if Juanma makes this change conditioned
so that it only has effect on Windows?
next prev parent reply other threads:[~2008-02-27 19:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 18:50 Emacs pretest 22.1.91 Chong Yidong
2008-02-19 23:59 ` Jason Rumney
2008-02-21 6:35 ` Takashi Hiromatsu
2008-02-22 16:17 ` Eli Zaretskii
2008-02-23 3:51 ` Takashi Hiromatsu
2008-02-23 15:29 ` Eli Zaretskii
2008-02-24 14:21 ` Jason Rumney
2008-02-25 1:16 ` Takashi Hiromatsu
2008-02-25 1:27 ` Juanma Barranquero
2008-02-25 1:57 ` Takashi Hiromatsu
2008-02-25 2:13 ` Juanma Barranquero
2008-02-25 2:45 ` Takashi Hiromatsu
2008-02-25 2:44 ` Takashi Hiromatsu
2008-02-25 9:43 ` Juanma Barranquero
2008-02-25 6:16 ` Takashi Hiromatsu
2008-02-25 9:54 ` Juanma Barranquero
2008-02-25 10:58 ` Juanma Barranquero
2008-02-25 11:28 ` Jason Rumney
2008-02-25 11:42 ` Juanma Barranquero
2008-02-25 20:07 ` Eli Zaretskii
2008-02-26 1:19 ` Juanma Barranquero
2008-02-26 4:16 ` Eli Zaretskii
2008-02-26 9:36 ` Juanma Barranquero
2008-02-26 19:50 ` Eli Zaretskii
2008-02-27 1:20 ` Juanma Barranquero
2008-02-27 1:56 ` Juanma Barranquero
2008-02-27 4:14 ` Eli Zaretskii
2008-02-27 12:25 ` Juanma Barranquero
2008-02-27 12:41 ` Jason Rumney
2008-02-27 14:11 ` Juanma Barranquero
2008-02-27 15:49 ` Juanma Barranquero
2008-02-27 15:50 ` Stefan Monnier
2008-02-27 15:54 ` Juanma Barranquero
2008-02-28 1:03 ` Stefan Monnier
2008-02-28 4:14 ` Eli Zaretskii
2008-02-28 4:59 ` Stefan Monnier
2008-02-29 11:03 ` Eli Zaretskii
2008-03-02 5:15 ` Stefan Monnier
2008-02-27 19:15 ` Eli Zaretskii [this message]
2008-02-28 0:48 ` Juanma Barranquero
2008-02-25 23:45 ` Takashi Hiromatsu
2008-02-26 1:23 ` Juanma Barranquero
2008-02-26 4:09 ` Takashi Hiromatsu
2008-02-25 1:46 ` Jason Rumney
2008-02-22 19:28 ` Claus
2008-02-22 20:08 ` Eli Zaretskii
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=uir0aky6t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lekktu@gmail.com \
--cc=matsuan@ca2.so-net.ne.jp \
/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).