Mon 16 Oct 2017 07:43:51 PM UTC, comment #2:
For the macro functions, I figured you'd say that, so attached :)
As for the rest, given the names of the keys, and your commentary (which I generally agree with), I'd do this:
1. Make "speller" official, and "tospell" the alias.
2. Make "browser" official, and "tofiles" the alias.
3. Make "pageup" official, and "prevpage" the alias.
4. Make "pagedown" official, and "nextpage" the alias.
At least then, the key names are consistently the official ones, and in the cases where the key names diverge from the tags, the tags are the unofficial ones. As long as nano continues to support both the official and unofficial bindings, nothing will change in terms of code, and the documentation will only need to be updated to reflect the new official names in these four cases.
And as for whether they need to be documented or not... as long as the tags keep the same names, fine. I still don't particularly like undocumented features, but using the tag names is intuitive enough in these cases that I can deal with it.
Is this proposal acceptable?
(file #42170)
|