mainThe GNU Bourne-Again SHell - Support: sr #108596, Bash completion fails for files...

 
 

sr #108596: Bash completion fails for files with names containing newlines

Submitter:  None
Submitted:  Sat 07 Jun 2014 04:09:59 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  2 - Minor Status:  Invalid
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 25 Mar 2015 10:49:08 AM UTC, comment #1: 

Not a bash bug.

This is a bug in the bash-completion package, which is independently developed. Please report this to them.

Eduardo Bustamante <dualbus>
Sat 07 Jun 2014 04:09:59 AM UTC, original submission:  

Bash tab-completion fails for file names containing new lines. It provides multiple selections which correspond to the separate lines contained in the file name:

example:

$ python -c "open('foo\nbar','w')"
$ ls
foo?bar
$ ls ./f
bar  foo 

Anonymous

 

(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 (Updated the item)
  • -email is unavailable- added by dualbus (Posted a comment)
  •  

    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
    2015-11-13 chet StatusNone Invalid

    Back to the top

    Powered by Savane 3.12.
    Corresponding source code