![]() Java under OS X doesn't integrate properly with Spaces. muCommander doesn't work properly with Spaces, why?Īs much as we respect Apple, this is actually their fault. ![]() If you can't, however, you only need run chmod +x on the file for it to become executable again. If you can upgrade to Java 1.6, we advise you to do so. Extracting executable files from archives (or copying them, for that matter) will drop the executable flag, preventing you from executing it. Until version 1.6, Java did not know how to set file permissions on local files. The short answer is, because you're not running Java 1.6 or higher. Why can't I execute applications extracted by muCommander? Why aren't file permissions properly preserved? You need to open them "natively" (mapped to Shift Enter by default). app files are in fact directories, and muCommander will browse them rather than start the application. This question is closely linked to the previous one: OS X. In order to start Open Office, you need to open "natively" (mapped to Shift Enter by default) the document. ODF files are actually ZIP files, and muCommander recognises them as such: when you try to open one, muCommander will show you the contents of the archive rather than start Open Office. When you double-click or press Enter on an OpenOffice? document, the document's internals are revealed, which may seem a bit awkward. This is an often requested feature, one that we're thinking about and have a few ideas on how to implement, but it's not there yet. If you know better and can point us in the right direction with code samples or documentation links, we'd be happy to hear about it. As far as we know, Java doesn't allow us to use system dependent things like that. Simply put, because we haven't found how. Why doesn't muCommander use the system right-click menu? Please read this article for more information. menu grayed out?īecause you haven't defined any commands for it to use. ![]() You're running muCommander on a known system but with a configuration that we haven't encountered before. Your commands or associations? file is corrupt. See this page? for information on how you can have your system supported. You're running muCommander on a system that isn't officially supported. There could be many reasons for this, but the most common ones are: This is done by editing your commands.xml file and creating the view and edit commands.įor an in-depth explanation, read the documentation. How can I replace the default editor / viewer?
0 Comments
Leave a Reply. |