(next-error) and buffer popups

(next-error) and buffer popups

[Sam Halliday]

Hello all,

I typically have a couple of emacs frames on my desktop because I have a multi-monitor setup.

I usually have the compile buffer open in one of the secondary frames, but the behaviour of (next-error) is a bit frustrating because it will always open the compile buffer in a new window in whatever frame I invoke it from. This results in two windows in my field of view showing the same information.

Is there an alternative to (next-error) which does the same "jump to error in source" behaviour but doesn't popup the compile buffer? The following logic would be perfect:

  (when (compile-buffer-not-visible)
    (popup-compile-buffer-in-current-frame))
  (goto-errored-source-file-and-line)

Best regards,
Sam

Re: (next-error) and buffer popups

[Dmitry Gutov]

On 05/18/2015 12:06 PM, Sam Halliday wrote:

> I usually have the compile buffer open in one of the secondary frames, but the behaviour of (next-error) is a bit frustrating because it will always open the compile buffer in a new window in whatever frame I invoke it from. This results in two windows in my field of view showing the same information.

I'm pretty sure this behavior is a bug which should be fixed.

Re: (next-error) and buffer popups

[Stefan Monnier]

> I typically have a couple of emacs frames on my desktop because I have
> a multi-monitor setup.

Are these monitors considered separate displays or are they combined
into one giant display (e.g. can you seamlessly move a frame fro one
monitor to the other)?


        Stefan

Re: (next-error) and buffer popups

[Sam Halliday]

On Monday, 18 May 2015 16:46:38 UTC+1, Stefan Monnier  wrote:
> > I typically have a couple of emacs frames on my desktop because I have
> > a multi-monitor setup.
> 
> Are these monitors considered separate displays or are they combined
> into one giant display (e.g. can you seamlessly move a frame fro one
> monitor to the other)?

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

Re: (next-error) and buffer popups

[Stefan Monnier]

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

The separate displays may still matter in the end, because Emacs is also
designed to work in conditions where frames are displayed in fully independent
displays located in different places (one in the office and one at
home, say), so it sometimes considers "frames in another display" as
invisible, just like iconified frames (except they can't be deiconified).


        Stefan

Re: (next-error) and buffer popups

[Sam Halliday]

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

Re: (next-error) and buffer popups

[ISHIKAWA,chiaki]

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