Parent of a derived mode's keymap.

Parent of a derived mode's keymap.

[Lute Kamstra]

Currently, the parent of a derived mode's keymap is set by the mode
function.  This means that if the docstring of a derived mode shows
the keybindings of its keymap, the bindings of the parent keymap are
not shown until the mode function is first called.  Why not set the
parent keymap at top-level, right after the defvar of the keymap
variable?

Lute.

Re: Parent of a derived mode's keymap.

[Stefan Monnier]

> Currently, the parent of a derived mode's keymap is set by the mode
> function.  This means that if the docstring of a derived mode shows
> the keybindings of its keymap, the bindings of the parent keymap are
> not shown until the mode function is first called.  Why not set the
> parent keymap at top-level, right after the defvar of the keymap
> variable?

- it may not yet be loaded (that's a pretty common occurrence).
- the parent mode may not use the standard <foo>-mode-map name for
  its keymap.
- IIRC there was one more reason, but I can't think of it right now.


        Stefan

Re: Parent of a derived mode's keymap.

[Lute Kamstra]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Currently, the parent of a derived mode's keymap is set by the mode
>> function.  This means that if the docstring of a derived mode shows
>> the keybindings of its keymap, the bindings of the parent keymap are
>> not shown until the mode function is first called.  Why not set the
>> parent keymap at top-level, right after the defvar of the keymap
>> variable?
>
> - it may not yet be loaded (that's a pretty common occurrence).

Ah, yes.  Should have thought of that.

> - the parent mode may not use the standard <foo>-mode-map name for
>   its keymap.
> - IIRC there was one more reason, but I can't think of it right now.

Thanks,

  Lute.

Re: Parent of a derived mode's keymap.

[Richard Stallman]

    - it may not yet be loaded (that's a pretty common occurrence).
    - the parent mode may not use the standard <foo>-mode-map name for
      its keymap.

Could you please add this info in comments at the right place?

Re: Parent of a derived mode's keymap.

[Stefan Monnier]

>     - it may not yet be loaded (that's a pretty common occurrence).
>     - the parent mode may not use the standard <foo>-mode-map name for
>       its keymap.

> Could you please add this info in comments at the right place?

Done,


        Stefan

Re: Parent of a derived mode's keymap.

[David Kastrup]

I can't decide whether the title of this thread is more fitting for a
blues song or a pulp fiction booklet.  It certainly projects drama.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Parent of a derived mode's keymap.

[Lute Kamstra]

David Kastrup <dak@gnu.org> writes:

> I can't decide whether the title of this thread is more fitting for a
> blues song or a pulp fiction booklet.  It certainly projects drama.

Hey, it says derived, not deprived.

Lute.

Re: Parent of a derived mode's keymap.

[David Kastrup]

Lute Kamstra <Lute.Kamstra.lists@xs4all.nl> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> I can't decide whether the title of this thread is more fitting for a
>> blues song or a pulp fiction booklet.  It certainly projects drama.
>
> Hey, it says derived, not deprived.

Actually, for some keymaps "depraved" would fit better.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Parent of a derived mode's keymap.

[Lute Kamstra]

David Kastrup <dak@gnu.org> writes:

>>> I can't decide whether the title of this thread is more fitting for a
>>> blues song or a pulp fiction booklet.  It certainly projects drama.
>>
>> Hey, it says derived, not deprived.
>
> Actually, for some keymaps "depraved" would fit better.

I knew it!  You're one of them vi lovers!  There is nothing wrong with
Emacs using escape, meta, alt, control, and shift!

Lute.