unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: michael_heerdegen@web.de, 11233@debbugs.gnu.org
Subject: bug#11233: 24.1.50; Wishlist: dired mouse-2 other window behavior
Date: Tue, 09 Oct 2012 11:36:23 +0200	[thread overview]
Message-ID: <5073F017.4090501@gmx.at> (raw)
In-Reply-To: <87391p19lv.fsf@mail.jurta.org>

 > I suggest to use the same modifiers as used in web browsers:
 > mouse-1 opens in the same window, C-mouse-1 opens in other window
 > (not selected), C-S-mouse-1 opens in other window (and selected),

Does this mean the buffer would appear in two windows?  On Firefox
C-S-mouse-1 behaves just as C-mouse-1 here.

 > S-mouse-1 opens in other frame.

Would we decode this in `find-file' or `dired-find-file'?  IIUC we'd
have to check

(a) whether the mouse was used at all and, if so, which modifier was
     applied,

(b) whether the mouse was over a text with a this-window / other-window
     / other-frame interpretation, and

(c) what any user customizations wrt prefix key and modifiers are in the
     present context.

`push-button' and `button-activate' do something related.  Could we
interact with these functions?

martin





  parent reply	other threads:[~2012-10-09  9:36 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
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 [this message]
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=5073F017.4090501@gmx.at \
    --to=rudalics@gmx.at \
    --cc=11233@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=michael_heerdegen@web.de \
    /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).