-
- 2.1. What it looks like
- 2.2. Configuring Git
- 2.3. Setting up the GPG key
-
- 3.1. VS Code
- 3.2. Other configs
-
- 6.1. Git
- 6.2. Fish shell
- 6.2.1. Dependencies
- 6.3. Starship
- 6.4. Base16-shell
- 6.5. Tmux
- 6.6. Neovim with vim-go
- 6.7. Others
This is the home for my environment configurations, scripts, and exported tool settings. Some configurations are MacOS specific. For instructions on how to install and use any of these configurations, please see the installing packages section.
In this README I'll highlight some interesting configuration options.
My terminal configurations allow for consistency of look and feel and of functionalities across all terminals on a MacOS, either iTerm, Terminal, or VS Code's terminal. Same whether running on tmux or on a straight fish shell.
Note at the bottom the different windows in this workspace. This is likely to change as I work with different types of projects, but this setup flexibility with tmux allows for me to work with only one terminal window most of the time. This is a setup that I run on my terminal but not on VS Code.
No more fussing and googling around for different themes or plugins. The packages below come with easy ways to configure appearance settings. This is extra great when wanting to switch from daily work with all the information on the shell and maybe a dark mode, into a minimalist looking, light background shell for a demo/presentation.
- starship: many options of shell prompt styles (any shell)
- base16-shell: many options to quickly change the shell default colors (any shell)
- tmux
- tmux themepack plugin: various tmux themes and statusbar styles
Changes to the configuration of any of these packages will apply to all terminal applications (some after restart.) See the installing packages section for instructions.
This configuration allows the signing of commits automatically with a GPG key. Signed commits are labeled Verified if the identity of the committer can be verified.
Note: for projects that require committers to adhere to the requirements of the Developer Certificate of Origin (DDO), adding the -s flag to commits to add a valid Signed-off-by line is a separate requirement.
When you look at the commit log with the --show-signature flag, the full (public) signature information is shown:
git log --show-signature
- The git configuration must be installed; see the instructions in the Installing packages with stow#Git section
- The values in the .gitconfig file need to be changed appropriately
- A GPG key needs to be configured/generated and uploaded to GitHub.
In the past I've tried setting up my GPG key and had to go over multiple documents. This SO answer on generating and signing a new key, and exporting it to GitHub, includes all the step needed for that: macos - git - gpg onto mac osx: error: gpg failed to sign the data - Stack Overflow.
It also mentions a (free) Mac app for managing and signing keys: GPG Keychain Mac. This could be a nice complementary tool to the command line.
My VS Code settings in a gist file on GitHub. My VS Code is specifically configured to use:
- Go and the
goplslanguage server - bash, fish, and tmux, defaults to tmux. You may change the default in the setting
"terminal.integrated.defaultProfile.osx": "tmux",.
iTerm and other configs and scripts are in the other-configs directory.
Note: the configs for iTerm are almost irrelevant since all terminal configurations are driven by the packages in this repo. I only have a few window settings that I'd wish to recover if needed.
When you use any editor for Go code that is configured to use the gopls language server you cannot open multiple modules at the same time in your editor without a world of hurt!
This would apply to both vim-go and VS Code. See the official instructions for how to properly setup your workspace.
I use stow for managing all the configurations I care to keep recoverable and/or well organized. Stow permits both since I can keep all config files in this dotfiles directory, and stow will create the appropriate symlinks to them according to how the directory structure is created.
-
Good start page in the manual: Invoking Stow
-
This is a good and short article about how stow works: Brandon Invergo - Using GNU Stow to manage your dotfiles
Some terminology:
Stow directory: the directory that contains the packages. In this case, this dotfiles directory.
Stow target directory: needs to be set with the --target flag, usually $HOME. Otherwise, it will default to the parent directory of the stow directory.
When a package is stowed, it creates a symlink from $HOME/.somedotconfig/package-X-config-dir to the <your-path>/dotfiles/package-X-dir/.somedotconfig/package-X-config-dir.
This is what the installed fish package looks like:
$ ls -l $HOME/.config/fish
lrwxr-xr-x 1 carlisiac staff 61 Jun 22 08:25 /Users/carlisiac/.config/fish -> ../working/src/github.com/carlisia/dotfiles/fish/.config/fishWhatever you have under the directory <your-path>/dotfiles/package-X-dir/.somedotconfig/ is going to be installed under $HOME/.somedotconfig/. And: .somedotconfig can be directories or files.
Pre-requisites:
- Clone this repo:
git clone git@github.com:carlisia/dotfiles.git - Install stow: Stow - GNU Project - Free Software Foundation - Install
Versions more recently used:
MacOS 11.4
Homebrew 3.2.0
git version 2.30.1 (Apple Git-130)
fish 3.2.2_1
tmux 3.2a
neovim 0.4.4_2
starship 0.55.0
gpg (GnuPG) 2.3.1
Most or all of the packages need to have binaries installed. See their respective documentations for specific instructions. I use Homebrew for everything unless there is no existing Homebrew formula.
Note: to prune obsolete symlinks: use the --restow flag.
Stow the package:
cd <your-path>/dotfiles
stow -vv git --target=$HOMEAfter installing, change the values in the .gitconfig file.
The fish shell is an extremely user-friendly but also powerful shell. I have been using it for maybe a decade now and cannot imagine using anything else.
Stow the package:
cd <your-path>/dotfiles
stow -vv fish --target=$HOMEAfter installing, change the values in the fish config file.
Here are some dependencies that are configured in the fish config file. All or any of these can be removed. If you want to use them, read the instructions in their respective sections below for installing and setting them up.
-
tmux
With the included configuration, any new terminal window will create a new
tmuxserver (and a window with a session; any subsequent sessions will attach to it). If you don't want to install tmux, or you do but this is not desirable, remove the configuration block that starts at line#1 of the file. Without this setting all terminals will open with afishshell. You can always typetmuxto boot it up.` -
starship
There is this line in the configuration file:
starship init fish | sourcethat executes the starship prompt. -
base16-shell
The lines around
set BASE16_SHELL "$HOME/.config/base16-shell"run the shell script that loads the base16 themes.
The Starship: Cross-Shell Prompt is a feature-full shell prompt that is compatible with almost any OS and shells. You can pick and choose how to display elements in your prompt by configuring the startship.toml file. Changes take effect immediately (click enter), no need to restart the shell.
Stow the package:
cd <your-path>/dotfiles
stow -vv starship --target=$HOMEI have my shell prompt loaded with indicators (and I could have more):
I could also quickly change it to a very minimalist version with only the immediate directory structure showing (and I could have even less):
Shell's colors: chriskempson/base16-shell: Base16 for Shells. Once installed, changing the shell color is as quick and convenient as typing base16 on any shell and tabbing twice, and arrow down to pick a selection. To go back to the default color, this is the one: base16-3024.
Stow the package:
cd <your-path>/dotfiles
stow -vv base16-shell --target=$HOMERun test script:
cd <your-path>/dotfiles
sh ./base16-shell/.config/base16-shell/colortestWhen you first run the test, it is possible that you won't have the colors properly loaded and will see this:
Open a new shell and type base16 followed by a tab to perform tab completion, followed by another tab to expland the list. It'll look like this:
Arrow up/down and click on any of the options to trigger the loading.
Run the test again. If it succeeds, you'll see this:
Now you are ready to try out the many different shell color themes.
Tmux: Home · tmux/tmux Wiki
The tmux configuration is in the tmux.conf file. It is currently configured to use this tmux theme and statusbar plugin: Powerline Double Magenta - jimeh/tmux-themepack. You can replace this by a different themed one. Only works when a shell has the tmux server booted up.
Stow the package:
cd <your-path>/dotfiles
stow -vv tmux --target=$HOMEOptional: entering the alias dev will start a tmux session with some pre-configured windows and panes setup. It will look like the screenshot in the Terminal windows section. This dev alias points to a bourne script and the alias is being set in the fish config file.
Note: Eventually these tmux scrips will be moved into fish functions.
If you don't have Neovim installed: Home - Neovim. After installing Neovim, install the junegunn/vim-plug: Minimalist Vim Plugin Manager (choose Unix, Linux).
Stow the package:
cd <your-path>/dotfiles
stow -vv nvim --target=$HOMEInstall vim-go: fatih/vim-go: Go development plugin for Vim - Install
To first install Neovim dependencies, run :PlugInstall and :GoInstallBinaries
Edit the nvim/.config/nvim/init.vim as you wish. The existing init.vim is heavily a copy of Fatih's init.vim.
Any other package in this repo is installed in the same way.