On Thu, 20 Aug 2009, Patrick Winnertz wrote:
Would you mind to send me your .mc folder as .tar.gz in private?
I actually don't mind - but I try to do my share to track down the
problem. ;-)
Then I
can try to reproduce this with your settings. Using my settings there
is no error at all.. I can execute every executable I want.
After completely deleting my ~/.mc directory the problem vanished.
So I'll try to inject the backup I made and will seek for the config
file responsible for the problem and will keep you informed.
cat > `mktemp --tmpdir=/tmp/mc-${USER}/ mcextXXXXXX` <<EOT
#!/bin/sh
`pwd`/<file_name_to_execute>
EOT
Mh... to be honest mc only really execute it as ./$exec on the shell.
This is what I expected as well - but the string on the console
seems to support my assumption. Perhaps there is a config option
which by chance triggered the behaviour I was guessing above.
Will do so. I just wanted to do a quick check whether this is a known
issue.
No.. not really. We also tried on the upstream site to reproduce this
issue but we all (8 guys) failed to reproduce this.
I seem to have a tendency to trigger strange bugs in programms. A
friend of mine on the physics department had developed this skill to
a real masterhood - he was able to trigger a bug in nearly any
program and we used to ask him to serve as guinea pig user for
own written software ... ;-)
If you could give us some more hints how to reproduce this, this would
really help us.
After having deleted the ~/.mc directory it appeared only once and
now it vanished. Whatever it might have been - I do not really care
any more if it happens only the first time.
Well, there is no need to ask me for RTFM. ;-)
Sorry for that ;-)
No problem. ;-))
I'll come up with further information later
Andreas.
--
http://fam-tille.de
Klarmachen zum Ändern!
