bug#3516: 23.0.94; function key names in Info

[Drew Adams]

> > emacs -Q
> > C-h r
> > g keys
> >  
> > We see things like <F1>, <F2>, <RET>, and <ESC> without single
> > quotes. Similarly, in other parts of the manual.
> >  
> > Shouldn't those be `<f1>', `<f2>', `<RET>', and `<ESC>'?
> >  
> > We use `C-x <RET>' here, and we use `C-x', but not `<RET>'. 
> > Likewise, we use `<ESC>C-h' (which should be `<ESC> C-h', BTW),
> > but not `<ESC>'.
> >  
> > The notation used does not seem consistent.
> > Why write "(`C-h' or <F1>)", instead of "(`C-h' or `<F1>')"?
> 
> Please show here the Texinfo sources, not just the text from the Info
> manual.  I'm not saying that all you report is necessarily correct,
> but it could be: ESC and RET are both characters and keys.  In the
> character context, ESC and RET are correct, while in the key context,
> `<ESC>' and `<SPC>' are correct (the latter comes from @key, and I
> don't remember now whether @key produces the quotes in addition to
> <..>).

I don't have the Texinfo sources.

I'm just an Emacs user reporting what seems to be an Emacs bug - in Info. You
are the Texinfo & Info expert, and you will know better than I what is the
appropriate Texinfo coding. You decide, after looking over my bug report and the
Texinfo sources or whatever.

For my part, I was referring to (or trying to refer to) passages that talk about
keys, not characters. To me, key sequences should be wrapped in `...', even when
they have <...>. To me, the key sequence should be written `<SPC>' even if the
character is written SPC. It sounds like that is what you're saying also. It is
not, however, what I see in the manual in various places, such as the node I
mentioned.