From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, Drew Adams <drew.adams@oracle.com>
Cc: 2270@emacsbugs.donarmstrong.com,
Chong Yidong <cyd@stupidchicken.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
2270@debbugs.gnu.org
Subject: bug#2270: [PATCH] bug#2270, RE: 23.0.90; find-library:... (2) other-window version
Date: Wed, 27 Apr 2016 20:43:15 +0300 [thread overview]
Message-ID: <636c5081-9c37-5eb4-ca6b-d44c654bd0e2@yandex.ru> (raw)
In-Reply-To: <871t5rgdfp.fsf@gnus.org>
On 04/27/2016 08:38 PM, Lars Ingebrigtsen wrote:
> `find-library' isn't bound to any key, but I think it probably should
> be. `C-x 4 l' seems like as good a keystroke as any. Any thought from
> other people? I use the command quite a lot...
I think the "other window" version should simply be a separate command,
like find-function-other-window, xref-find-definitions-other-window, etc.
Having a default binding for it would be a bit odd, considering
find-library doesn't have one.
>> 2. I think that the other-window version is far more useful than
>> the same-window version. So if other-window behavior is available
>> only via a prefix arg I'd prefer that it be the other way around:
>> a prefix arg uses the same window; no prefix arg uses another
>> window. (Yes, that would be a change in the default behavior.)
-1 from me.
> The command now uses pop-to-buffer-same-window, which is quite
> customisable, as I understand things. (I haven't looked into the
> new-fangled window popping controlling functions.) So I think this
> should be customisable ... somehow ... by the users now.
It's... not as easy as one might hope. And if you customize
`find-library' to use the other window this way, there will be no way to
have it use the current window just this one time. And vice versa.
next prev parent reply other threads:[~2016-04-27 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 2:27 bug#2270: 23.0.90; find-library: (1) doc string, (2) other-window version Chong Yidong
2012-10-24 17:41 ` bug#2270: [PATCH] bug#2270, RE: 23.0.90; find-library:... " Drew Adams
[not found] ` <jwv3913g142.fsf-monnier+emacs@gnu.org>
2012-10-24 19:38 ` Drew Adams
2012-10-24 20:42 ` Stefan Monnier
2012-10-24 21:20 ` Stefan Monnier
2012-10-24 21:25 ` Drew Adams
2016-04-27 17:26 ` Lars Ingebrigtsen
2016-04-27 17:34 ` Drew Adams
2016-04-27 17:38 ` Lars Ingebrigtsen
2016-04-27 17:43 ` Dmitry Gutov [this message]
2016-04-27 17:56 ` Lars Ingebrigtsen
2016-04-27 18:57 ` Dmitry Gutov
2016-04-27 18:46 ` Stefan Monnier
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=636c5081-9c37-5eb4-ca6b-d44c654bd0e2@yandex.ru \
--to=dgutov@yandex.ru \
--cc=2270@debbugs.gnu.org \
--cc=2270@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).