You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first glob element represents the "main" extension for the file type. While this doesn’t affect the
mimetype matching algorithm, this information can be useful when a single main extension is needed
for a mimetype, for instance so that applications can choose an appropriate extension when saving a
file.
This is useful information. In particular, it would be good if the extensions() function returned the glob elements in the order defined in each file. The trouble is that the order is randomized in the globs file, if the weights are equal, so for example on my system the extension returned by extensions() in scalar context for applicaton/javascript is .jsm, and not the more obvious .js, which is the first in the XML file, and hence the main extension according to the spec.
The text was updated successfully, but these errors were encountered:
The Shared MIME-info Database spec says:
This is useful information. In particular, it would be good if the
extensions()
function returned the glob elements in the order defined in each file. The trouble is that the order is randomized in theglobs
file, if the weights are equal, so for example on my system the extension returned byextensions()
in scalar context forapplicaton/javascript
is.jsm
, and not the more obvious.js
, which is the first in the XML file, and hence the main extension according to the spec.The text was updated successfully, but these errors were encountered: