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

Péter Prőhle 1925823 at bugs.launchpad.net
Tue May 11 12:34:45 UTC 2021


Sorry that I edited the original bug report, but I think it was better
to make it more informative, and not to grab these improvements of the
bug description among the comments.  Read please, re-read please the new
version of the bug report.

** Description changed:

+ 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.
  
- But in return this bug, the pasted command is showed in reverse
- coloring,
+ >>> Newline bug of second kind:
  
- what is very disturbing when a command is not executed, but decorated in
- a funny way instead.
+ If I prepare a bash command say
  
- This is new in 21.04, the dropping commands into a gnome-terminal worked
- fine in 20.10, ...
+         cp  target-directory
  
- ... and in the last 27 years of my linux usage.
+ 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.

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