Chaned the tmux theme for the numbering of the windows from dsquare to
fsquare. This gives us a filled in square with contrast to easily see
the window numbers.
Due to the fact that this config is not used we are going to clean this
up. Going forward only the plugins directory will be used so that any
custom plugins I want to add can be added here and managed locally. This
leaves the neovim distribution (if wanted) up to the user.
Reviewed-on: #37
Fixed issue where when opening a second terminal it'd open in the same
tmux session making it so that it's just a mirror of the first terminal.
Closing that terminal would close all terminals. Also added an alias to
vim which calls nvim
Reviewed-on: #36
Removed cmake from `ensure_installed` so that we dont lok to make
sure cmake is installd when starting or updating nvim. It makes
more sense to have the user install this with Mason instead.
Moved sudo notification (the wizard) over to the left hand side of the
status bar before the prompt character. It makes it easier to see you
have escalated privileges and it plays nicer with kitty formatting.
Added in all the required plugins to get code completions, snippets,
linting, and formatting working. Also configured to auto install
a LSP for any language that isn't currently installed.
Integrated LSP functionality into neovim configurations. Installed
Mason to manage the installation of language servers. Used
mason-lspconfig for the bridge between Mason and nvim-lspconfig.
Also installed telescope-ui-select plugin to telescope to allow it
to use telescope and it's windows for code actions.
Modified the following options:
- Telescope
- Changed to use latest release branch instead of a specific verson
- Vim Options
- Created custom keybinds for moving between windows:
- <C-A-h> - Move Window Left
- <C-A-j> - Move Window Down
- <C-A-k> - Move Window Up
- <C-A-l> - Move Window Right
Added in barbar plugin to give us a tab line. Also added in keybinds
as follows for navigation:
<C-j> Previous Tab
<C-k> Next Tab
<C-h> Move Tab Left
<C-l> Move Tab Right
Added in my custom configuration from Neovim that I started writing
from scratch. So far only have implemented tokyonight theme,
telescope, treesitter, and neotree.
Added the kitty/ directory to add in the kitty config files. also
setup in a way that when passing --dotfiles to stow it will
convert to a dotfile when stowing. This allows us to not have to
use dotfiles to avoid having hidden files in the repository.
Will be standard going forward.
2024-08-01 13:38:19 -04:00
13 changed files with 259 additions and 32 deletions
Dotfiles is a repository to hold my collection of dotfiles. Each directory is it's own module if you will for enabling certain subsets of the dotfiles.
## Installation
To install dotfiles first you need to clone the repository. I highly recommend that you clone into your home directory so that you don't need to pass a `--target` every time we invoke stow.
We can clone the repository with the following command:
After cloning that is it. Just change into the directory and you can deploy or un-deploy following the below instructions.
## Deploying
From inside of our dotfiles directory we can deploy very easily with the following command:
`stow --dotfiles --verbose zsh`
If this command succeeds that is it. Stow creates symlinks to the files in this directory for where they need to go. If you already have configuration files in place then the command may fail. If that happens we have a couple of choices. First things first we need to adopt in the already existing file like so:
`stow --dotfiles --adopt --verbose zsh`
What adopt will do is it will pull your already existing files in and put it's contents in in place of our contents. You have 2 options from this point.
### Keeping Your Changes
If you want to keep your configuration instead of using the one provided in the repository you can just do a git commit. Highly recommend changing branches first. This can be done like so:
```bash
git checkout -b my-custom-config
git add --all
git commit -m "My custom configuration"
```
### Using the repository version
If you instead want to use the version of the configuration provided from this repository that is easy as well. That can be accomplished with the following:
`git restore zsh`
In this instance that will revert all the changes to the zsh module (effectively erasing your changes and putting back the repository configuration) but the symlinks are still in place. Just replace `zsh` with the module that you want to restore back to the repository version.
## Undeploying
If you want to undeploy the stowed files that can be done with the following:
`stow --delete --verbose zsh`
This command will unstow the zsh changes. The symlinks are removed and now you manually have to take care of the changes. If instead you want to redeploy you can run the following:
`stow --restow --verbose zsh`
This will unstow and then stow the files again. This is great to run if you for instance have moved files and you need to update the symlinks.
## Useful Hints
### Simulating Changes
If you are ever unsure of what is going to happen with a command you can always pass the `--simulate` flag. This combined with `--verbose` will show you exactly what would have changed without making any changes to any files on your system.
# We want to make sure that autocompletions are loaded
autoload -Uz compinit && compinit
# Initialize zoxide
eval "$(zoxide init zsh)"
# Finally we want to use starship for our prompt
# (because rust that's why)
eval "$(starship init zsh)"
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.