"Oh god no, mah marijuana patch!!..."
Man I've gotta rewatch it now.
"Oh god no, mah marijuana patch!!..."
Man I've gotta rewatch it now.
On a golden parachute I'm sure.
sickofit
For what it's worth, I don't understand the nix language or all the package manager functions in their entirety. I generally use what I need and that's it. Most information I've required that is nixpkgs
-specific I was able to find in the manual. home-manager has one as well and it's been the best reference for me.
If so, how does that solve the problem of clutter in $HOME ?
If it wasn't clear from my message, the problem(s) these tools are solving for me would be 1. not having to keep track of my dotfiles and their directories, and 2. not storing configuration files directly on the disk I use for the $HOME
dir. I'm not claiming these tools would solve clutter in the $HOME
dir. Further, I think it should be alright for me to share tools for managing configuration files in your home directory in a discussion that directly relates to that subject.
So you create a symlink from $HOME/.program.ini to something in the nix store?
Normally it's the other way around. When you use nix and home-manager, you're technically generating files that will live in the nix-store and nix/home-manager will take care of symlinking those files to locations in your $HOME
dir.
In this scenario though, I would use the https://nix-community.github.io/home-manager/options.html#opt-home.file option from home-manager to create a symlinks to a location that's outside of my $HOME
dir so those files don't have to live on my home disk.
My particular use-case is that I want persistent configuration files that are shared throughout a handful of devices on my network. To this end, I use some home-manager symlinks that lead to a network folder where all these various directories and configuration files actually live. I edit those configurations in a single place and their changes propagate across the network to all the devices that would use them.
You can manage symlinks pretty easy with home-manager. I'd personally setup symlinks for these app configuration directories if I don't want them storing files directly on the disk I use for $HOME
. It's also done in a delcarative way that can persist across multiple computers.
Wizards of the Coast
This is the right answer, and I wish more people would grasp that.
Is this IDE going to make it impossible to install the Rust plugin in their other IDEs? Like is there anything preventing a user from continuing to use the Rust plugin and CLion after this has been released?
Almost all of these IDEs have language-specific features in them. PyCharm has Scientific tools (like SciView) for generating graphs using code and data. Rider features a pretty nice Windows Form builder for generating and creating GUIs for applications. Etc.
I can't imagine it being very useful or practical to unload all these language-specific plugins each time you open the program to write in a language that can't utilize those features.
Pretty neat. You can use this with RPCS3. Unfortunately it's probably a matter of time before Take-Two/Rockstar ruin all the fun as they've historically done with fan projects.