Darren Schroeder
Darren Schroeder
It seems like there was a way to `get_config()` where it worked like we're wanting it to. Maybe it's `nu_engine::get_config(engine_state, stack)`. Can you see if that makes any difference?
> Another question: nu -c "some commands" seems always use the default nu_protocol::config::Config, settings in $nu.config-path are ignored. This is as it's supposed to be. It loads the default_config.nu. I...
can you change the parameters that get passed with $SHELL -c?
that looks like it's working at least. that's what i was thinking, just add `-l` to `-c` and it'll source your configs.
would love to get this working after our next release if you have time to work on it @nibon7
I'm not getting correct results.   I'm also wondering if there's another way to test `auto` mode than with nvim?
can you merge main so I can test this more please?
This is with `NO_COLOR=1 cargo r`. Why do you think my PROMPT_INDICATOR is not showing up? I have it set like this ```nushell $env.PROMPT_INDICATOR = {|| if ($env.LAST_EXIT_CODE == 0)...
I think the examples in your reedline PR convey this better than your screenshots above. Having said that, i couldn't really get this to work and put more comments in...
I still can't get this to work but I could be doing something wrong.