* bug#9640: compilation bully mode
@ 2011-09-30 22:26 ` jidanni
2011-10-01 3:04 ` Stefan Monnier
` (3 more replies)
0 siblings, 4 replies; 14+ messages in thread
From: jidanni @ 2011-09-30 22:26 UTC (permalink / raw)
To: 9640
A Makefile or some other file occupies my entire screen.
I now do (compile "seq 999")
How can I make the *compilation* buffer now occupy the entire screen
with the bottom of the buffer visible, all with no additional
keystrokes? The hacks people gave me that I put into
http://jidanni.org/comp/configuration/.emacs no longer work as of
emacs-snapshot:
Installed: 1:20110926-1
and frankly I don't understand why there is no
(set Man-notify-method 'bully) like choice for compilation mode.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
@ 2011-09-30 22:29 jidanni
2011-10-01 9:08 ` martin rudalics
` (3 more replies)
0 siblings, 4 replies; 14+ messages in thread
From: jidanni @ 2011-09-30 22:29 UTC (permalink / raw)
To: 9641
(setq Man-notify-method 'bully); but q didn't put me back in my initial state:
E.g., with a split window, do M-x man cat, then type q.
Only one window is restored.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9640: compilation bully mode
2011-09-30 22:26 ` bug#9640: compilation bully mode jidanni
@ 2011-10-01 3:04 ` Stefan Monnier
2011-10-01 3:49 ` jidanni
` (2 subsequent siblings)
3 siblings, 0 replies; 14+ messages in thread
From: Stefan Monnier @ 2011-10-01 3:04 UTC (permalink / raw)
To: jidanni; +Cc: 9640
> A Makefile or some other file occupies my entire screen.
> I now do (compile "seq 999")
> How can I make the *compilation* buffer now occupy the entire screen
> with the bottom of the buffer visible, all with no additional
> keystrokes? The hacks people gave me that I put into
> http://jidanni.org/comp/configuration/.emacs no longer work as of
> emacs-snapshot:
> Installed: 1:20110926-1
> and frankly I don't understand why there is no
> (set Man-notify-method 'bully) like choice for compilation mode.
The Emacs-23 way to do that should be:
(add-to-list 'special-display-buffer-name
'(("*Compilation*" (same-window . t))))
Stefan
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9640: compilation bully mode
2011-09-30 22:26 ` bug#9640: compilation bully mode jidanni
2011-10-01 3:04 ` Stefan Monnier
@ 2011-10-01 3:49 ` jidanni
2011-10-01 4:00 ` Stefan Monnier
2011-10-01 4:16 ` jidanni
2011-10-01 14:22 ` bug#9640: I'll try pop-up-frames jidanni
3 siblings, 1 reply; 14+ messages in thread
From: jidanni @ 2011-10-01 3:49 UTC (permalink / raw)
To: monnier; +Cc: 9640
>>>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
SM> The Emacs-23 way to do that should be:
SM> (add-to-list 'special-display-buffer-name
SM> '(("*Compilation*" (same-window . t))))
How about for Emacs-24?
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9640: compilation bully mode
2011-10-01 3:49 ` jidanni
@ 2011-10-01 4:00 ` Stefan Monnier
0 siblings, 0 replies; 14+ messages in thread
From: Stefan Monnier @ 2011-10-01 4:00 UTC (permalink / raw)
To: jidanni; +Cc: 9640
SM> The Emacs-23 way to do that should be:
SM> (add-to-list 'special-display-buffer-name
SM> '("*Compilation*" (same-window . t)))
> How about for Emacs-24?
Backward compatibility requirements mean it will work as well.
But if you want to do it the Emacs-24 way, then you'll want to use
(add-to-list 'display-buffer-alist
'("*Compilation*" display-buffer-same-window))
Stefan
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9640: compilation bully mode
2011-09-30 22:26 ` bug#9640: compilation bully mode jidanni
2011-10-01 3:04 ` Stefan Monnier
2011-10-01 3:49 ` jidanni
@ 2011-10-01 4:16 ` jidanni
2011-10-01 14:44 ` Stefan Monnier
2011-10-01 14:22 ` bug#9640: I'll try pop-up-frames jidanni
3 siblings, 1 reply; 14+ messages in thread
From: jidanni @ 2011-10-01 4:16 UTC (permalink / raw)
To: monnier; +Cc: 9640
>>>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
SM> (add-to-list 'display-buffer-alist
SM> '("*Compilation*" display-buffer-same-window))
Sounds similar to the
(setq display-buffer-alist
(cons '(((regexp . "\\*compilation.+\\*"))
(function ; was "fun-with-args" before
(lambda (buffer &rest args)
(delete-other-windows)
(let (display-buffer-alist)
(display-buffer buffer 'same-window))))
(override . t))
display-buffer-alist))
in my http://jidanni.org/comp/configuration/.emacs that recently stopped
working :-(
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
2011-09-30 22:29 bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
@ 2011-10-01 9:08 ` martin rudalics
2011-10-01 9:26 ` jidanni
` (2 subsequent siblings)
3 siblings, 0 replies; 14+ messages in thread
From: martin rudalics @ 2011-10-01 9:08 UTC (permalink / raw)
To: jidanni; +Cc: 9641
> (setq Man-notify-method 'bully); but q didn't put me back in my initial state:
> E.g., with a split window, do M-x man cat, then type q.
> Only one window is restored.
Do you mean you have a frame with two windows, invoke man, type q in the
window used by man and get a frame with one window?
martin
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
2011-09-30 22:29 bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
2011-10-01 9:08 ` martin rudalics
@ 2011-10-01 9:26 ` jidanni
2011-10-01 10:05 ` martin rudalics
2011-10-01 10:14 ` jidanni
2011-10-01 11:55 ` bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
3 siblings, 1 reply; 14+ messages in thread
From: jidanni @ 2011-10-01 9:26 UTC (permalink / raw)
To: rudalics; +Cc: 9641
>>>>> "mr" == martin rudalics <rudalics@gmx.at> writes:
>> (setq Man-notify-method 'bully); but q didn't put me back in my initial state:
>> E.g., with a split window, do M-x man cat, then type q.
>> Only one window is restored.
mr> Do you mean you have a frame with two windows, invoke man, type q in the
mr> window used by man and get a frame with one window?
I think so. I never learned "frames". The problem I see is the same in
"emacs -nw" too.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
2011-10-01 9:26 ` jidanni
@ 2011-10-01 10:05 ` martin rudalics
0 siblings, 0 replies; 14+ messages in thread
From: martin rudalics @ 2011-10-01 10:05 UTC (permalink / raw)
To: jidanni; +Cc: 9641
> mr> Do you mean you have a frame with two windows, invoke man, type q in the
> mr> window used by man and get a frame with one window?
>
> I think so. I never learned "frames". The problem I see is the same in
> "emacs -nw" too.
Basically "bully" (in `Man-notify-when-ready') means
(bully
(and (frame-live-p saved-frame)
(select-frame saved-frame))
(pop-to-buffer man-buffer)
(delete-other-windows))
to pop to the man buffer in some window and to delete all other windows
on that frame. No command bound to `q' can restore any windows killed
by the `delete-other-windows' call. So if `q' earlier restored the
two-windows layout something strange must have happened. Maybe someone
can clarify ...
martin
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
2011-09-30 22:29 bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
2011-10-01 9:08 ` martin rudalics
2011-10-01 9:26 ` jidanni
@ 2011-10-01 10:14 ` jidanni
2011-10-01 10:58 ` martin rudalics
2011-10-01 11:55 ` bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
3 siblings, 1 reply; 14+ messages in thread
From: jidanni @ 2011-10-01 10:14 UTC (permalink / raw)
To: rudalics; +Cc: 9641
>>>>> "mr" == martin rudalics <rudalics@gmx.at> writes:
mr> to pop to the man buffer in some window and to delete all other windows
mr> on that frame. No command bound to `q' can restore any windows killed
mr> by the `delete-other-windows' call. So if `q' earlier restored the
mr> two-windows layout something strange must have happened. Maybe someone
mr> can clarify ...
It never did. I was hoping it would.
I was hoping to be able to see a man page and then have it go away
without side effects... Of course I never learned frames so I suppose
this is not a problem for most people.
I was also hoping to get a M-x compile command that would act like
'bully... I mentioned that in another bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
2011-10-01 10:14 ` jidanni
@ 2011-10-01 10:58 ` martin rudalics
2011-09-30 22:26 ` bug#9640: compilation bully mode jidanni
0 siblings, 1 reply; 14+ messages in thread
From: martin rudalics @ 2011-10-01 10:58 UTC (permalink / raw)
To: jidanni; +Cc: 9641
> I was hoping to be able to see a man page and then have it go away
> without side effects... Of course I never learned frames so I suppose
> this is not a problem for most people.
Indeed. You could try by setting `pop-up-frames' to t and see whether
it breaks too many of your earlier editing habits. If it does, you
might want to add all relevant buffer names (or suitable regexps) to
`special-display-buffer-names' (`special-display-regexps') and look
whether that solves your problems.
> I was also hoping to get a M-x compile command that would act like
> 'bully... I mentioned that in another bug.
Same here. You don't really want to use the same frame. You want to
use another frame and that should intuitively work well for text-only
terminals too.
martin
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9641: Man-notify-method 'bully does not remember how windows were
2011-09-30 22:29 bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
` (2 preceding siblings ...)
2011-10-01 10:14 ` jidanni
@ 2011-10-01 11:55 ` jidanni
3 siblings, 0 replies; 14+ messages in thread
From: jidanni @ 2011-10-01 11:55 UTC (permalink / raw)
To: rudalics; +Cc: 9641-done
>>>>> "mr" == martin rudalics <rudalics@gmx.at> writes:
mr> Indeed. You could try by setting `pop-up-frames' to t and see whether
Hmmm, aside from the scary flash upon the birth of the new window, I
think this is the greatest thing that has happened to me emacs-wise
since the 1980's. Speaking of which, here is a song,
* Devo - Speed Racer (1982-10-30)
http://www.youtube.com/watch?v=p07Pg5RZah0&list=PLF51D79F159020CC1
Thanks!
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9640: I'll try pop-up-frames
2011-09-30 22:26 ` bug#9640: compilation bully mode jidanni
` (2 preceding siblings ...)
2011-10-01 4:16 ` jidanni
@ 2011-10-01 14:22 ` jidanni
3 siblings, 0 replies; 14+ messages in thread
From: jidanni @ 2011-10-01 14:22 UTC (permalink / raw)
To: 9640-done
I'll try the pop-up-frames mentioned in Bug #9641, and reopen if still
having problems.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#9640: compilation bully mode
2011-10-01 4:16 ` jidanni
@ 2011-10-01 14:44 ` Stefan Monnier
0 siblings, 0 replies; 14+ messages in thread
From: Stefan Monnier @ 2011-10-01 14:44 UTC (permalink / raw)
To: jidanni; +Cc: 9640
> Sounds similar to the
> (setq display-buffer-alist
> (cons '(((regexp . "\\*compilation.+\\*"))
> (function ; was "fun-with-args" before
> (lambda (buffer &rest args)
> (delete-other-windows)
> (let (display-buffer-alist)
> (display-buffer buffer 'same-window))))
> (override . t))
> display-buffer-alist))
That's using a format of display-buffer-alist which we don't use any
more (i.e. it was only installed temporarily on the trunk and then
replaced by something else).
Stefan
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2011-10-01 14:44 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-30 22:29 bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
2011-10-01 9:08 ` martin rudalics
2011-10-01 9:26 ` jidanni
2011-10-01 10:05 ` martin rudalics
2011-10-01 10:14 ` jidanni
2011-10-01 10:58 ` martin rudalics
2011-09-30 22:26 ` bug#9640: compilation bully mode jidanni
2011-10-01 3:04 ` Stefan Monnier
2011-10-01 3:49 ` jidanni
2011-10-01 4:00 ` Stefan Monnier
2011-10-01 4:16 ` jidanni
2011-10-01 14:44 ` Stefan Monnier
2011-10-01 14:22 ` bug#9640: I'll try pop-up-frames jidanni
2011-10-01 11:55 ` bug#9641: Man-notify-method 'bully does not remember how windows were jidanni
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).