Re: Command substitution (backtick) and tab completion

[chengiz]

On Jan 1, 11:20 pm, Chet Ramey <chet.ra...@case.edu> wrote:
> On 12/31/10 11:01 PM, Sven Mascheck wrote:
>
> > On Fri, Dec 31, 2010 at 12:20:38PM -0800, chengiz wrote:
> >> On Dec 31, 12:20 pm, Sven Mascheck <masch...@in-ulm.de> wrote:
>
> >>> (see alsohttp://lists.gnu.org/archive/html/bug-bash/2008-01/msg00049.html)
> >>> [...]
>
> >> I dont see how that's related - I dont doubt you that the fix to this
> >> issue "broke" my example, but in that case there's premature
> >> execution, in my case the ticks are closed. [...]
>
> > Here's how I understood it:
> > The original problem was just the trigger. The decision was to completely
> > disable command substitution while the completion system is active here.
> > That's why I posted the bug report link: just see the reply from Chet.
>
> The idea is that it's not safe, in general, to run arbitrary command
> substitutions more than once.  They may have side effects.
>
> Chet

So if I get this right, the only time this is a problem is when the
command substitution runs more than once. When does this happen? Not
in my "ls `pwd`/<tab>" example where the command runs once and
replaces itself with its output. Does it only run more than once when
the ticks are not complete? In that case I reiterate that I dont see
how the fix is related to the reported bug.