unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	dann@ics.uci.edu, 1133@emacsbugs.donarmstrong.com,
	emacs-devel@gnu.org
Subject: bug#1133: Tool-bar and multi-tty
Date: Fri, 10 Oct 2008 13:18:31 -0400	[thread overview]
Message-ID: <jwvej2omkrv.fsf-monnier+emacsbugreports__16280.5734006271$1223659995$gmane$org@gnu.org> (raw)
In-Reply-To: <uy70wj3aa.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Oct 2008 09:51:57 +0200")

>> Bug 1133 notes a problem with tool-bars and multi-tty.  Basically,
>> tool-bar-map is not set up if the first frame is on a tty; it is only
>> initialized when the first graphical frame is created.  This causes
>> problems for major modes that define their own tool-bar maps.
>> 
>> I think the solution is to define a normal hook, tool-bar-setup-hook, to
>> be run after the tool-bar is set up successfully for the first time.

> This sounds like a very complicated solution.  Why can't we set up
> tool-bar-map unconditionally?  Perhaps changes that make that possible
> are much smaller and cleaner than what you suggest here?

My thoughts exactly... Why?


        Stefan






  parent reply	other threads:[~2008-10-10 17:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <873aj56v2p.fsf@cyd.mit.edu>
2008-10-10  7:50 ` bug#1133: Tool-bar and multi-tty Eli Zaretskii
2008-10-10  7:51 ` Eli Zaretskii
     [not found] ` <uy70wj3aa.fsf@gnu.org>
2008-10-10 17:05   ` Chong Yidong
2008-10-10 17:18   ` Stefan Monnier [this message]
     [not found]   ` <jwvej2omkrv.fsf-monnier+emacsbugreports@gnu.org>
2008-10-10 18:27     ` Chong Yidong
     [not found]   ` <87prm8fkjn.fsf@cyd.mit.edu>
2008-10-10 18:27     ` Eli Zaretskii
     [not found]     ` <uljwwi9vc.fsf@gnu.org>
2008-10-10 19:43       ` Chong Yidong
     [not found]       ` <873aj48cd9.fsf@cyd.mit.edu>
2008-10-10 19:51         ` Chong Yidong
2008-10-10 21:32         ` Eli Zaretskii
2008-10-11 16:28         ` Stefan Monnier
     [not found]         ` <jwvbpxrkshx.fsf-monnier+emacsbugreports@gnu.org>
2008-10-11 19:49           ` Chong Yidong
     [not found]           ` <877i8edi9l.fsf@cyd.mit.edu>
2008-10-12  8:28             ` Andreas Schwab
2008-10-12  8:52             ` Andreas Schwab
     [not found]             ` <je1vym2o1m.fsf@sykes.suse.de>
2008-10-12 13:51               ` Chong Yidong
     [not found]               ` <87abd96hwo.fsf@cyd.mit.edu>
2008-10-12 14:31                 ` Andreas Schwab
     [not found]                 ` <jefxn128c4.fsf@sykes.suse.de>
2008-10-12 17:10                   ` Chong Yidong
2008-10-10  2:30 Chong Yidong

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='jwvej2omkrv.fsf-monnier+emacsbugreports__16280.5734006271$1223659995$gmane$org@gnu.org' \
    --to=monnier@iro.umontreal.ca \
    --cc=1133@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=dann@ics.uci.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.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).