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

Add various defaults #146

Closed
wants to merge 20 commits into from
Closed

Conversation

apexskier
Copy link
Contributor

@apexskier apexskier commented Apr 3, 2021

I just found this site/repo and it's exactly what I was looking for. I normally manually hunt for defaults or use https://www.defaults-write.com (which is not really organized in a useful manner), and this looks like exactly the setup I've wanted.

I have my own system for managing defaults across multiple computers and have a pretty extensive collection I'd like to start contributing to this repository. This PR kicks things off with a number of global apple configurations, many of which come from the system preferences.

Edit: I've now added quite a bit more, and will probably keep doing so until #150 and #151 are in.

@yannbertrand
Copy link
Owner

What do you think about a "Global" category?

@apexskier
Copy link
Contributor Author

I think global for NSGlobalDomain would make sense.

I'd personally get rid of the "custom" categories and make it all based on the domain (pull the domain key up from the keys list into the category item in the yaml file). That would enforce an organization scheme that contributors wouldn't have to make decisions about, at the expense of a little less customization. It would also get rid of the Miscellaneous section.

I think everything's currently organized by domain except com.apple.dock is split into "Dock", "Mission Control", and "Miscellaneous", there are several NSGlobalDomain items in the finder section, and "Menu Bar" would be "Menu Bar Clock".

apexskier added a commit to apexskier/macos-defaults that referenced this pull request Apr 4, 2021
This reorganizes defaults file by domain and hoists the domain up into
the category section.

I was fixing some of the descriptions to make them proper markdown, and
I discovered they actually aren't processed as markdown like I thought,
which means the meta tags and the layout on category pages broke when I
started using real markdown. I've updated the templates to fix this.

I've also tightened up the json schema a bit, which can also be
extracted from this PR.

I'm going to need to apply the markdown fixes for yannbertrand#146,
but the reorganization is a proposal for discussion.
apexskier added a commit to apexskier/macos-defaults that referenced this pull request Apr 4, 2021
This reorganizes defaults file by domain and hoists the domain up into
the category section.

I was fixing some of the descriptions to make them proper markdown, and
I discovered they actually aren't processed as markdown like I thought,
which means the meta tags and the layout on category pages broke when I
started using real markdown. I've updated the templates to fix this.

I've also tightened up the json schema a bit, which can also be
extracted from this PR.

I'm going to need to apply the markdown fixes for yannbertrand#146,
but the reorganization is a proposal for discussion.
@apexskier
Copy link
Contributor Author

apexskier commented Apr 4, 2021

Here's an example of that organization - apexskier/macos-defaults@markdown-support...apexskier:domain-organization

@apexskier apexskier changed the title Add various macOS global defaults Add various defaults Apr 5, 2021
@yannbertrand
Copy link
Owner

I prefer to keep the categories as is, which is easier to understand from a non-dev/end user perspective

apexskier added a commit to apexskier/macos-defaults that referenced this pull request Apr 5, 2021
Currently, page url generation (slugification) is just toLowerCase. In
yannbertrand#146 I add some
defaults that contain keys with spaces, which currently breaks.

This pulls in `slugify` to add support, and shell escapes keys in
examples.
yannbertrand pushed a commit that referenced this pull request Apr 6, 2021
Currently, page url generation (slugification) is just toLowerCase. In
#146 I add some
defaults that contain keys with spaces, which currently breaks.

This pulls in `slugify` to add support, and shell escapes keys in
examples.
yannbertrand pushed a commit that referenced this pull request Apr 6, 2021
Currently, page url generation (slugification) is just toLowerCase. In #146 I add some defaults that contain keys with spaces, which currently breaks.

This pulls in `slugify` to add support, and shell escapes keys in examples.
yannbertrand pushed a commit that referenced this pull request Apr 6, 2021
Currently, page url generation (slugification) is just toLowerCase. In #146 I add some defaults that contain keys with spaces, which currently breaks.

This pulls in `slugify` to add support, and shell escapes keys in examples.
@yannbertrand
Copy link
Owner

Is the PR still a Draft? Let me know if I can review it 🙂

Gudsfile pushed a commit to Gudsfile/macos-defaults that referenced this pull request Oct 16, 2022
Currently, page url generation (slugification) is just toLowerCase. In yannbertrand#146 I add some defaults that contain keys with spaces, which currently breaks.

This pulls in `slugify` to add support, and shell escapes keys in examples.
@apexskier apexskier closed this Oct 29, 2024
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

Successfully merging this pull request may close these issues.

2 participants