unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Inactive Minibuffer Requires Redisplay for Input Methods
Date: Wed, 8 Jan 2003 14:16:27 +0900 (JST)	[thread overview]
Message-ID: <200301080516.OAA00596@etlken.m17n.org> (raw)
In-Reply-To: <m2k7hijihz.fsf@owlbear.local> (message from Andrew Choi on Mon, 06 Jan 2003 10:27:52 -0700)

In article <m2k7hijihz.fsf@owlbear.local>, Andrew Choi <akochoi@shaw.ca> writes:

> Certain Quail input methods display a list of word choices in an
> /inactive/ minibuffer for the user to select by typing 0 to 9.  The
> change below in xdisp.c (redisplay_window) prevents this minibuffer from
> being displayed.

> To see a manifestation of the problem, switch to the input method
> chinese-ctlaub, for example, and type `ngoh'.  Before the change, a list
> of choices labeled by their respective numbers are displayed in the
> minibuffer.  After the change they don't appear.

> -----
> 2002-12-22  Richard M. Stallman  <rms@gnu.org>

> 	* xdisp.c (try_cursor_movement): Don't call try_window here.
> 	(redisplay_window): Never redisplay minibuffer when inactive.

The reason why Quail does that is that the text must be shown
with some face.  Previously, we couldn't use `message' for
that.   But, now we can do something like this:
  (message (propertize "hello" 'face 'highlight))
So, if requested, I can make quail to use `message' instead
of minibuffer.  Actually, that change will make the code
simpler.  The only drawback I can think of now is that it
consumes *Messages* buffer too much.

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2003-01-08  5:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 17:27 Inactive Minibuffer Requires Redisplay for Input Methods Andrew Choi
2003-01-08  5:16 ` Kenichi Handa [this message]
2003-01-08  6:58   ` Miles Bader
2003-01-08 10:13   ` Kim F. Storm

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=200301080516.OAA00596@etlken.m17n.org \
    --to=handa@m17n.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).