: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: closed new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
> What steps will reproduce the problem?
Try to run ffdec.sh as-is (e.g. ./ffdec.sh)
> What is the expected output? What do you see instead?
Expect: decompiler window to open
Happens: Permission denied (because it's not executable)
<After setting executable bit...>
Happens: /bin/sh^M: bad interpreter
<After running dos2unix...>
Works as expected.
> What version of the product are you using? On what operating system?
2.1.2 on Linux (Ubuntu 14.04)
The line endings are fine now. And yes, it is possible to mark a file as executable in a
zip, but I don't know if Windows software knows how to do that.
Also, if it's not too much trouble, it would be great if the contents of the ZIP were
wrapped in their own directory so they don't get lost and mixed in with nearby files.
Please try the latest nightly again. Now the filemode of ffdec.sh should e 755. I can't
see any diffrences on windows, but maybe you can.
About putting everything to a folder in the zip:
I do not prefer this structure, but if JPEXS likes it, then we will do it.