Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grouping commands #221

Open
krystof-k opened this issue Jul 19, 2022 · 1 comment
Open

Grouping commands #221

krystof-k opened this issue Jul 19, 2022 · 1 comment

Comments

@krystof-k
Copy link
Contributor

krystof-k commented Jul 19, 2022

Some settings change multiple keys. For example default Finder new window setting:

  • com.apple.finder.NewWindowTarget = PfAF &
    com.apple.finder.NewWindowTargetPath = file:///System/Library/CoreServices/Finder.app/Contents/Resources/MyLibraries/myDocuments.cannedSearch
    for Recents
  • com.apple.finder.NewWindowTarget = PfHm &
    com.apple.finder.NewWindowTargetPath = file:///Users/username/
    for home (~/.)
  • com.apple.finder.NewWindowTarget = PfDe &
    com.apple.finder.NewWindowTargetPath = file:///Users/username/Desktop/
    for desktop (~/Desktop/)
  • com.apple.finder.NewWindowTarget = PfDo
    com.apple.finder.NewWindowTargetPath = file:///Users/username/Documents/
    for documents (~/Documents/)
  • com.apple.finder.NewWindowTarget = PfID
    com.apple.finder.NewWindowTargetPath = file:///Users/username/Library/Mobile%20Documents/com~apple~CloudDocs/
    for iCloud (~/Library/Mobile%20Documents/com~apple~CloudDocs/)
  • com.apple.finder.NewWindowTarget = PfVo &
    com.apple.finder.NewWindowTargetPath = file:///
    for a (root) volume
  • com.apple.finder.NewWindowTarget = PfCm
    com.apple.finder.NewWindowTargetPath deleted
    for computer
  • com.apple.finder.NewWindowTarget = PfLo
    com.apple.finder.NewWindowTargetPath = file:///custom/path
    for a custom location

I believe it would make more sense to group the commands under some higher entity which would describe the overall behavior (or setting in the UI). That would be also future-proof when the underlying commands may change in future macOS versions, but the behavior may stay the same.

@yannbertrand
Copy link
Owner

Good point (see #206). I believe the defaults.yml file has made its time, it's limitating on several points.

I will simplify the whole project by just creating a markdown file for each page, no more yml to md compiler. I'll let you updated in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants