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 also http://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
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
