Hi Ralph. Ralph Corderoy <[email protected]> wrote: |Martin wrote: |> What I (and a colleague of mine) never understood: what's the point |> of the s-nail line-editor? | |Being new to the list, I've been wondering that too. ~e and ~v are |available. ~h lets one cursor through the field. And if it is wanted, |aren't there's BSD-compatible libraries that provide GNU readline-like |behaviour?
Oh, editline(3) support has been dropped. And if i can afford a good `bind' mechanism next, plus ^V, then fixup getprompt() thereafter, then it is likely that it will never come back! Yes, there is no reason for doing so? No, i think none. To be honest, i even already had the thought of dropping readline(3) support. Not in v15, because of our brute-force tabulator expansion, but later on. E.g., the codebase has to shrink again, and i think i have offered readline(3) support because it was easy to implement and because it offers a good user experience, and of course because users (including myself) are used to it. But the MLE is small, fast, uses only basic standards and is builtin. With some more effort i think it offers more than enough for «mailx». I think when it is possible to say "~@<RET>/usr/<TAB>" and get an easy browsable selection instead of a brute-force expansion then it is time to drop readline support. The MLE usage shortcuts are pretty standard and with `bind' and very small effort users will be able to improve their experience. I think that most people which really adjust their .inputrc for individual programs have to look into the manual to write the entries, so, then it is a matter of which manual they read. Ciao. --steffen ------------------------------------------------------------------------------ __________________________________ [email protected]
