Re: [Nano-devel] RFC: entering characters by code -- what with 0x0A?

[David Ramsey]

Benno Schulenberg:
> What I instead propose is that M-V 0 0 0 0 0 A will beep when the user
> tries that in an edit buffer or at a search prompt, and will enter a
> literal ^J when at a filename prompt.  And the sequence M-V 0 0 0 0 0
> 0 will beep at a filename prompt (because a filename cannot contain
> byte 0x00) and will enter a literal ^@ when in an edit buffer or at a
> search prompt.

Sounds good to me: the beep indicates that there's a problem instead of
blocking characters silently, which could be confusing for users who
don't know these character issues.

> Oh, I forgot: for comparison, typing at a prompt the sequence M-V 0 0
> 0 0 0 9 will enter an actual Tab into the string, but typing the Tab
> key will try to do filename completion or search term completion,
> depending on at what prompt you are.  So... having an M-V sequence
> always enter a character (when possible) and never execute a function
> makes things more consistent.

Exactly.  Consistency is important.  Although, using that example, M-V
Tab does always enter an actual Tab into the string, so that fits with
your plan already.