Skip to content

Instantly share code, notes, and snippets.

@ResidentMario
Last active September 5, 2025 16:26
Show Gist options
  • Select an option

  • Save ResidentMario/0895eed3f82a151c7e4d98a8b85f75af to your computer and use it in GitHub Desktop.

Select an option

Save ResidentMario/0895eed3f82a151c7e4d98a8b85f75af to your computer and use it in GitHub Desktop.
Shell settings

This gist contains my development environment settings. The idea is that I should be able to reproduce my development environment from scratch.

  1. Download and install iTerm2.

  2. Download and install Oh My Zsh: http://ohmyz.sh/.

  3. Install Powerline fonts: https://github.com/powerline/fonts.

  4. In the iTerm2 settings go to Preferences > Profile > Colors > Color Presets, and select Tango Dark.

  5. Remove the machine name from the prompt by running cd ~/.oh-my-zsh/themes/; sed -i -e 's/@%m//g' agnoster.zsh-theme.

    The machine name seems to be derived from the machine name set by the kernel, but modifying this in settings did not get rid of the overlong Alex-MacBook prompt. This does.

    Note that this counts as an edit to a git-tracked repository, causing it to diverge from the cloned master. This may or may not cause problems should you ever want to upgrade oh-my-zsh. If it does, just remove the changes and rerun the command after updating.

  6. Set theme to "agnoster" in the Oh My Zsh config.

  7. Set "font" in iTerm to Hack.

  8. Set window size to 120x36 in the iTerm settings.

  9. Set my plugins in Oh My Zsh: plugins=(git pip brew docker kubectl npm python).

  10. Install htop: brew install htop.

  11. Turn off the less pager for git (go back to dumb cat output): git config --global pager.branch false.

  12. The zsh shell font will not work in VS Code fully correctly for reasons. To fix this, install the Menlo for Powerline font, and switch to that in Font Settings. Instructions for Linux here; only difference on macOS is that it's easiest to open the font (double click) and install it using the Font Book app.

  13. In VSCode settings find window.AutoDetectColorScheme and enable it. This tells VSCode to inherit the color scheme (light mode / dark mode) from the OS. Also need to do this in Slack.

  14. Install my suite of VSCode extensions: Python (publisher: Microsoft), Pylance (Microsoft), Jupyter Notebook Renderers (Microsoft), Jupyter Keymap (Microsoft), Jupyter (Microsoft), Docker (Microsoft), Back and Forward buttons (grimmer), GitLens (GitKraken), Go (Go Team at Google), Live Preview (Microsoft), markdownlint (David Anson).

  15. Install the code shortcut in terminal (instructions here).

  16. Follow the instructions here to turn on Pylint (pip install pylint first) and set it up to use the Black rule-set. See also the Black docs for some justification for these otherwise magical strings. Note that the blog post author was wrong to insert spaces around the equals (=) on the liens that have it, this breaks things—remove these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment