Nicolas Dudebout

The recent work on hsenv to support multiple versions and be cleaner has completely broken the emacs support. The emacs support worked by setting the same variables as the activate...

You are indeed right, this new approach would not likely help. I just read the intro and he talks about GUI working without a shell and I got excited. However,...

Unfortunately we also need to change the environment variables used. Take a look at the fork I mentionned earlier. It starts in that direction with what I use. The problem...

The problem lies in Snap making an assumption about the buildDir. Look at this fix in pandoc for example: https://github.com/jgm/pandoc/commit/ff0061281f23b730034aeeb5de0568d6eec08b32

One dist directory per hsenv is the desired behavior. An hsenv is an isolated environment. If you create multiple hsenv and do different configurations in each hsenv you will expect...

What I think would be good for that most common case (i.e. having only one hsenv) is to restore the unnamed hsenv folder. I thought it was better when an...

I think the new behavior is counter intuitive when you use the other equivalent tools such as virtualenv for python. You should have to use a flag only when you...

The default naming of .hsenv_ is still a little weird. What is so special about the name of the containing dir?

This is exactly what I think we should do. And keep the `--name` option. This way when you do not give a name there is no name given instead of...

@Infinisil, your problem stems from [the first line in your `shell.nix` file](https://github.com/Infinisil/soph/blob/master/shell.nix#L1): ``` with import ./. {}; ``` Because it imports "the current directory", that directory ends up being watched...