Re: no-empty-command-line-completion -- thought fixed in 4.2? when?

[Chet Ramey]

On 4/27/12 10:24 PM, Linda Walsh wrote:
> I thought this was fixed in 4.2, yet I'm still seeing it...
> 
> when's this going to be fixed?

There are a couple of things wrong with your question.  First, the name of
the shopt option is no_empty_cmd_completion.  Second, you haven't
demonstrated a failure mode.  When I enable that option and hit TAB at an
empty PS1 prompt I don't get command completion; it just beeps.

> It's driving me crazy, as bash drops input because it asks questions about
> displaying 1000's of completions...).
> 
> 
> 
> when I paste a few lines of source in at the shell -- doesn't
> matter if it is bash script or perl or written text...
> 
> I can't rely on bash not corrupting the text.
> 
> Even between single quotes:
> 
> a='
> <tab>blah
> '
> will generate autocomplete.

Of course.  It performs filename completion.  That's not a position where
bash is ready to read a command, so the option setting is not relevant.

> So why isn't this fixed?

You haven't actually described a reproducible problem.  Maybe you should
turn off line editing before pasting input.  Clearly you don't need editing
in that case, and bash/readline can't tell the difference between pasted
and keyboard input.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/