all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>
To: Sam Halliday <sam.halliday@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: (next-error) and buffer popups
Date: Thu, 21 May 2015 10:02:40 +0900	[thread overview]
Message-ID: <555D2EB0.6040504@yk.rim.or.jp> (raw)
In-Reply-To: <2264e862-b616-4fa7-ab0d-9bf3dc4cb4a1@googlegroups.com>

On 2015/05/19 18:59, Sam Halliday wrote:
> On Monday, 18 May 2015 18:38:46 UTC+1, Stefan Monnier  wrote:
>>> They are separate displays, but that shouldn't matter here because the
>>> behaviour is the same even if two frames are positioned to be in the same
>>> monitor (or, indeed, if I only have one monitor and two frames).
>>
>> It looks like it's indeed not to source of your problem.  The first
>> thing to check is your setting for display-buffer-reuse-frames.
>
> Aha! That was it! And, of course, now that I know what to look for I'm able to find lots of other people asking the same thing
>
> http://stackoverflow.com/questions/3311577
>
>
> Thank you,
> Sam
>
>

In the tiny print at the end of above URL, I see

 > This variable is obsolete since 24.3; use a 'reusable-frames' alist
 > entry in 'display-buffer-alist'. –  cYrus Jan 3 at 13:02

What exactly should we do?

TIA




      reply	other threads:[~2015-05-21  1:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  9:06 (next-error) and buffer popups Sam Halliday
2015-05-18 13:33 ` Dmitry Gutov
2015-05-18 15:45 ` Stefan Monnier
     [not found] ` <mailman.3210.1431963996.904.help-gnu-emacs@gnu.org>
2015-05-18 16:02   ` Sam Halliday
2015-05-18 17:38     ` Stefan Monnier
     [not found]     ` <mailman.3221.1431970724.904.help-gnu-emacs@gnu.org>
2015-05-19  9:59       ` Sam Halliday
2015-05-21  1:02         ` ISHIKAWA,chiaki [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=555D2EB0.6040504@yk.rim.or.jp \
    --to=ishikawa@yk.rim.or.jp \
    --cc=help-gnu-emacs@gnu.org \
    --cc=sam.halliday@gmail.com \
    /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.