On 03/22/2011 07:56 PM, Robby Workman wrote:
> On Tue, 22 Mar 2011, Robert C. Helling wrote:
>
>> Ok, I see. Now, I filed a bug report with adobe.com pointing to this page.
>> Let's see what happens.
How did you find out where to file the report, and do you have a link to
the report?
Back in October, I searched for a way to file the bug, and the closest I
could find at that time was to post on their forums which is what I did,
but haven't seen any responses:
http://forums.adobe.com/thread/745833
> I thought this was already fixed by them in their latest release.
The 9.4.2 US English *.deb and *.rpm available from their site still
(re)define the _filedir() function. As long as that happens and we use
it, pretty much all bets are off - I wouldn't spend time finding out
exactly what bits in their implementation are the ones that cause problems.
I'm tempted to add a "readonly -f _filedir" in bash_completion to make
it clearer to people that something's wrong, and to protect our
implementation from being overridden. The acroread completion shipped
by Adobe should continue to work just as it does now if it ended up
using our _filedir().
But on the other hand, we have a "namespace prefix" roadmap item for 2.0
for all functions in bash-completion which when/if implemented would
make this particular issue moot as it stands now.
http://wiki.debian.org/Teams/BashCompletion/Proposals/Roadmap
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
