my dotfiles
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Jordan Orelli 1a4a4b0166 nvim completion is working fine without this 1 year ago
.config some vim tweaks to highlight the current line 2 years ago
Vundle.vim@b255382d62 organizing some stufffff 2 years ago
nvim neovim terminal colors 2 years ago
prefs can clone git repos now 2 years ago
scripts winmode concept hmm 2 years ago
vim nvim completion is working fine without this 1 year ago
windows this is getting good 2 years ago
.bash_profile neovim linux 2 years ago
.bashrc remove extra cargo env sourcing 2 years ago
.gitignore i dunno let's try some new shit 2 years ago
.gitignore_global ignore OS temp files and compiled files 9 years ago
.gitmodules maybe packer should not be a submodule 2 years ago
.screenrc adding screenrc 11 years ago
.tmux.conf dunno what these tmux settings are but ok 2 years ago
README.md organizing some stufffff 2 years ago
cargo-config.toml nvim windows kinda works now yay 2 years ago
code-settings.json remove old zig thing 2 years ago
config.ini neovim linux 2 years ago
install better config format 2 years ago
vimrc neovim linux 2 years ago

README.md

dotfiles

my preferences files

setup

The way this repo is setup is that the .dotfiles directory is expected to be the authoritative storage of all of the preferences file on a given machine. The install script creates the necessary symlinks for these preference files to be seen by the appropriate applications.

sharing between WSL and Windows

If you want to use this repo to manage the preferences file of both a WSL instance and its Windows host, clone this repo on WSL and then symlink the directory into the home directory of the Windows host like so:

C:\Users\Name>mklink /D .dotfiles \\wsl$\instance\home\name\.dotfiles

You can then navigate into the Linux directory from Windows, either on the command line or in Explorer.exe. Using an administrator shell, run the install script from the Windows side. Windows requires admin privileges in order to make symbolic links, so you need an admin shell to register new links on Windows.