.desktop files are essentially used similar to Windows’ registry - you create such a metadata file in a specific location, and it acts as a launcher, autostart setup, and file type assignment (so you can easily assign e.g. PNG files to open with Krita by default).
As the wiki says, you can put multiple MIME types (file type descriptor such as “text/plain” or “application/json” or “image/jpeg” and so on) onto one dotdesktop file, meaning you only need a single launcher to support all file types.
Krita explicitly creates quite a few dotdesktop files, each supporting only a single MIME type.
Downside: littered desktop.
Upside: you can easily pick and choose which file types to open with Krita directly.
Most desktop environments actually handle the [samename]. extension.desktop repetition so you’ll only have one Krita launcher entry but it will still collate all MIME type support that is present. Want to exclude e.g. BMP files? Delete the .bmp.desktop file.
XDG Desktop files are a mostly standardized way to integrate individual programs into the desktop. For example, a desktop file in /usr/share/applications or ~/.local/share/applications can add programs to the application launcher, both desktop launcher menus and separate apps like dmenu-run; or they can be used to start applications when the desktop session starts by placing them in ~/.config/autostart.
Desktop files can also set properties related to an application. In this particular case, the MimeType field tells the desktop session what MIME types should be associated with the application. For example, my desktop file for Blender associates the application/x-blender MIME type with it, which causes Blender to show up in the Open with… dialog.
The MimeType field is a semicolon-separated list. One desktop file can define multiple associated MIME types for the same application. Krita instead creates a separate file for each association.
Anyone with any light to shed?
.desktop files are essentially used similar to Windows’ registry - you create such a metadata file in a specific location, and it acts as a launcher, autostart setup, and file type assignment (so you can easily assign e.g. PNG files to open with Krita by default).
As the wiki says, you can put multiple MIME types (file type descriptor such as “text/plain” or “application/json” or “image/jpeg” and so on) onto one dotdesktop file, meaning you only need a single launcher to support all file types.
Krita explicitly creates quite a few dotdesktop files, each supporting only a single MIME type.
Downside: littered desktop.
Upside: you can easily pick and choose which file types to open with Krita directly.
Most desktop environments actually handle the
[samename]. extension.desktoprepetition so you’ll only have one Krita launcher entry but it will still collate all MIME type support that is present. Want to exclude e.g. BMP files? Delete the.bmp.desktopfile.XDG Desktop files are a mostly standardized way to integrate individual programs into the desktop. For example, a desktop file in
/usr/share/applicationsor~/.local/share/applicationscan add programs to the application launcher, both desktop launcher menus and separate apps likedmenu-run; or they can be used to start applications when the desktop session starts by placing them in~/.config/autostart.Desktop files can also set properties related to an application. In this particular case, the
MimeTypefield tells the desktop session what MIME types should be associated with the application. For example, my desktop file for Blender associates theapplication/x-blenderMIME type with it, which causes Blender to show up in the Open with… dialog.The
MimeTypefield is a semicolon-separated list. One desktop file can define multiple associated MIME types for the same application. Krita instead creates a separate file for each association.