From: "Drew Adams" <drew.adams@oracle.com>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: RE: pop-up-frames inconvenience
Date: Mon, 5 Jun 2006 08:26:55 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEAADHAA.drew.adams@oracle.com> (raw)
In-Reply-To: <alac8rzlkt.fsf@quant8.janestcapital.quant>
Hi Sam,
1. help-gnu-emacs@gnu.org is the proper list for this kind of question.
Followups there, please.
2. I've wrestled with trying to get Emacs to play well with a
one-frame-per-buffer (by default) behavior for a long time. Take a look at
my library oneonone.el. It might suit you, and, if not, it might give you
some ideas for your own customizations. See
http://www.emacswiki.org/cgi-bin/wiki/OneOnOneEmacs.
HTH.
--
when pop-up-frames is customized to t, the frames proliferate without
end and have to be explicitly deleted.
e.g., C-x m (`compose-mail') now creates a new frame that does not go
away automatically when I hit C-c C-c (`message-send-and-exit').
worse than that, when I hit TAB in the minibuffer, the *Completions*
window is now popped in its own frame, which has keyboard focus (thus
further typing results in errors unless I switch the keyboard focus to
the original frame) and obscures the original frame, hiding what I have
already typed.
--
I want buffers created by the emacs server to show up in their own
frames, so I do
(add-hook 'server-switch-hook 'new-frame)
(custom-set-variables '(server-window 'pop-to-buffer))
the result is that the server buffer is shown both in a new frame and a
new window in an existing frame.
neither *Help*, nor *info*, nor the source are helpful...
next prev parent reply other threads:[~2006-06-05 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 15:08 pop-up-frames inconvenience Sam Steingold
2006-06-05 15:26 ` Drew Adams [this message]
2006-06-05 19:58 ` Eli Zaretskii
2006-06-05 21:00 ` Drew Adams
2006-06-05 21:30 ` Sam Steingold
2006-06-06 6:53 ` Drew Adams
2006-06-06 21:13 ` Richard Stallman
2006-06-07 1:58 ` John S. Yates, Jr.
2006-06-05 15:31 ` Sam Steingold
2006-06-06 1:23 ` Stefan Monnier
2006-06-06 2:06 ` Richard Stallman
2006-06-06 12:50 ` Sam Steingold
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=DNEMKBNJBGPAOPIJOOICGEAADHAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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.
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).