.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.
.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.