cc @svanderburg

(put the newline according to git)

-1, though it's a purely personal preference so I won't insist if this is widely supported.

EDIT: there is a reason to have it, which is that commands that don't terminate their output with a newline don't mess up the prompt.

there is a reason to have it, which is that commands that don't terminate their output with a newline don't mess up the prompt.

While messing up all other commands.

The thing is that this is non standard. NixOS (from what I know) is the only distro that does this. Also I'm pretty sure that in Ubuntu, commands that finish without newlines aren't messed up, how do they do it?

EDIT: Ubuntu doesn't fix it (and no one has ever complained about it)

While messing up all other commands.

The thing is that this is non standard. NixOS (from what I know) is the only distro that does this. Also I'm pretty sure that in Ubuntu, commands that finish without newlines aren't messed up, how do they do it?

zsh fixes that on its own, maybe bash also have an option for that?

While messing up all other commands.

It doesn't mess anything up at all, just looks different.

there is a reason to have it, which is that commands that don't terminate their output with a newline don't mess up the prompt.

It doesn't mess anything up at all, just looks different.

Applies to both

A non-newline-terminated command does mess up the prompt if the prompt doesn't start with a newline. To see what I mean, try printf " %.0s" $(seq $((COLUMNS - 5 ))), and compare behaviour afterwards with a newline in the prompt and without.

A non-newline-terminated command does mess up the prompt if the prompt doesn't start with a newline. To see what I mean, try printf " %.0s" $(seq $((COLUMNS - 5 ))), and compare behaviour afterwards with a newline in the prompt and without.

I think i would be nice to do it similarly to Ubuntu (if they actually have a way and I'm not just making things up) but the same applies:

It doesn't mess anything up at all, just looks different.

This is just a choice but I believe it is better to do what is "expected".

Maybe you could mention it on Discourse and ask for people's opinions.
I don't really care either way, since I use fish and it does this:

$ echo "Foo"
Foo
$ echo -n "foo"
foo⏎                                                                                                                                                                                                                                           $

However when I use bash on other distros I'm sometimes confused where my PS1 indicator has gone when it's just at the end of a long line without \n.
So I concur with @lheckemann that I don't want my prompt messed up.

As you mentioned it has been like this for >10 years so I wouldn't change it willy nilly.

Indeed it has been this way since the start and I don't see a strong reason to change it. I prefer it this way since I think it makes bash a bit more readable by clearly separating command invocations. Obviously not everybody will agree but that's true for any default.