[Bash-completion-devel] Using \t in IFS

[Freddy Vulto]

Ville Skyttä <ville.skytta <at> iki.fi> writes:
> Is there a particular reason that a lot of cases where IFS is set in bash 
> completion (for proper handling of spaces), it is set to something that 
> includes \t, for example IFS=$'\t\n'?  Why not usually set it to $'\n' instead 
> (only in cases where we don't want/need to split by tabs but only by newlines, 
> which I believe equals vast majority of cases)?

+1

Leaving just the \n in a filename to be unsupported, seems to be the
best we can do.  See also this recent discussion on bug-bash:

http://www.mail-archive.com/bug-bash@gnu.org/msg07977.html