From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: michael_heerdegen@web.de, 11233@debbugs.gnu.org
Subject: bug#11233: 24.1.50; Wishlist: dired mouse-2 other window behavior
Date: Sat, 06 Oct 2012 09:48:55 -0400 [thread overview]
Message-ID: <jwvvcenzpgz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <50702A93.7060008@gmx.at> (martin rudalics's message of "Sat, 06 Oct 2012 14:56:51 +0200")
> + (define-key map [mouse-1] 'dired-mouse-find-file-this-window)
I don't think we can use this by default (but a user can have it as
a local customization, of course).
> Alternatively, we could bind mouse-2 to a command
> `dired-mouse-find-file' which according to some option say
> `dired-mouse-find-file-other-window' would visit the file in the
> selected or another window.
I hope we can start moving in this direction, indeed.
As mentioned months ago, I'd like to move away from all the
foo(|-other-(frame-window)) madness since I suspect that most users
only use one of those alternatives.
So instead, we should only have `find-file' (which the user could
customize the use this-window, other-window, or other-frame) and that
would be complemented by new prefix commands that cause the next command
to use "other-window" or "this-window" or "other-frame".
Stefan
next prev parent reply other threads:[~2012-10-06 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 3:34 bug#11233: 24.1.50; Wishlist: dired mouse-2 other window behavior Michael Heerdegen
2012-10-06 12:56 ` martin rudalics
2012-10-06 13:48 ` Stefan Monnier [this message]
2012-10-06 17:19 ` martin rudalics
2012-10-06 18:14 ` Stefan Monnier
2012-10-08 6:57 ` martin rudalics
2012-10-08 11:05 ` Juri Linkov
2012-10-08 13:33 ` Drew Adams
2012-10-09 9:36 ` martin rudalics
2012-10-09 23:15 ` Juri Linkov
2012-10-08 14:12 ` Stefan Monnier
2012-11-13 13:50 ` martin rudalics
2012-11-13 17:42 ` Stefan Monnier
2012-11-14 15:35 ` Michael Heerdegen
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=jwvvcenzpgz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11233@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=rudalics@gmx.at \
/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).