dotfriedrice

Call me old fashioned but what's wrong with having a regular git repo anywhere you want with all of your dotfiles and them symlink those files to where they need to go? If you wanted to you could && a few symlinks and other commands into 1 copy / paste'able command to get up and running really quickly. It's also painless to manage secrets by sourcing in optional files. It also works nicely when you want files living across 2 systems (such as WSL 2 and Windows) where on a Windows box you consider certain Windows files dotfiles even though technically they exist elsewhere. I've been managing my dotfiles like this for a few years and it seems to be working out well not just for myself but others who have want to use them either partially or in full. I open sourced them here: https://github.com/nickjj/dotfiles I purposely broke up some of the

> Getting the same working with WSL2 was a pain in the ass, and I eventually gave up. Overall it works the same as WSL 1, you just need to change DISPLAY=:0 to DISPLAY="$(/sbin/ip route | awk '/default/ { print $3 }'):0" Here's a snippet from my bashrc that handles both WSL 1 and WSL 2: https://github.com/nickjj/dotfiles/blob/385007837ab787a2be2e...

You'll want to make sure clipboard sharing is enabled too. This way you can share clipboard data from WSL and Windows. My VcXsrv config is public on GitHub at: https://github.com/nickjj/dotfiles/blob/master/c/Users/Nick/... Putting it in that directory sets VcXsrc to start when Windows boots up. You would just replace "Nick" with your Windows user name and put it in that path. Then you never have to worry about starting VcXsrv ever again. Also if anyone is using both WSL 2 and WSL 1, you need to set different values for DISPLAY depending on which version you use. My .bashrc handles this at: https://github.com/nickjj/dotfiles/blob/385007837ab787a2be2e...

Thanks. Yeah good call on the lack of color in that one. Here's a better example https://youtu.be/44pNDuRO77g?t=269 , it's straight to a point where I'm in a vimrc file with about the smallest text I ever use on video. I'm guessing the comments would be pretty hard to read in a high sun light area, that's my only complaint with the One theme -- the contrast on them is a bit low. In the video you linked I see what you mean. I haven't tested it outside but just eyeballing some of the screenshots in the presentation the blue function names are likely impossible to read, the dark orange / red module names could be borderline too since it's kind of dark text on a dark background, and even the green atoms are a bit similar to the background in terms of darkness. I'm not sure what color theme that is but personally I wouldn't use it. I try to st

I've been running WSL and then WSL 2 for a while now as my full time development environment, it's quite solid. This isn't mentioned in the blog post but if you use VcXsrv you can have it start up automatically by putting its config in your start up folder. That's what I've been doing here for the last year or so: https://github.com/nickjj/dotfiles/blob/master/c/Users/Nick/... If anyone prefers video about 6 months ago I recorded https://www.youtube.com/watch?v=idW-an99TAM which is about a 30 minute drive by of setting up WSL 2 + Docker + VcXsrv and a bunch of other tools that are handy on Windows for web development.

I recently added my Vim spell check file to my dotfiles at: https://github.com/nickjj/dotfiles/commit/b5563e3baabc95ec3829f02c26b3fcd4900425fe It has 305 unique programming / tech terms that I find myself referencing in documentation, technical blog posts and podcast show notes. It's not an exhaustive list. I've been casually appending to it over the last year or so. It would be cool if others posted their list so we can merge them together.

I'm a big fan of using wsltty. Everything works and it has very low input latency. I run tmux and terminal Vim in it every day for hours of coding. Screenshots of my terminal and set up are in my dotfiles https://github.com/nickjj/dotfiles. It looks exactly the same as xterm on my native Linux laptop. I've even gone as far as running i3 through WSL1 / wsltty and it worked very well with 1 monitor. I stopped using it because I have 2 monitors, but if I had 1 monitor it would have been usable for day to day development.

> It's my understanding that mouse input events have been available for decades. I'm not sure where you're seeing problems with them. Here's a narrated few minute video that shows how mouse events don't get passed through to the terminal (with or without tmux), and how they do get passed through using WSLtty using the same exact tmux and Vim configs for both environments. The video: https://drive.google.com/file/d/1DIR3iwc6AkOLQ19Scv88VI17Wdg... My dotfiles are open source at: https://github.com/nickjj/dotfiles