The GNU Bourne-Again SHell - Patches: patch #9920, Fix bug when newline in a file,...
You are not allowed to post comments on this tracker with your current authentication level.
patch #9920: Fix bug when newline in a file, tab+tab
Submitter: | Mikhail Pavlovich Sidorenko <sgmuwa> | ||
Submitted: | Mon 13 Apr 2020 09:52:00 PM UTC | ||
Category: | None | Priority: | 3 - Low |
Status: | Invalid | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Tue 14 Apr 2020 01:50:19 AM UTC, comment #1: |
Chet Ramey <chet> |
Mon 13 Apr 2020 09:52:00 PM UTC, original submission:
Bash incorrectly suggests file names if there is a new line in the file name.
Then write «rm "11» and press [TAB] twice. Bash will not write the file name "111
|
Mikhail Pavlovich Sidorenko <sgmuwa> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-04-14 | chet | Status | None | Invalid | |
2020-04-13 | sgmuwa | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-758e.
Corresponding source code
I suspect this is an issue with the bash-completion package. Bash as distributed doesn't have any problems completing filenames containing newlines.