I hadn’t noticed since most of my files have extensions anyway, but indeed, I just tested a markdown file by removing the extension. It changed the association from Atom to TextEdit, but couldn’t open it. (Something about UTF-8 not being applicable. ?? Really ?? Opening with Atom worked fine though.)
Preview doesn’t work either as noted. Thanks for the info. Regards, Adrien > On Mar 29, 2020 w14d89, at 10:17 PM, John Ralls <jra...@ceridwen.us> wrote: > > > >> On Mar 29, 2020, at 4:52 PM, Adrien Monteleone >> <adrien.montele...@lusfiber.net> wrote: >> >> Linux and Mac don’t generally care if a file has an extension. They >> determine the file type independent of it. > > That's sadly no longer true of MacOS and hasn't been since IIRC 10.7. The > pre-NeXTStep MacOS used a extended attribute to determine file type and the > early versions of Mac OS X continued the practice. Support for that was > deprecated in 10.6 and while not formally removed it seemed to stop working > in 10.7. There is limited support for determining file type from the command > line by looking at the file header, but Finder can't do that. File type > displayed in Finder, application associations, and QuickLook display of > files is all driven by the extension. > > Regards, > John Ralls > > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
