On Sun, Dec 27, 2009 at 1:10 PM, Sven Joachim <svenj...@gmx.de> wrote: > On 2009-12-27 17:49 +0100, John Martin wrote: > >> On Sun, Dec 27, 2009 at 11:27 AM, Sven Joachim <svenj...@gmx.de> wrote: >>> >>> What does "readlink -f $(/usr/bin/which gzip)" print? >> >> ,----[ sudo readlink -f $(/usr/bin/which gzip) ] >> /bin/gzip >> `---- > > And what does Emacs print when you evaluate > > (executable-find "gzip") <--- press C-x C-e here
"/bin/gzip" Previously you asked: > So busybox is not installed as /bin/gzip, but somewhere else on your > PATH. Indeed. Not only in /bin/busybox but also ~/bin/busybox with, I think, the default PATH. ,----[ printenv PATH ] /home/jam/bin:/usr/local/bin:/usr/bin:/bin:/usr/games `---- When I move busybox out of ~/bin all seems to be well. I dunno how busybox got to ~/bin but it was unintended. I do not however understand why emacs should have tried to use busybox instead of /bin/gzip? Is this to be expected? Having cleared the problem by moving the offending file away I cannot seem to reproduce the problem by moving the file back to ~/bin. If the result of the extraneous `bin/budybox is to be expected then it would seem that this bug is ready to be closed, no? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
