Re: Scanning keymaps for keybindings

Re: Scanning keymaps for keybindings

[despen]

Elena <egarrulo@gmail.com> writes:

> Hello,
>
> I'd like to remap some keybindings in different contexts, for
> consistency.
>
> I've read the relevant section of the Elisp manual, but it seems there
> is no way to list all keymaps variables for a search.  `current-active-
> maps' returns the value of keymaps, not keymaps' variables' names.
>
> I think I could list all variables and then pattern match them against
> ".*-map$".  `describe-variable' lists variables, but I've not been
> able to extract the variable listing code.
>
> Any help? Thanks.

^h m

You need to issue that in each mode you want to fool with.

I'm not sure what you mean by keymap variables.
Are you after all the modes you are using?

Most people (myself), just start with the global-map and then
make mode bindings as needed.

Re: Scanning keymaps for keybindings

[despen]

Elena <egarrulo@gmail.com> writes:

> On Nov 9, 9:37 pm, des...@verizon.net wrote:
>> You need to issue that in each mode you want to fool with.
>>
>> I'm not sure what you mean by keymap variables.
>> Are you after all the modes you are using?
>
> Yes, I'm after *all* keymaps.  Since `describe-variable' can list all
> global variables, I think it can be done.  I know I will get some
> false-positives with a regex-based approach, but I will just discard
> variables which are not keymaps.

Keymaps are created on the fly.

Use MH-E and you get the mh-folder-map and a bunch of other maps.

If you haven't used mh-e, the map doesn't exist.

What you want would have to be done with grep and the .el files
and would still only see what you have installed.

Re: Scanning keymaps for keybindings

[Elena]

On Nov 9, 10:56 pm, Andreas Politz <poli...@fh-trier.de> wrote:
> Are you looking for `mapatoms' ?

Yes, thanks.

Re: Scanning keymaps for keybindings

[Elena]

On Nov 9, 10:47 pm, Tim X <t...@nospam.dev.null> wrote:
> Depending on what you want to do, you may be able to use something like
> after-change-major-mode hook or similar to update things after a new
> mode is used. However, this assumes all modes have been written
> following standard conventions, which cannot be guaranteed.

The goal I'd like to accomplish is remapping a keybinding without
having to dig through the documentation and Elisp files.  Yes, I know
you can type "C-h c" to know what the name of the command which is
bound to a specific key, then you can grep such name to know which
keymap you'd have to change; but since I'm a keyboard layout
thinkerer, I'd prefer to automate that.

Re: Scanning keymaps for keybindings

[Elena]

On 9 Nov, 23:46, p...@informatimago.com (Pascal J. Bourguignon) wrote:
> It means that there may exist a lot of keymaps that are not bound to any
> variable, but that will nontheless be activated upon a mode change (and
> then accessible via the current-active-maps function).
>
> More over, a mode may very well compute its keymaps dynamically, when it
> is activated or at some other time.
>
> So there is no way to get an exhaustive list of keymaps with a static
> analysis.  All you can do is to try to collect some keymap objects at
> some specific time.  And perhaps try again later.

How true!  Being stucked on keymap scanning, I thought I'd just write
a simpler function with a regex guessing based search.  The first
command I have tried is `ido-prev-work-directory', bound to "M-p".  I
thought it should have existed a keymap variable whose name would
match "ido-.*-map", but according to `describe-variable' there isn't
any.  Digging into "ido.el", showed such function was being bound by
`ido-init-completion-maps', thus requiring source modification, I
think.

Hard times in Emacs for keyboard remappers :-(

Re: Scanning keymaps for keybindings

[Elena]

On Nov 10, 6:56 pm, Stefan Monnier <monn...@iro.umontreal.ca> wrote:
> I think you're going about it in the wrong way.  If you tell us more
> precisely what you're trying to do, we can probably give you some better
> indications of how to do it.

Nevermind.  My understanding now is that the only effective way is
tracking down by hand where the key are bound and write the
appropriate fix on a case by case basis.

However, for the curious, here is the full story.  Being a Viper
+Vimpulse user, I'm used to J and K to go to next and to previous
line.  For the sake of consistency, I'd like to use M-j and M-k
instead of M-p (ido-prev-work-directory) and M-n (ido-next-work-
directory) to go back and forth in IDO's (ido.el) directory history.
Of course, since N-based and P-based bindings for next and previous
items are pervasive in Emacs (for consistency) this meant I had to do
quite a few remappings.  This raised the learning challenge to
somewhat automate the task.