emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

customize-*-other-window cmds don't respect special-display* values


From: Drew Adams
Subject: customize-*-other-window cmds don't respect special-display* values
Date: Sun, 16 Jan 2005 10:05:58 -0800

I have (setq special-display-regexps '("[ ]?[*][^*]+[*]")), and I display
special-display buffers in a different kind of frame (via
special-display-frame-alist). I also use (setq pop-up-frames t), so
other-window acts like other-frame.

I have also removed customized buffers from `same-window-buffer-names', so
that customize will open a separate frame for each of its buffers.

All of the customize commands work correctly, except for the *-other-window
commands. The *-other-window commands do not respect
special-display-regexps, so I don't get the proper frame, as defined by
special-display-frame-alist.

The reason is apparently this, in the definition, for instance, of
customize-group-other-window:

(let ((window (selected-window))
              ;; Copied from `custom-buffer-create-other-window'.
              (pop-up-windows t)
              (special-display-buffer-names nil)
              (special-display-regexps nil)
              (same-window-buffer-names nil)
              (same-window-regexps nil))
          (pop-to-buffer name)
          (select-window window))

To me, this is a bug - setting the special-display* variables to nil
short-circuits my attempts to make the customize-*-other-window commands
behave as the other customize buffers behave.

This bug exists in both Emacs 20.7 and Emacs 21.3.50, BTW.

Thanks,

  Drew

In GNU Emacs 21.3.50.1 (i386-mingw-nt5.1.2600)
 of 2004-07-26 on BERATUNG4
configured using `configure --with-gcc
(3.3) --cflags -I../../jpeg-6b-1/include -I../../libpng-1.2.4-1/include -I..
/../tiff-3.5.7/include -I../../xpm-nox-4.2.0/include -I../../zlib-1.1.4-1/in
clude'





reply via email to

[Prev in Thread] Current Thread [Next in Thread]