From: Chong Yidong <cyd@stupidchicken.com>
To: Kenichi Handa <handa@m17n.org>
Cc: 553@emacsbugs.donarmstrong.com
Subject: bug#553: 23.0.60; Unknown button type `quail-keyboard-layout-button'
Date: Thu, 21 Aug 2008 19:41:58 -0400 [thread overview]
Message-ID: <87d4k27x6h.fsf@cyd.mit.edu> (raw)
Hi Handa-san,
> 1. `emacs -Q'
> 2. `M-: (require 'help-mode) RET'
> or run any Help command that loads this mode
> 3. Activate an input method by C-\
> 4. Click `mouse-3' on the input method's indicator
> on the mode-line
>
> It fills the *Help* buffer with the text only until
> it tries to create a button, and fails with the error
> "make-text-button: Unknown button type `quail-keyboard-layout-button'".
>
> This is because `quail-help-init' fails to define new button types.
> It currently has the form:
>
> (defun quail-help-init ()
> (unless (featurep 'help-mode)
> (require 'help-mode)
> (define-button-type 'quail-keyboard-layout-button
> :supertype 'help-xref
> 'help-function '(lambda (layout)
> (help-setup-xref `(quail-keyboard-layout-button ,layout)
> nil)
> (quail-show-keyboard-layout layout))
> 'help-echo (purecopy "mouse-2, RET: show keyboard layout"))
>
> (define-button-type 'quail-keyboard-customize-button
> :supertype 'help-customize-variable
> 'help-echo (purecopy "mouse-2, RET: customize keyboard layout"))))
>
> So it doesn't define two button types if `help-mode' is already loaded.
>
> I guess it was done to define them only once, and not redefine on next
> invocations.
Do you remember why you wrote quail-help-init this way? It seems
unnecessary; why not define the button types directly at the top level
of quail.el?
next reply other threads:[~2008-08-21 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 23:41 Chong Yidong [this message]
2008-08-25 15:52 ` bug#553: 23.0.60; Unknown button type `quail-keyboard-layout-button' Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 21:11 Chong Yidong
2008-07-12 22:04 Juri Linkov
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=87d4k27x6h.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=553@emacsbugs.donarmstrong.com \
--cc=handa@m17n.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 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.