unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>, emacs-devel@gnu.org
Subject: Re: A simple implementation of context-sensitive keys
Date: Sat, 13 Sep 2008 01:46:29 +0200	[thread overview]
Message-ID: <48CAFF55.5040508@gmail.com> (raw)
In-Reply-To: <87wshhpcjr.fsf@thinkpad.tsdh.de>

Tassilo Horn wrote:
> "Lennart Borgman" <lennart.borgman@gmail.com> writes:
> 
> Hi Lennart,
> 
>>> Sorry, no time to write the code now.  What I mean is that in
>>>
>>>  (info "(elisp)Searching Keymaps")
>>>
>>> there's the pseudocode how emacs finds the command for a key.  Now
>>> you can surrogate "FIND-IN" with lookup-key and see if the key is
>>> bound in the map.  In that code you know the map or at least the
>>> mode, cause you either have the variable directly (like
>>> overriding-local-map) or you walk an alist of the form ((mode-name
>>> . keymap)...) in the case of FIND-IN-ANY.
>> It would be good if that where true, but it is not. You have to take a
>> closer look to understand how this works. I think a good start might
>> be the code I sent before.
> 
> Here's a q&d implementation of what I thought should do the trick.  It
> works for me, although only very briefly tested.
> 
> --8<---------------cut here---------------start------------->8---
> (defun find-key-commands (key)
>   (let (list)
>     (when overriding-terminal-local-map


Yes, the structure of the key binding search must be mirrored in the
routine. But the problem I tried to solve was rather to find the keymap
variable names.

You do not have those names available anywhere really. You have to guess.

But combining the mirrored structure with the routine that guesses the
keymap variable name would be the best I think.




  reply	other threads:[~2008-09-12 23:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10  7:17 A simple implementation of context-sensitive keys Tassilo Horn
2008-09-10 10:36 ` Lennart Borgman (gmail)
2008-09-10 10:57   ` Tassilo Horn
2008-09-10 16:43     ` Ted Zlatanov
2008-09-10 14:14 ` Sean O'Rourke
2008-09-10 14:48   ` Miles Bader
2008-09-10 14:53     ` Juanma Barranquero
2008-09-10 15:17       ` Sean O'Rourke
2008-09-10 15:32         ` Juanma Barranquero
2008-09-11  7:35     ` Tassilo Horn
2008-09-11  8:17       ` Miles Bader
2008-09-11  8:48         ` Tassilo Horn
2008-09-10 17:49 ` Stefan Monnier
2008-09-10 19:21   ` Tassilo Horn
2008-09-11  1:41     ` Stefan Monnier
2008-09-11  7:17       ` Tassilo Horn
2008-09-11 14:40         ` Ted Zlatanov
2008-09-11 15:53           ` Tassilo Horn
2008-09-11 13:41       ` Lennart Borgman (gmail)
2008-09-11 13:48         ` Lennart Borgman (gmail)
2008-09-11 14:22           ` Tassilo Horn
2008-09-11 20:38             ` Lennart Borgman (gmail)
2008-09-12  6:58               ` Tassilo Horn
2008-09-12  8:34                 ` Lennart Borgman (gmail)
2008-09-12  9:47                   ` Tassilo Horn
2008-09-12 11:00                     ` Lennart Borgman
2008-09-12 16:13                       ` Tassilo Horn
2008-09-12 23:46                         ` Lennart Borgman (gmail) [this message]
2008-09-13  7:28                           ` Tassilo Horn
2008-09-13  9:32                             ` Lennart Borgman (gmail)
2008-09-15  7:26                               ` Tassilo Horn
2008-09-15 22:39                                 ` Lennart Borgman (gmail)
2008-09-11 20:44         ` Stefan Monnier
2008-09-11 21:14           ` Lennart Borgman (gmail)
2008-09-12  1:33             ` Stefan Monnier
2008-09-12  8:29               ` Lennart Borgman (gmail)

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=48CAFF55.5040508@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=tassilo@member.fsf.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).