Dotfiles/site-modules/core/files/nushell/scripts/path.nu


export-env {
  $env.GOPATH = $"($env.HOME)/Code"
  $env.PATH = $env.PATH
    | split row ":"
    | prepend ([$env.HOME ".cargo" "bin"] | path join)
    | str join ":"
}
feat(nu): setup nushell and start off the config This is some investigation in to nushell will work. I will be looking to use this cross platform, as zsh will not work on windows. Adds some of the core modules so I don't loose my mind having to relearn mussel memory. The goal of this is to replicate my use of oh-my-zsh, I think this will take some time, I have sunk years into the zsh config. The aliases will be the same, the GOPATH project structure will be replicated and the dir hooks will be implemeted so my PATH gets setup just as I like it. 2024-12-08 10:55:03 +00:00
			`export-env {`
			`$env.GOPATH = $"($env.HOME)/Code"`
chore(shell): add module load the rvm env into nushell This is a real hack but, it works. Because nushell is not posix rvm will not natively work. This uses a login sub shell to change the ruby version with bash, it then get the all the relevant environment variables and loads them into the nushell environment. 2025-01-10 20:29:11 +00:00			`$env.PATH = $env.PATH`
			`\| split row ":"`
			`\| prepend ([$env.HOME ".cargo" "bin"] \| path join)`
			`\| str join ":"`
feat(nu): setup nushell and start off the config This is some investigation in to nushell will work. I will be looking to use this cross platform, as zsh will not work on windows. Adds some of the core modules so I don't loose my mind having to relearn mussel memory. The goal of this is to replicate my use of oh-my-zsh, I think this will take some time, I have sunk years into the zsh config. The aliases will be the same, the GOPATH project structure will be replicated and the dir hooks will be implemeted so my PATH gets setup just as I like it. 2024-12-08 10:55:03 +00:00			`}`