I have a problem with folder naming in macOS — I need to name a folder with *.Menu in the end. But if I do that Finder thinks it's some sort of a system file and not a directory. The same goes with *.framework. Is there some setting in Finder to turn off this behaviour?

  • 2
    I would advise against using extensions that are used by the system for purpose other they what they are already registered for, for the system, as this may cause unwanted problems. I'd choose a different naming convention! – user3439894 Aug 20 '17 at 15:23
  • 1
    You could use ._Menu for example. Should please both you and Mac maybe. – Natsfan Aug 20 '17 at 16:16
  • @john, nah, it doesn't look nice, but thanks for the idea :) Anyway, for now I decided to just make a whole hierarchy representing a namespace. It solves the problem, it's just I don't need a whole hierarchy for the moment. I think it's unfortunate that Apple decided to treat folders with special names as bundles. They should 've used zip archives with custom file extensions to represent .app, .framework and other system bundles. – Aleksey Usatov Aug 20 '17 at 16:56
  • Do mean * in the file name? – mmmmmm Aug 21 '18 at 17:52
  • You could try a different file system manager. – William Aug 21 '18 at 19:01

My solution is to use an underscore. I wanted to have folders like:

domainname.com domainname.cc

to store local versions of websites I deploy.

But have settled with underscore instead. That means I don't have to worry about the mac thinking these folders are actually files of some specific type. If I used .cc, there's a risk the mac would think that folder is a c++ source file :) So, I'm happy with:

domainname_com domainname_cc

such that I know I don't have to worry about that.

  • The OP already stated in the comments he does not want to use an underscore. – user3439894 Aug 21 '18 at 17:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .