From: jidanni@jidanni.org
To: ttn@gnuvola.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: all I wanted to do was make *compilation* the sole visible buffer
Date: Fri, 09 Dec 2011 07:46:06 +0800 [thread overview]
Message-ID: <87y5umtyo1.fsf@jidanni.org> (raw)
In-Reply-To: mailman.2070.1323182415.798.help-gnu-emacs@gnu.org
>>>>> "TN" == Thien-Thi Nguyen <ttn@gnuvola.org> writes:
TN> (defun solipsistic-child (process)
TN> "Me, me, look at me!"
TN> (with-current-buffer (process-buffer process)
TN> (delete-other-windows)))
TN> (add-hook 'compilation-start-hook 'solipsistic-child)
Very nice, except it leaves the user staring at the... Makefile, not *compilation*.
next parent reply other threads:[~2011-12-08 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2070.1323182415.798.help-gnu-emacs@gnu.org>
2011-12-08 23:46 ` jidanni [this message]
2011-12-10 21:02 ` all I wanted to do was make *compilation* the sole visible buffer Thien-Thi Nguyen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5umtyo1.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=help-gnu-emacs@gnu.org \
--cc=ttn@gnuvola.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.
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).