unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: [display-buffer] a way to make it behave as before?
Date: Mon, 20 Jun 2011 14:39:11 +0900	[thread overview]
Message-ID: <b4mtybljc3k.fsf@jpl.org> (raw)
In-Reply-To: 4DFB7705.2000401@gmx.at

(I believe I use the most recent bzr Emacs 24.)

>> I'm fiddling `display-buffer-alist' and others so as to make
>> `display-buffer' behave as before, though I didn't find out a
>> smart way so far.  What behavior I want is:
>>
>> `find-file-other-window' opens a file in the other window of
>> the frame when the frame is split into two windows.  Don't split
>> either of two windows into two, IOW don't change the window
>> configuration of the frame[1].

> I just provided a new specifier for `display-buffer-alist' called
> other-window-means-other-frame.  Please set it and tell me whether it
> works (Sometimes I wonder what `find-file-other-frame' is for ;-)).

Where/How can I find that specifier in the customization buffer?
Ok.  I tried those two:

(progn
  (makunbound 'display-buffer-alist)
  (load "window")
  (setcdr (car display-buffer-alist)
          (append (cdar display-buffer-alist)
                  '((other-window-means-other-frame . nil)))))

(progn
  (makunbound 'display-buffer-alist)
  (load "window")
  (setcdr (car display-buffer-alist)
          (append '((other-window-means-other-frame . nil))
                  (cdar display-buffer-alist))))

But I saw no difference.  `C-x 4 f' or `C-x 4 b' still opens a file
or a buffer in a new frame, or another existing frame that already
displays its window.  In the later case, I cannot see it immediately
if that frame is hidden by other applications or iconified.

I only want to see it in the other window of the current frame.

>> Even if there is a window that
>> visits the file in another frame, don't use it[2].

> Does this mean that in Emacs 23 you have `display-buffer-reuse-frames'
> nil and `pop-up-frames' t?

No, both are nil.  I leave most such options the default.

> Anyway.  Why don't you remove all instances of reuse-window from
> `display-buffer-alist' that would use a window on another frame, that
> is, use only instances of the (reuse-window ... ... nil) type.  This way
> a window gets reused iff it's on the selected frame.

The main reason I want to do all within the current frame is because
Emacs doesn't raise a hidden frame.  On cygwin (I use it in the office)
and on Fedora 14 Linux (I use it in home), Emacs puts a newly created
frame on the top of the screen, but it doesn't for a frame that exists
but is hidden.

As for Fedora 14, I use an external program called `wmctrl' to make
`raise-frame' work, but it has no effect on cygwin.  Cf.
http://lists.gnu.org/archive/html/emacs-devel/2006-10/msg01117.html

>> As for the `other-window' specifier, it seems there's no way to
>> customize so as to make it behave as above.  (It might be
>> `display-buffer-macro-specifiers', but it's a constant.)

> It's been already removed from there.  Please have a look.

Confirmed.  Thanks.

>> I wish there were a switch that makes it behave as before. ;-)
>>
>> [1] I don't want an Emacs frame to be split into many windows,
>>     because the screen height of my note is not so high, and
>>     a font I use is not so small.
>> [2] `raise-frame' doesn't work on cygwin (and possibly some
>>     window managers, like metacity).



  reply	other threads:[~2011-06-20  5:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17  9:54 [display-buffer] a way to make it behave as before? Katsumi Yamaoka
2011-06-17 15:47 ` martin rudalics
2011-06-20  5:39   ` Katsumi Yamaoka [this message]
2011-06-20  6:21     ` Katsumi Yamaoka
2011-06-20  9:25     ` martin rudalics
2011-06-20 10:39       ` Katsumi Yamaoka
2011-06-20 12:23         ` martin rudalics
2011-06-20 23:04           ` Katsumi Yamaoka
2011-06-21  2:11             ` Katsumi Yamaoka
2011-06-21 14:05               ` Katsumi Yamaoka
2011-06-21 16:11               ` martin rudalics
2011-06-22  1:13                 ` Katsumi Yamaoka
2011-06-22  7:20                   ` martin rudalics
2011-06-22 13:32                     ` Katsumi Yamaoka
2011-06-22 13:45                       ` martin rudalics
2011-06-22 14:32                         ` Drew Adams
2011-06-22 14:59                         ` joakim
2011-06-23  5:07                           ` Miles Bader
2011-06-22 16:43                         ` Thierry Volpiatto
2011-06-23  6:40                         ` Katsumi Yamaoka
2011-06-23  9:48                           ` martin rudalics
2011-06-23 10:21                             ` Katsumi Yamaoka
2011-06-23 11:08                               ` martin rudalics
2011-06-23 11:52                                 ` David Kastrup
2011-06-22 15:13                       ` Juanma Barranquero
2011-06-22 23:20                         ` Katsumi Yamaoka
2011-06-23  0:23                           ` Juanma Barranquero

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=b4mtybljc3k.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).