From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: I wish list-buffers used my current window when it listed my buffers
Date: Sat, 17 Aug 2013 01:24:19 +0200 [thread overview]
Message-ID: <87y5811aos.fsf@web.de> (raw)
In-Reply-To: E34C41DE-8163-4968-8F4F-D3E4B9D471AB@gmail.com
Jay Cotton <jay.cotton@gmail.com> writes:
> Also, the window behavior prefix command sounds like a neat idea. It
> seems like it would have to be either:
>
> a) different for different commands, in order to maintain existing
> differences in prefix args (ie., C-u C-x 'some-command might already
> mean something)
>
> or
>
> b) obscure enough that it would risk being tedious to use
An example:
C-x C-b acts according to your default.
C-x 4 C-x C-b would pop up a new window and use it.
C-x 5 C-x C-b would create a new frame and use it.
C-x 4 and C-x 5 are already a prefixes (in the sense of key bindings), but
not realized as commands.
You would still be able to use prefix args, like
C-x 5 C-u 1 C-x C-b
> right? A difficult task indeed, I hope I can help somehow.
These are future plans.
I tried to implement something like this for myself, but discarded it.
The concept is easy, but the details are not. For example, if you use
C-x 5 before a command that at first reads in a string with completion,
do you want your completion list to appear in a new frame when hitting
TAB? Probably not. Commands that display multiple new buffers are
problematic.
Michael.
next prev parent reply other threads:[~2013-08-16 23:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 2:02 I wish list-buffers used my current window when it listed my buffers Jay Cotton
2013-08-15 4:56 ` Bob Proulx
[not found] ` <mailman.16.1376542594.10748.help-gnu-emacs@gnu.org>
2013-08-15 12:45 ` Dan Espen
2013-08-15 23:23 ` Jay Cotton
2013-08-16 13:33 ` Michael Heerdegen
2013-08-16 13:33 ` Michael Heerdegen
2013-08-16 22:12 ` Jay Cotton
2013-08-16 23:24 ` Michael Heerdegen [this message]
[not found] ` <mailman.163.1376660121.10748.help-gnu-emacs@gnu.org>
2013-08-16 14:03 ` Dan Espen
2013-08-16 22:33 ` Jay Cotton
2013-08-16 22:51 ` Bob Proulx
2013-08-16 23:38 ` Jay Cotton
2013-08-20 23:07 ` Stefan Monnier
[not found] ` <mailman.447.1377040083.10748.help-gnu-emacs@gnu.org>
2013-08-21 4:51 ` Rustom Mody
2013-08-21 22:55 ` Bob Proulx
[not found] ` <mailman.532.1377125749.10748.help-gnu-emacs@gnu.org>
2013-08-22 4:44 ` Rustom Mody
2013-08-16 23:08 ` Michael Heerdegen
2013-08-16 23:44 ` Jay Cotton
2013-08-16 23:51 ` Jay Cotton
[not found] ` <mailman.210.1376693505.10748.help-gnu-emacs@gnu.org>
2013-08-16 23:14 ` Dan Espen
2013-08-19 3:41 ` Samuel Wales
[not found] <mailman.11.1376532793.10748.help-gnu-emacs@gnu.org>
2013-08-15 3:42 ` Rustom Mody
2013-08-15 4:54 ` Eric Abrahamsen
2013-08-15 7:31 ` Thorsten Jolitz
2013-08-15 12:32 ` Michael Heerdegen
2013-08-15 12:59 ` Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5811aos.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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 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.