/kdeldycke-dotfiles

🍎 macOS dotfiles for Python developers.

Primary LanguageShellBSD 2-Clause "Simplified" LicenseBSD-2-Clause

Kevin's dotfiles

Dot-files and system configuration for Python developers on macOS with Apple Silicon hardware.

Mac OS X 10.13 High Sierra solarized terminal and vim

Features

  • Aimed at Python programmers using Neovim and VisualStudio Code.
  • Targets ZSH shell (now the default since Catalina).
  • Produce colored output for most of shell commands.
  • All color schemes are based on Monokai.
  • Terminal and coding font is Source Code Pro.
  • Keeps macOS fast, lean and secure.

Pre-installation

We will reinstall macOS from scratch.

  1. Download macOS from the App Store.app.

  2. Plug a USB drive to your machine, format it with the Disk Utility app, double-check it is mounted at /Volumes/Untitled, and finally flash it with the macOS image:

    $ sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --nointeraction
    
  3. Reboot your machine, reinstall macOS, create a user.

  4. Login to your new user, and launch System Preferences.app.

  5. Go to Security & PrivacyPrivacyClick the lock to make changes, and then unlock with touch ID or password:

  6. Go to Full Disk Access, click the + button, go to ApplicationsUtilities, and choose Terminal.app:

Install

  1. First, you need a local copy of this project.

    If you're lucky and have git already installed on your machine, do:

    $ cd ~
    $ git clone --recursive https://github.com/kdeldycke/dotfiles.git
    

    If you don't have git yet, fetch an archive of the repository:

    $ mkdir ~/dotfiles
    $ cd ~/dotfiles
    $ curl -fsSL https://github.com/kdeldycke/dotfiles/tarball/main | tar --strip-components 1 -xvzf -
    
  2. Now you can install the dotfiles on your system:

$ cd ~/dotfiles
$ /bin/zsh ./install.sh 2>&1 | tee ./install.log

Post-installation

Manual setup required to finish up the perfect configuration.

This is a list of manual post-installation steps required to fully configure the system. Haven't found any way to automate them all.

System Preferences.app

  1. In Displays, set external monitor scale:

  2. In Touch IDAdd other fingerprints.

  3. In Security & PrivacyPrivacyAccessibility, activate:

    • Amethyst.app
    • Logi Options Daemon
    • Logi Options
    • MonitorControl.app

  4. In Security & PrivacyPrivacyFull Disk Access, click the + button. Then go to ApplicationsUtilities, to add:

    • BlockBlock.app
    • KnockKnock.app
  5. In Security & PrivacyPrivacyAnalytics & Improvements: uncheck all options to disallow analytics sharing.

  6. In Security & PrivacyPrivacyApple Advertising: uncheck Personalized Ads option.

  7. In Security & PrivacyPrivacyDeveloper Tools, activate Terminal:

SSH & GPG

Copy SSH (./dotfiles/dotfiles/.ssh/) and GPG (./dotfiles/dotfiles/.gnupg/) folders from Time Machine backups.

Safari

In Preferences...Extensions, activate:

  • 1Password
  • AdGuard Assistant
  • Open in IINA

AdGuard

In Preferences...Filters, click the + button and subscribe to all filter lists:

Logi Options

For productivity, setup custom trackball shortcuts with macOS desktop management tools and Amethyst windows commands.

Page-up button assignment → Smart zoom:

Page-down button assignment → Shift + Opt + Ctrl + J:

Wheel click button assignment → Misson Control:

Wheel left click assignment → Desktop (left):

Wheel right click assignment → Desktop (right):

Side button assignment → Shift + Opt + Space:

Upgrade

I'm trying to make the install procedure indempotent so you'll just have to call the script again to upgrade your system:

$ ./install.sh 2>&1 | tee ./install.log

Maintenance

It mainly consist in refreshing some assets at every macOS major release:

Versions

Only the current default main branch is supported and actively maintained. Older branches are available for archive.

Former support of Kubuntu and Ubuntu Server Linux distributions has been dropped. You can still find these as dedicated branches, but all are quite ancient (2016).

Resources

License

For convenience, some third party code and assets are hard-copied in place. These particular items have their own license and copyright:

The rest of the content is configuration and code I accumulated over years. Some was heavily inspired by other dotfiles repositories. But each time I borrow something, I try to credit the author and/or point to the source. You should be able to trace back the origin of things by looking at the commit history.

If you can't find any clue about an external source, then assume it is original content I produced, which I released under the BSD 2-Clause License.