On Sun Sep 02 00:20:10 2012, shlomif wrote: > Hi all, > > On Mon Aug 06 02:29:34 2012, shlomif wrote: > > Hi all, > > > > On Fri Jul 27 14:28:55 2012, shlomif wrote: > > > On Fri Jul 27 13:07:36 2012, andreas.koenig.7os6VVqR@franz.ak.mind.de > > wrote: > > > > >>>>> On Fri, 27 Jul 2012 05:37:33 -0700, "perl@profvince.com via RT" > > > > <perlbug-followup@perl.org> said: > > > > > > > > > On 27/07/2012 14:31, Vincent Pit wrote: > > > > >> > > > > >> This should have been fixed by commit 9df8bd1d (which is in > > > > 5.17.2). > > > > > > > > > Or more likely by ea7bdd87e for this specific issue (tab > > > > completion was > > > > > broken in several places) > > > > > > > > Not here. For me, the example I posted works neither with 9df8bd1d nor > > > > ea7bdd87e nor with pretty recent bleadperl v5.17.2-81-g613c63b. > > > > > > > > > > There problem is that there is now a different error. The attached patch > > > appears to fix it. > > > > > > Regards, > > > > > > -- Shlomi Fish > > > > > > > Shouldn't this patch be applied and this bug report closed? Or are you > > waiting for something else. Ping. > > > > Please apply this patch or let me know how it should be improved. It has > been roughly a month since my last comment. Every time I have touched perl5db.pl (even applying someone else’s patch), I have caused problems. So I am hoping someone else will step up and handle this. Anyone? -- Father Chrysostomos --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=114284Thread Previous | Thread Next