all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: Re: [display-buffer] a way to make it behave as before?
Date: Fri, 17 Jun 2011 17:47:17 +0200	[thread overview]
Message-ID: <4DFB7705.2000401@gmx.at> (raw)
In-Reply-To: <b4mei2svl4o.fsf@jpl.org>

 > 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 ;-)).

 > 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?

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.

 > 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.

 > 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).

martin



  reply	other threads:[~2011-06-17 15:47 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 [this message]
2011-06-20  5:39   ` Katsumi Yamaoka
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DFB7705.2000401@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=yamaoka@jpl.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.