mainThe GNU Bourne-Again SHell - Support: sr #110878, "printf '%s\n' {0..10000} | :...

 
 

sr #110878: "printf '%s\n' {0..10000} | : | less" prints "[1]+ Stopped"

Submitter:  Askar Safin <safinaskar>
Submitted:  Thu 04 May 2023 11:29:54 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  None
Open/Closed:  Open Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 09 May 2023 02:24:49 PM UTC, comment #1: 

Thanks for the report.

This was reported back in December

https://lists.gnu.org/archive/html/bug-bash/2022-12/msg00064.html

and the fix is in the bash devel branch.

https://lists.gnu.org/archive/html/bug-bash/2022-12/msg00074.html

has a basic explanation of what's happening.

Chet Ramey <chet>
Group administrator
Thu 04 May 2023 11:29:54 AM UTC, original submission:  

BEGIN OF STEPS TO REPRODUCE
Type this command:

printf '%s\n' {0..10000} | : | less

You will probably see that "less" will launch. If it will, then press "q" to quit "less". Then you will see:

[1]+  Stopped                 printf '%s\n' {0..10000} | : | less

I absolutely don't like this message. It is annoying. It requires me to run "fg"

I reproduced this is two debian versions. First is (old) debian stretch amd64 with "GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)" and less 481. The other is fresh debian sid amd64 (as on May 2023) with "GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)" and less 590. Details of reproduction in this two environments slightly differ.

Also the bigger number is in {0..10000}, the more likely is to reproduce the bug. In particular, in stretch {0..10000} always reproduce the bug, but {0..10} - does not
END OF STEPS TO REPRODUCE

DISCUSSION
I don't know whether this is bug in bash or in less. Also, let me tell how I actually found this bug. I tried to type something like this:

history | sed 's/^....//' | less

Keep in mind that I have big .bash_history (241119 lines). But "sed" command gave error. I will not get into details, let's assume that I simply mistyped "sed", i. e.:

history | sedd 's/^....//' | less

And I got that annoying "[1]+  Stopped" message. I actually often get into such situations, so this is legitimate bug

Askar Safin <safinaskar>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by chet (Posted a comment)
  • -email is unavailable- added by safinaskar (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-05-09 chet StatusNone Done

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code