undo C-_ and C-/: mention hex codes

undo C-_ and C-/: mention hex codes

[jidanni]

In the emacs manual at the several places where it talks about the
undo keys C-_ and C-/, please also mention what hex codes you are
talking about (0x1F) etc. Maybe you are just talking about the same
0x1F and 0x1F, or maybe two different codes. The user wants to know.

Or maybe there's a extra layer of abstraction involved. Mention that
too.

Anyways, mentioning it would help the user better understand
paragraphs like:

      The reason the `undo' command has three key bindings, `C-x u', `C-_'
   and `C-/', is that it is worthy of a single-character key, but `C-x u'
   is more straightforward for beginners to remember and type.  Meanwhile,
   `C--' on a text-only terminal is really `C-_', which makes it a natural
   and easily typed binding for undoing.

Re: undo C-_ and C-/: mention hex codes

[Jason Rumney]

jidanni@jidanni.org wrote:
> In the emacs manual at the several places where it talks about the
> undo keys C-_ and C-/, please also mention what hex codes you are
> talking about (0x1F) etc. Maybe you are just talking about the same
> 0x1F and 0x1F, or maybe two different codes. The user wants to know.
>   

I've yet to meet a user who thinks about keybindings in terms of "hex 
codes", whatever that means.

If you're talking about the ASCII control codes that happen to be 
produced by some control key sequences on text terminals, then I think 
it would just confuse users, the majority of whom these days are using 
graphical terminals that deal with key events, not ASCII character 
sequences.

Re: undo C-_ and C-/: mention hex codes

[Stefan Monnier]

> In the emacs manual at the several places where it talks about the
> undo keys C-_ and C-/, please also mention what hex codes you are
> talking about (0x1F) etc.

By "hex code" you mean "ascii char code", I guess.

> Maybe you are just talking about the same 0x1F and 0x1F, or maybe two
> different codes.  The user wants to know.

Patches welcome, but note that unless you're running Emacs on a tty, C-/
and C-_ are two different keys/events.  And I wouldn't be surprised if
some terminal emulator out there also sends different byte-sequences for
those two keys.

> Or maybe there's a extra layer of abstraction involved. Mention that
> too.

I don't see why, really.  My main concern is to make sure the user can
run the command bound to those keys, and that doc should be appropriate
since the user can then try C-x u, C-_, C-/, and C--, all of which
should work, whether or not they generate the same byte-sequence.


        Stefan