평판: 685.3k
3.4k
1.1k
2.6k
Got in a 17" 2.16 MBP. stock 120 GB hard drive. The hidden files (invisible files) are all showing when I open the hard drive. Booted from a 10.6 disk, ran Disk Utilities with no hard drive problems and repaired permissions. Updated software to 10.6.3. I've forgotten how to turn the visibility of the hidden files on and off. Anyone remember how? Thanks
좋은 질문 입니까?
평판: 685.3k
3.4k
1.1k
2.6k
Close rab but no cigar. It was actually this:
defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder
해당 답변은 도움이 되었습니까?
평판: 88.9k
203
262
144
평판: 13
2
Just a clarification to what rab777hp said in the 4th (currently last) comment following his/her response above -- it wouldn't be the bash shell that interprets the "FALSE" / "NO" argument, but the 'defaults' command.
Bash doesn't interpret arguments passed to commands (although it does process them quite extensively, in the course of providing filename globbing, variable substitution, and all of the other shell features it's responsible for), once it's done its processing the resulting argument strings are simply handed off to the command being executed.
It certainly makes a lot of sense that the 'defaults' command considers "FALSE" and "NO" to be equivalent. (Probably "OFF", at least, would also be permissible.) But the responsibility for determining the meaning of those strings rests squarely upon the command's argument-processing code, and thus may vary somewhat based on how different commands are implemented.
해당 답변은 도움이 되었습니까?
thanks for the clarification +
Yeah sorry for the mixup, thanks for the clarification as well. I've never tried ON and OFF, but I've always used TRUE and YES and FALSE and NO interchangeably, as they are.
평판: 20.3k
68
33
18
$ defaults write com.apple.Finder AppleShowAllFiles NO
해당 답변은 도움이 되었습니까?
Thanks for the try anyway
Thanks for the vote- but that command actually works, I in fact just retested it now on my system after reading your comment, I'm running 10.6.3, you sure you typed it in right?
Just tested out your's as well, works fine, from what I know- FALSE and NO are the same the way TRUE and YES are as well. I believe in the bash shell it is the exact same command, and since you're just activating or deactivating (binary possibilities), leaves no room for in between, either works or doesn't work.
24 시간 전: 0
7일 전: 12
30일 전: 20
전체 시간: 1,602
