mathiasbynens / mathiasbynens/dotfiles

Issues setting global preferences in Yosemite?

Open
#444 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
31.5k
Forks
8.4k
PR merge metrics
No merged PRs in 30d

Description

I’m starting to notice some inconsistencies in preferences that appear attached to the global domain/preferences.

The main case that caught my attention was that although the “tap-to-click” method runs (and the clean up kills cfprefsd, Finder, and SystemUIServer), the change does not take _however_ if I open the mouse section of System Preferences, I do see that this checkbox is, in-fact, selected:

```
defaults write com.apple.driver.AppleBluetoothMultitouch.trackpad Clicking -bool true
defaults -currentHost write NSGlobalDomain com.apple.mouse.tapBehavior -int 1
defaults write NSGlobalDomain com.apple.mouse.tapBehavior -int 1
```

Restarting seems to resolve, though I’d be curious to know if this is user error or something that others have noticed as a change starting with Yosemite?

I’ve also noticed that a few other global preferences tend not to work anymore:

```
# Does not select the preference; restarting machine has no effect
sudo defaults write /Library/Preferences/.GlobalPreferences AppleInterfaceTheme Dark
```

```
# Admittedly this varies slightly from what is currently in this repo
# Restarting machine resolves
defaults write -g com.apple.swipescrolldirection -bool false
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is identified. Start by reproducing the three defaults command cases from the issue on Yosemite, then inspect the repository’s macOS defaults entry point and related discussion. Done means determining whether the behavior is expected or a regression and defining a concrete repository change or documentation update.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, shell
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.