I know you can set or unset the hidden flag of a folder/file by doing chflags hidden foo.txt and chflags nohidden foo.txt.

But is there anyway of telling whether the folder/file is currently hidden or not?

I don't want to just determine if the folder/file is beginning with a dot.

migrated from stackoverflow.com Aug 18 '11 at 19:09

This question came from our site for professional and enthusiast programmers.

up vote 10 down vote accepted

According to the ls man page, you should be able -O option combined with the -l option to view flags with ls. For example:

ls -Ol foo.txt
-rw-r--r-- 1 harry staff - 0 18 Aug 19:11 foo.txt
chflags hidden foo.txt
ls -Ol foo.txt
-rw-r--r-- 1 harry staff hidden 0 18 Aug 19:11 foo.txt
chflags nohidden foo.txt
ls -Ol foo.txt
-rw-r--r-- 1 harry staff - 0 18 Aug 19:11 foo.txt

Edit: Just to give a more specific solution to what the OP wanted (see comments below): To see if a folder is hidden or not, we can pass the -a option to ls to view the folder itself. We can then pipe the output into sed -n 2p (thanks Stack Overflow) to get the required line of that output. An example:

mkdir foo
chflags hidden foo
ls -aOl foo | sed -n 2p
drwxr-xr-x@ 2 harry staff hidden 68 18 Aug 19:11 .

Edit 2: For a command that should work regardless of whether it's a file or a folder, we need to do something slightly more hacky.

The needed line of output from ls -al varies depending on whether the thing is a file or folder, as folders show a total count, whereas files do not. To get around this, we can grep for the character r. This should be in ~all of all files/folders (nearly all should have at least one read permission), but not in the totals line.

As the line we want to get then becomes the first line, we can use head -n 1 to get the first line (alternative, if you prefer sed, sed -n 1p could be used).

So, for example with a directory:

mkdir foo
chflags hidden foo
ls -aOl foo | grep r | head -n 1
drwxr-xr-x@ 2 harry staff hidden 68 18 Aug 19:11 .

and with a file:

touch foo.txt
chflags hidden foo.txt
ls -aOl foo.txt | grep r | head -n 1
-rw-r--r-- 1 harry staff hidden 0 18 Aug 19:11 foo.txt

Edit 3: See Tyilo's answer below for a nicer way than grepping for r :)

  • But doing this with a folder, will list the flags for the files/folders under it – Tyilo Aug 18 '11 at 18:18
  • To just view hidden files, pipe it through grep (e.g ls -Ol fooDir/ | grep hidden) to view only hidden files/folders. This will still show all the files, but if you pipe it through some sed/awk magic (someone else will have to help here I'm afraid) you should be able to get just a list of files. – hrickards Aug 18 '11 at 18:22
  • I don't want a list of the files I just want to know is folder "foo" is hidden or not – Tyilo Aug 18 '11 at 18:27
  • Ok. So to view the directory itself add the -a option to ls. To just get the line you need from the output, you can use sed. For example: ls -aOl foo | sed -n 2p. This will display one line of output. If it contains the word "hidden", then foo is hidden. If it does not, foo is not hidden. :) – hrickards Aug 18 '11 at 18:33
  • 2
    Using ls -Old dirname/ will show you the properties of the directory itself, not its contents. – bahamat Aug 18 '11 at 23:10

Found the solution here: https://stackoverflow.com/questions/7112599/ls-get-information-of-the-directory-specified-only-not-info-about-the-sub-file/7112619#7112619

Which basically is ls -ldO foo and then you just append | awk '{ print $5 }' to make it display the information

  • Yep, or you could do that :) Much cleaner way than grepping for r – hrickards Aug 18 '11 at 19:05
  • Should I mark your or mine question as the answer? Your question wasn't what I used / the best way, but my answer is not mine. – Tyilo Aug 18 '11 at 19:06
  • I'm not entirely sure. I guess the expected way would be to mark mine as the answer, then accept the answer on your other question. I imagine anything's fine though. – hrickards Aug 18 '11 at 19:08
  • Be aware that the awk will break if there is whitespace in the username or groupname (which should be extremely unlikely, but hey). I added a safer solution that uses stat. – mrm Apr 17 at 17:29

As referenced by @Tyilo, @Sorpigal suggests trying stat, which encodes "user flags" with %Xf (heX encoded user flag), and is much safer for machine parsing.

$ stat -f "%Xf" ~/Library

The hex values for user flags live here: grep UF /usr/include/sys/stat.h. As of macOS 10.11:

#define UF_SETTABLE     0x0000ffff  /* mask of owner changeable flags */
#define UF_NODUMP       0x00000001  /* do not dump file */
#define UF_IMMUTABLE    0x00000002  /* file may not be changed */
#define UF_APPEND       0x00000004  /* writes to file may only append */
#define UF_OPAQUE       0x00000008  /* directory is opaque wrt. union */
/* #define UF_NOUNLINK  0x00000010 */   /* file may not be removed or renamed */
#define UF_COMPRESSED   0x00000020  /* file is hfs-compressed */
/* UF_TRACKED is used for dealing with document IDs.  We no longer issue
   notifications for deletes or renames for files which have UF_TRACKED set. */
#define UF_TRACKED      0x00000040
#define UF_HIDDEN       0x00008000  /* hint that this item should not be */

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.