macmarrum

We've moved from SourceForge to GitHub. Please post your question in https://github.com/freeplane/freeplane/discussions

Hello @Orama We've moved from SorceForge to GitHub. Please have a look at the related topic: https://github.com/freeplane/freeplane/discussions/493 and if you need further assistance, ask your question on GitHub. Regards Mac

We have moved. Please ask your question in https://github.com/freeplane/freeplane/discussions Also, if you can attach a sample mindmap (after ZIPing it), it would help people understand your issue better.

Correction: installing the mime-info globally did the trick on my system: Freeplane's .mm files are recognized correctly, alongside .mm files of Objective C++. Since the mime-info part is done, we need to take care of the document-icon part: Linux packages of Freeplane should include the icon files for application/x-freeplane documents. In the .deb package, I can see that the application icon is in 2 sizes: 32x32 and scalable. It would make sense to me if the new document icon was at least for these...

@fnatter I just saw your post. Indeed, increasing the magic priority does the trick. I'm on Arch Linux and run Freeplane locally (not installed globally). It looks to me that the feature request is therefore about including the appropriate icon.

@fnatter I just saw your post. Indeed, increasing the magic priority does the trick. EDIT: it looks like I spoke too soon I'm on Arch Linux and run Freeplane locally (not installed globally). It looks to me that the feature request is therefore about including the appropriate icon.

@fnatter I just saw your post. Indeed, increasing the magic priority does the trick. I'm on Arch Linux and run Freeplane locally (not installed globally). It looks to me that the feature request is therefore about including the appropriate icon.

According to shared-mime-info-spec#Recommended checking order If a MIME type is provided explicitly (eg, by a ContentType HTTP header, a MIME email attachment, an extended attribute or some other means) then that should be used instead of guessing. If no explicit type is present, the glob rules should be applied to the name to get the type. If no glob rules match, the magic rules should be tried next. If nothing matches, the default type of application/octet-stream should be used for binary data,...