From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] mouse-1 click follows link
Date: Sun, 31 Oct 2004 09:24:06 -0600 (CST) [thread overview]
Message-ID: <200410311524.i9VFO6v05450@raven.dms.auburn.edu> (raw)
In-Reply-To: <m3mzy3giav.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
Kim Storm wrote:
I don't see how this would work -- the mouse-2 binding is typically
made in a keymap property on the link itself, as even things that
_are_ links use different bindings for mouse-2.
So how can you use a global map for links ?
I was thinking of a common _parent_ keymap, say `link-keymap' for
links. In fact, no separate `link' property would be needed. Each
kind of link would use its individual keymap, but would do:
(set-keymap-parent this-keymap link-keymap)
link-keymap would be a customizable variable with predefined values.
Maybe there are problems with this, but I do not immediately see them.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-10-31 15:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 13:04 [PATCH] mouse-1 click follows link Kim F. Storm
2004-10-29 23:54 ` Luc Teirlinck
2004-10-30 22:04 ` Kim F. Storm
2004-10-31 0:09 ` Luc Teirlinck
2004-10-31 12:49 ` Kim F. Storm
2004-11-01 7:24 ` Richard Stallman
2004-10-31 0:34 ` Luc Teirlinck
2004-10-31 12:53 ` Kim F. Storm
2004-10-31 15:24 ` Luc Teirlinck [this message]
2004-10-31 18:37 ` David Kastrup
2004-10-31 20:03 ` Luc Teirlinck
2004-10-31 20:13 ` David Kastrup
2004-10-31 21:40 ` Stefan
2004-10-31 23:39 ` Kim F. Storm
2004-11-01 0:33 ` Stefan
2004-11-27 0:44 ` [NEW PATCH] " Kim F. Storm
[not found] ` <E1CYJ5T-0002qS-UR@fencepost.gnu.org>
2004-12-14 15:15 ` Kim F. Storm
2004-12-14 20:13 ` Robert J. Chassell
2004-12-14 23:33 ` Kim F. Storm
2004-12-16 23:08 ` Kevin Rodgers
2004-12-17 9:57 ` Kim F. Storm
2004-12-17 10:20 ` Alex Schroeder
2004-12-15 8:46 ` Richard Stallman
2004-12-16 12:24 ` Richard Stallman
2004-12-16 15:12 ` Kim F. Storm
2004-12-18 0:20 ` Richard Stallman
2004-12-18 13:50 ` Robert J. Chassell
2004-12-17 15:48 ` Kim F. Storm
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=200410311524.i9VFO6v05450@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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).