Skip to content

Stop putting newline character (and ellipsis) to break long lines #300

Description

@maxfl

...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.

  1. 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.

  1. There already was a discussion in the mailing list about the ellipsis which prevent long command-line from being copy-pasted.

  2. 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions