From: Richard Riley <rileyrg@googlemail.com>
To: emacs-devel@gnu.org
Subject: Re: Usage examples of dedicated windows and popup frames?
Date: Fri, 08 Jul 2011 16:47:37 +0200 [thread overview]
Message-ID: <cqsjqgkewm.fsf@news.eternal-september.org> (raw)
In-Reply-To: 871uy0n9ch.fsf@member.fsf.org
Tassilo Horn <tassilo@member.fsf.org> writes:
> Hi all,
>
> my probably most frequently used emacs keys are `ESC ESC ESC' and `C-x
> b' which somehow suggests that I might want to improve my window/frame
> management.
>
> Since lately I've read of many people on this list that they are using
> dedicated windows, dedicated minibuffer frames, and popup frames. I've
> briefly checked the docs. Well, that explains all variables and
> functions, but it doesn't really help finding some appealing overall
> configuration that just works for me.
>
> As a self-experiment, I've just evaluated
>
> (setq pop-up-frames 'graphic-only
> display-buffer-reuse-frames t)
>
> in *scratch* to try out something completely different from the default
> behavior. And basically I it's not that bad. But after using it for an
> hour, I have more than 10 open emacs frames now. Most of them were
> opened for showing completion possibilities, but after I've finished
> completion they became useless. It would be great if those would be
> closed automagically...
>
> Long story short: it would be nice if some people with non-standard
> window/frame settings could share and briefly explain their
> configuration. I'm very interested.
>
> And maybe it's a good idea to ship emacs with some predefined setups
> users can easily try out and then extend to find one that suits them
> best, for example, the current default window oriented configuration, a
> more frame oriented configuration, and a frame oriented configuration
> with a dedicated minibuffer frame, too.
Have a look at Icicles too ....
next prev parent reply other threads:[~2011-07-08 14:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 14:19 Usage examples of dedicated windows and popup frames? Tassilo Horn
2011-07-08 14:47 ` Richard Riley [this message]
2011-07-08 14:49 ` John Yates
2011-07-08 16:11 ` Stefan Monnier
2011-07-08 16:34 ` Drew Adams
2011-07-08 16:51 ` Stefan Monnier
2011-07-08 17:38 ` Drew Adams
2011-07-08 17:54 ` Tassilo Horn
2011-07-08 18:55 ` Stefan Monnier
2011-07-09 13:00 ` martin rudalics
2011-07-09 15:03 ` Drew Adams
2011-07-10 0:43 ` chad
2011-07-10 9:00 ` martin rudalics
2011-07-10 9:43 ` Drew Adams
2011-07-12 17:47 ` chad
2011-07-12 18:55 ` Drew Adams
2011-07-13 6:24 ` martin rudalics
2011-07-13 23:09 ` chad
2011-07-10 23:45 ` undisplay temporary dialog buffers when done [was: ... dedicated windows and popup frames] Drew Adams
2011-07-09 17:22 ` Usage examples of dedicated windows and popup frames? Tassilo Horn
2011-07-10 9:00 ` martin rudalics
2011-07-10 9:39 ` Tassilo Horn
2011-07-10 15:30 ` martin rudalics
2011-07-10 16:00 ` Tassilo Horn
2011-07-10 21:13 ` Drew Adams
2011-07-08 16:11 ` Drew Adams
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=cqsjqgkewm.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.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).