all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@gnu.org>
Cc: 8397@debbugs.gnu.org
Subject: bug#8397: 24.0.50; defcustom :type face
Date: Mon, 6 Feb 2012 07:23:39 -0800	[thread overview]
Message-ID: <EECB55497E1F40CE8A261F42A4A7D245@us.oracle.com> (raw)
In-Reply-To: <87ipjkmc6g.fsf@gnu.org>

> > If you make the *Completions* window dedicated (e.g. (setq
> > special-display-regexps '("[ ]?[*][^*]+[*]"))), then M-TAB switches
> > the focus to the *Completions* frame each time you hit it.  
> > That means you cannot just continue to type text into the
> > edit field - you must first reselect the customize frame
> > to give it focus.
> 
> This is an inherent limitation of special-display-regexps.  It is
> possible to use display-buffer-alist to get the same effect while
> leaving an exception for *Completions*.

Sorry, but that is just irrelevant.

Obviously, I _want_ *Completions* to be special-display, or I wouldn't have
provided a recipe that makes it so.

Saying that the problem I describe does not exist if you do not follow the
recipe that shows the problem is, well, a bit of a cop-out, don't you think?

The problem described is a problem with a special-display *Completions* buffer.
It is not a limitation of `special-display-regexps'.  There is nothing
particular that `display-buffer-alist' offers to solve this problem, AFAIK.
What's required is redirecting the *Completions* frame focus to the minibuffer.






      reply	other threads:[~2012-02-06 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 17:45 bug#8397: 24.0.50; defcustom :type face Drew Adams
2012-02-05 16:03 ` Chong Yidong
2012-02-05 18:23   ` Drew Adams
2012-02-06 11:30     ` Chong Yidong
2012-02-06 15:23       ` Drew Adams [this message]

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=EECB55497E1F40CE8A261F42A4A7D245@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=8397@debbugs.gnu.org \
    --cc=cyd@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 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.