-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Description
...in both output and commandline editor.
In fact terminal emulators handle long lines by themselves though sometimes in a different way.
I use rxvt-unicode and here are the differences I see between fish and bash.
I use 'll' command in a folder with symlinks to produce wide output.
- When using fish, resizing terminal doesn't reformat lines. Split lines remain split.
If you make terminal wider, you see a line-break. If you make the terminal window narrower, text that goes outside gets lost.
When I use bash, resizing terminal reformats the output. Which is nice.
-
There already was a discussion in the mailing list about the ellipsis which prevent long command-line from being copy-pasted.
-
Long command lines are also can not be copy-pasted because of newline character which is interpreted as 'Return' when pasting. If I copy a split long command line from bash, it is pasted as single line. When I do it in fish, fish tries to execute every part preceding the 'newline'.
As for me I prefer the bash behavior in this case in all the cases. I propose to switch to it where it is possible.