Arch Linux User Repository

@JP-Ellis
The issue of virtual environments has come up only once before in the last 4-5 years (iirc) so it seems to affect very few people. I wonder if just as many would be affected by hard-coded paths. Given that I currently neither use virtual environments nor mess around with paths, I have no strong opinion on the matter. Given that the launcher scripts are just minimalist wrappers around the Python executable, I'm more inclined to just leave it as-is and let the user's who bother to set up a virtual environment set up their own aliases or wrappers as well. I'm remain open to arguments.

It would be good if /usr/bin/mimeo could be changed so that it uses an absolute path for Python (that is, replace "python3" with "/usr/bin/python3"). This ensures that the system python is always used and the mimeo module is available. This is an issue for people who use python virtual environments as the system modules are (generally) not made available in the virtual environment.

I'm experiencing a weird issue in which mimeo launches two applications when I want to open certain files.

For example,
┌─┤21:07:19│zoopp@zoopp-laptop:~
└──────────╼ mimeo --debug ~/wallhaven-317663.jpg
DEBUG: loading arguments from /home/zoopp/.config/mimeo/default_arguments.txt
DEBUG: opening /home/zoopp/.config/mimeo/associations.txt
DEBUG: ['/usr/bin/eog', '/home/zoopp/wallhaven-317663.jpg']
DEBUG: ['gimp-2.8', 'file:///home/zoopp/wallhaven-317663.jpg']

I've noticed that this happens only for files which have associations in ~/.config/mimeo/associations.txt. For reference, these are the file contents: https://paste.kde.org/po6wbvc9i.

I'm thinking of taking a look into it when I'll get some time. In the meantime, might someone have any ideas what could be wrong?

Thanks a lot for the fast fix/rewrite.

I have completely rewritten Mimeo in Python 3 while trying to adhere to the current standard on freedesktop.org.

Please use the forum thread[1] to report Mimeo errors and give feedback to keep the discussion in one place.

[1] https://bbs.archlinux.org/viewtopic.php?id=86855

@xduugu
The specification has changed a bit since Mimeo was written. Kludging in the new changes to the current messy codebase would be error-prone. I have been meaning to overhaul and rewrite it in Python 3 for years and with this I have finally started. I don't know how long it will take though, but I will post an update as soon as I have the time to finish it.

Hi Xyne,

according to [1], the default location of the mimeapps.list file is $XDG_CONFIG_HOME/mimeapps.list and $XDG_DATA_HOME/applications/mimeapps.list is deprecated and only kept for compatibility.
The specification also says that the default applications are stored in the mimeapps.list file as well. A default.list file is not mentioned in the specification.
Could you adjust mimeo to comply with the specification? Thanks a lot!

[1] http://standards.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.html

> @xduugu
> I have added a "--by-content" option to bypass the filename check. Please test > it and let me know if it works as expected.

(Copied your answer from the old AUR)

It works as expected. Thanks a lot.

Hi Xyne, thanks for mimeo. It's a great replacement for xdg-open. There is only one feature I'm missing:

Would it be possible to introduce an additional commandline option to bypass the file extension check in line 755:

mimetype = mimetypes.guess_type(rpath)[0]

and always rely on the file utility instead? Similar to mimeopen's option:

-M, --magic-only
Do not check for extensions, globs or inode type, only look at the
content of the file. This is particularly useful if for some reason
you don't trust the name or the extension a file has.

Fix typo from pazpi's comment. yes it does work.

gpg --recv-keys 1D1F0DC78F173680