Re: nano: make configuring key bindings easier for users

> I found a lot of bindings and command names that are basically hidden in the source code and I don't think that is a good idea.
> What I did is to take out all the hard-coded key bindings and put all commands in well-organized nanorc file. That way, a user has much more overview of the available commands and better control of which key they do and don't want to have configured.
> 
> The sample.nanorc file (and some command line option) support more modern key strokes. I created two different nanorc examples, that, hopefully, best reflect the exact configuration one would have obtained if using the configuration options at the bottom of that file.

Thank you for doing this very much appreciated work! Even if Benno will find no use for it, I have saved your patch, and will keep it as documentation. This is an area where I find nano quite opaque, and a list of all possible bindings, and a function to show all current bindings would be very helpful.

Peter