28 ms·

> I can rebuild my configuration(Aside from some fussy embedded toolchains) in half an hour or so. VS code, a few different linters, swissknife, stack tabs, tim

> I can rebuild my configuration(Aside from some fussy embedded toolchains) in half an hour or so. VS code, a few different linters, swissknife, stack tabs, timestamper, indenticator, pylance.... done. I can clone my dotfiles repo[0], run a single command that installs all my dependencies[1], another that links my config and I'm done. That gives me a fully-configured neovim with all my plugins (thanks vim-plug) within 2 minutes. [0] https://github.com/peteryates/dotfiles/ https://github.com/peteryates/dotfiles/ [1] https://github.com/peteryates/dotfiles/blob/master/Makefile#L12 https://github.com/peteryates/dotfiles/blob/master/Makefile#...

eternityforest 4y ago
Pretty impressive, but also looks like a big initial time investment. Also, will it all work on Windows? Looks like I'd need a whole new setup to get things running on a windows machine if for some reason that's what was available at work. Do things break between Linux releases? The number of extra steps you need to get something like language server protocol working makes it seem like at least some maintenance could be needed.
- petepete 4y ago
  Yeah, my config has been evolving though my career over the last twenty years or so. I'm totally not suggesting you jump ship or change the way you're working, but automating the copying of config and placing it under some kind of version control is the real winner. Things occasionally break, but the only part of my config where that's likely are my neovim plugins - things keep moving and occasionally a bit changes and I need to adapt. I can happily use a minimal neovim setup so if I need to disable LSPs for a bit it's not the end of the world. It's been mostly fine though. It would probably work on Windows but I don't think Windows has symlinks so you might need to copy files rather than stow them.

eternityforest 4y ago

Pretty impressive, but also looks like a big initial time investment. Also, will it all work on Windows? Looks like I'd need a whole new setup to get things running on a windows machine if for some reason that's what was available at work. Do things break between Linux releases? The number of extra steps you need to get something like language server protocol working makes it seem like at least some maintenance could be needed.

petepete 4y ago
Yeah, my config has been evolving though my career over the last twenty years or so. I'm totally not suggesting you jump ship or change the way you're working, but automating the copying of config and placing it under some kind of version control is the real winner. Things occasionally break, but the only part of my config where that's likely are my neovim plugins - things keep moving and occasionally a bit changes and I need to adapt. I can happily use a minimal neovim setup so if I need to disable LSPs for a bit it's not the end of the world. It's been mostly fine though. It would probably work on Windows but I don't think Windows has symlinks so you might need to copy files rather than stow them.