[Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste

Péter Prőhle 1925823 at bugs.launchpad.net
Thu May 27 14:52:08 UTC 2021


The bug is NOT the error of the original GNU package, but of the way how
it is integrated into the Ubuntu 21.04, because if I download the GNU
package itself, compile and try, then it works fine.

In detail what I did:

mkdir -p ~/bash

cd       ~/bash

rm -fr bash-*

sudo apt-get -y install byacc

wget https://ftp.gnu.org/gnu/bash/bash-5.1.tar.gz

tar xvzf bash-*.tar.gz
rm       bash-*.tar.gz
cd       bash-*

time ( ./configure ; make )

env -i PATH="$PWD:$PATH" ./bash --noprofile --norc

and here if I do the same cut and paste tests, and drop a command with a
terminating line feed character, then this bash binary will simply
execute it ...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1925823

Title:
  Ubuntu version of BASH losts or misinterprets the newline character
  coming from mouse paste

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Quiete a few experients shows, that bash misinterprets the newline-
  character coming from mouse paste, while in the same terminals the
  emacs or vim or alpine and many other character oriented programs
  interprest correctly.

  The problem is specific to the situation when we are at a bash prompt
  of a new version of bash we got in Ubuntu 21.04. As soon as I invoke
  an ssh session, the interpretation of the newline-caharcter becomes
  correct, since the remote older bash interprets correctly.

  >>> Newline bug of first kind:

  If there is a complete bash command with terminating newline in the
  cut and paste buffer,

  and it is pasted into a gnome-terminal,

  then the command is *not* executed, the newline is ignored by the
  terminal.

  >>> Newline bug of second kind:

  If I prepare a bash command say

          cp  target-directory

  and I collect into the paste buffer "source-file newline-character"

  and I drop it IN BETWEEN the prepared "cp" and "target-directory"

  then the result is wrong:

          instead of interpreting the newline-character as "push enter"

          the command is broken into the followint 2 lines:

                  cp source-file

                  target-directory

  and I get an error message about missing target specification.

          cp: missing destination file operand after 'source-file'
          Try 'cp --help' for more information.
          bash: target-directory: Is a directory

  I found better to make this original bug descripton more informative.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions



More information about the foundations-bugs mailing list