Thorsten Glaser <[email protected]> wrote: |> - no tab completion over / boundary in upward direction | |Eh, *what*?
E.g., ?0[steffen@sherwood mksh.cvs_git]$ cd ..<Tab> Doesn't do anything, only ?0[steffen@sherwood mksh.cvs_git]$ cd ../<Tab> will expand the CDUP listing; whereas ?0[steffen@sherwood code.extern]$ cd mks<Tab> expands to the desired one. |> - no tab completion in the middle of a word (for partial word before \ | cursor) | |That’s by design. If you’re in the middle of a word, it’ll still |complete the whole word. I find it appalling that e.g. GNU bash |doesn’t work that way. You get the partial behaviour by inserting |a space (temporarily). I must admist that i really hate this behaviour, i always get stuck; personal preference of course.. |> - jobs names hard cut to ridiculous size (should at least be START..END, \ | not |> STARTUNTILCUT, for, e.g., playing music or having multiple jobs which \ | read |> RFCs) | |It’s pretty hard to do this well. Additionally, there are some |memory constraints *and* terminal sizes come into play… but your |improvement idea is noted and gives me some ideas; I know where |and what to change, for this. | |> - when traversing history, the terminal width should be fully used; \ | i.e., if |> a line has 88 characters only 8 characters are shown, which often \ | results in |> the need to jump to the front to see the exact command... | |Yeah, the positioning algorithm is nōntrivial and sometimes |pretty annoying. That’s in the Emacs part in edit.c FWIW. |No good ideas about that one. And well, all that is on my todo list for some time now, maybe i can write some patches soon. Thanks again for mksh(1)! --steffen
