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

 
 

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

Submitted by:  None
Submitted on:  Sat 07 Jun 2014 04:09:59 AM UTC  
 
Category: NonePriority: 5 - Normal
Severity: 2 - MinorStatus: None
Privacy: PublicAssigned to: None
Originator Email: -unavailable-Open/Closed: Open
Operating System: GNU/Linux

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

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 File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by dualbus (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup