Sat 17 Dec 2016 03:58:38 PM UTC, comment #1:
Comparison with other editors.
Running 'pico abc*def' opens the file without problem, and show the name in the titlebar as "abc^Jdef", which is better than nano, but it adds a stray $ at the tail of the bar, as if it thinks that the contained text is longer than the bar. Opening the file browser witj ^R ^T show the name "abc.def" spread over two lines, which is /worse/ than nano. But still, selecting the file opens it fine, which is what nano can't do at the moment.
Runing 'vim abcdef' shows the name of the file as "abc^@def" in the statusbar, which seems good. But running 'vim .', it shows the file as two lines in in the browser: "abc" and "def" -- trying to select either, it opens a new file instead of opening the existing abcdef.
Running 'emacs -nw abc*def' opens the file fine, and shows the name as "abc^Jdef" on the statusbar. Running 'emacs -nw .' lists the name of the file spread over two lines -- trying to select it selects in fact "abc" and says that the file no longer exists.
So... I think nano should show the filename as "abc^Jdef", since the name contains a ^J, not a ^@. And if the file browser will be able to select the file (like pico is), we will have gained something over the other two. :)
|