* compile.el compilation-start overrides frame preference
@ 2007-11-23 1:17 John J Foerch
2007-11-24 22:53 ` martin rudalics
0 siblings, 1 reply; 3+ messages in thread
From: John J Foerch @ 2007-11-23 1:17 UTC (permalink / raw)
To: emacs-devel
Hello,
In compile.el, the function `compilation-start' contains:
(setq outwin (display-buffer outbuf nil t))
The third parameter of display-buffer (given as `t' in this call)
overrides the user setting of display-buffer-reuse-frames. My
personal preference would be for compilation-start to not override my
setting of display-buffer-reuse-frames, but perhaps there should be a
new user variable in compile.el to control this behavior.
To give you an idea of why I encountered this: I use emacs' grep.el a
lot, which uses compile.el for its buffer output. I wanted to make
the `*grep*' buffer always appear in the selected frame, instead of
raising another frame is already displaying the *grep* buffer.
What do you think?
John Foerch
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: compile.el compilation-start overrides frame preference
2007-11-23 1:17 compile.el compilation-start overrides frame preference John J Foerch
@ 2007-11-24 22:53 ` martin rudalics
2007-11-25 15:29 ` Juri Linkov
0 siblings, 1 reply; 3+ messages in thread
From: martin rudalics @ 2007-11-24 22:53 UTC (permalink / raw)
To: John J Foerch; +Cc: emacs-devel
> In compile.el, the function `compilation-start' contains:
>
> (setq outwin (display-buffer outbuf nil t))
>
> The third parameter of display-buffer (given as `t' in this call)
> overrides the user setting of display-buffer-reuse-frames. My
> personal preference would be for compilation-start to not override my
> setting of display-buffer-reuse-frames, ...
I think so too. Does anyone see a problem with
(setq outwin (display-buffer outbuf))
here?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: compile.el compilation-start overrides frame preference
2007-11-24 22:53 ` martin rudalics
@ 2007-11-25 15:29 ` Juri Linkov
0 siblings, 0 replies; 3+ messages in thread
From: Juri Linkov @ 2007-11-25 15:29 UTC (permalink / raw)
To: martin rudalics; +Cc: John J Foerch, emacs-devel
>> In compile.el, the function `compilation-start' contains:
>>
>> (setq outwin (display-buffer outbuf nil t))
>>
>> The third parameter of display-buffer (given as `t' in this call)
>> overrides the user setting of display-buffer-reuse-frames. My
>> personal preference would be for compilation-start to not override my
>> setting of display-buffer-reuse-frames, ...
>
> I think so too. Does anyone see a problem with
>
> (setq outwin (display-buffer outbuf))
>
> here?
This change will also fix an old bug that when on a text-only terminal
grep was run on one virtual frame, then running it on another virtual
frame in the same Emacs frame doesn't display the grep buffer.
--
Juri Linkov
http://www.jurta.org/emacs/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-11-25 15:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-23 1:17 compile.el compilation-start overrides frame preference John J Foerch
2007-11-24 22:53 ` martin rudalics
2007-11-25 15:29 ` Juri Linkov
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.