Pavel Volokitin
Pavel Volokitin
This sounds interesting. I wouldn't have it on by default though. But having a setting to enabling it would be great.
The second error with the wrong terminal size is now fixes in master. I will release a new version tomorrow. As per the first screenshot, I installed helix with scoop...
The error with the terminal size was fixed in mprocs 0.4.0. And for now I can't do anything with the background problem, since I can't reproduce the issue.
I tried to zoom in/out termusic in mprocs on Windows and it worked well. From this error it is not clear what went wrong. But I see that error handling...
Happy to hear that you find mprocs useful. I wanted to use default shell but quickly gave up on that idea. I think it will bring a lot of confusion...
I didn't change code related to those failing tests. The vt100 seems to be unmaintained, so at some point these tests might need to be fixed in this repo. But...
After quickly checking a couple of failing tests, it is not clear which behavior is correct - expected or actual.
`cwd` doesn't support env variables. It is just a plain path string. You can try to do something like this: `shell: "cd $XDG_CONFIG_HOME/nvim && entangled daemon"`.
I think it's not justified to add that logic to `cwd`. But even if adding that feature, I would expect it to only use env variables that are passed to...
I'm contemplating adding some operator to config which would allow using env variables. Something like this: ```yaml procs: neovim_literate: shell: entangled daemon cwd: { $expand: "$XDG_CONFIG_HOME/nvim" } ``` Where `{...