Eastcheap, 9 months ago

@finestructure
If I'm understanding this correctly, nothing happens to NU_LIB_DIRS if something is already assigned. Seems to me you'd need to test for that, append a colon (or whatever nushell uses for a separator) if so, and just unconditionally append '~/.config/nushell'.

I guess something like:

$env.NU_LIB_DIRS = ($env.NU_LIB_DIRS & append [':'])

$env.NU_LIB_DIRS = append ['~/.config/nushell']

But, then, I don't know anything about nushell.

finestructure, 9 months ago

@Eastcheap I'm pretty sure my version is correct - in fact, it's working again now 🤪

I've not touched the config since I posted this yesterday and now everything is working as expected on launch. Computers are weird 😅

finestructure, 8 months ago

Ok, I've figured this out. The problem is that I had an unrelated scripts directory in the directory I was launching #nushell from. That seems to override my NU_LIB_DIRS setting and lead to the error.

I've now moved my scripts to .config/nushell/_scripts and now use _scripts * works fine.

https://discord.com/channels/601130461678272522/614593951969574961/1153269044728840264

jntrnr, 9 months ago

@finestructure

There's work going on now to make it easier to use .config, though I don't think it's landed yet

finestructure, 9 months ago

@jntrnr That’s great to hear, I’ll try again in a while then 🙂