Closed RogerThiede closed 9 years ago
Actually this might be my misunderstanding with OS X defaults write
, but I'd like another opinion on it.
I think this may be a quirk with the defaults
command. You can see the command cider uses if you pass in the --debug
flag:
$ cider --debug set-default -bool com.apple.desktopservices DSDontWriteNetworkStores TRUE
==> defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool True
$ defaults read com.apple.desktopservices
{
DSDontWriteNetworkStores = 1;
}
In your last example, it looks like you're setting the value to the string "true", which may or may not do what you want (Objective-C apps often implicitly convert these values to true).
That makes sense. The OS X defaults application is choosing to store bool's as 0 or 1. My example in expected behavior was a bad example because I was actually setting a string (which ends up also having the desired effect.)
Not a bug.
Thanks.
When using
cider set-default -bool
, the given domain key is properly stored intodefaults.yaml
but the given domain key is not properly applied to the system. booleantrue
andfalse
are converted intoint
.Expected behavior is: