https://github.com/philgyford/dotfiles

System config stuff
https://github.com/philgyford/dotfiles

dotfiles shell

Last synced: about 2 months ago
JSON representation

System config stuff

• Host: GitHub
• URL: https://github.com/philgyford/dotfiles
• Owner: philgyford
• Created: 2013-04-06T16:38:30.000Z (about 13 years ago)
• Default Branch: main
• Last Pushed: 2026-04-17T14:28:24.000Z (3 months ago)
• Last Synced: 2026-04-17T16:32:54.552Z (3 months ago)
• Topics: dotfiles, shell
• Language: Lua
• Homepage:
• Size: 2.17 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# dotfiles

My system config stuff. Includes Neovim config (in `.config/nvim/`).

Switched from using bash to zsh in 2020, so the bash files probably won't

get many updates from here on.

For each of the files/folders do something like:

    $ ln -s ~/Projects/personal/dotfiles/filename ~/.filename

--

## Neovim

    $ ln -s ~/Projects/personal/dotfiles/.config/nvim ~/.config/nvim

    $ ln -s ~/Projects/personal/dotfiles/.config/nvim/lsp ~/.config/nvim/lsp

    $ ln -s ~/Projects/personal/dotfiles/.config/nvim/init.lua ~/.config/nvim/init.lua

I also had to install at least these things using Homebrew, for various plugins:

    $ brew install ripgrep

    $ brew install fzf

    $ brew install tree-sitter-cli

    $ brew install npm  # For emmet-language-server and biome

    $ brew install stylua  # For conform to format lua files

And then:

    $ npm install -g @olrtg/emmet-language-server

    $ npm install -g @biomejs/biome

And after installing the plugins, including Telescope, we *might* need to

manually do this build step for its optional fzf plugin:

    $ cd ~/.local/share/nvim/site/pack/core/opt/telescope-fzf-native.nvim

    $ make

### Plugins

#### Add a new plugin

1. Create a new file in `.config/nvim/lua/plugins/`. This should call

   `vim.pack.add()` on the repository URL, and then probably do at least

   `require("").setup()`.

2. Then `require()` that file from `.config/nvim/lua/plugins/init.lua`.

3. Either re-open neovim or do `:restart`.

#### Update plugins

Do `:lua vim.pack.update()` or shortcut `pu` to update all plugins.

#### Remove a plugin

Do `:lua vim.pack.del({"plugin-name"})`. (And delete file from `plugins`

folder?)

### Checking things are OK

Do `:checkhealth` to get a full report of any problems, or `:checkhealth

` for a specific plugin's.

### Adding support for different languages / file types

#### 1. Add a language server

1. Add a config file for it in `.config/nvim/lsp/`. See examples [at

   nvim-lspconfig](https://github.com/neovim/nvim-lspconfig/blob/master/doc/configs.md)

3. Use `:MasonInstall ` to install the language server.

#### 2. Add treesitter support

1. Ensure it's listed in `file_types` in

   `.config/nvim/lua/pluings/treesitter.lua`.

When you first open a file of a new type, there might be an error but

nvim-treesitter should then automatically install the new parser. You may

need to reload the file in question again.

Or manually install a new parser with `:TSInstall `.

Diagnose problems with `:checkhealth vim.lsp`

---

## VS Code

You should do something like this:

    $ ln -s ~/Projects/personal/dotfiles/vscode/keybindings.json ~/Library/Application\ Support/Code/User/keybindings.json

    $ ln -s ~/Projects/personal/dotfiles/vscode/settings.json ~/Library/Application\ Support/Code/User/settings.json

--

## Starship prompt

    $ ln -s ~/Projects/personal/dotfiles/.config/starship.toml ~/.config/starship.toml

--

## Other old notes

For Atom, you should also install the "package-sync" Package, which will read

your `.atom/packages.cson` file and install the necessary Packages. 

--

- Phil Gyford

- phil@gyford.com

- https://www.gyford.com