Closed dezren39 closed 3 weeks ago
ps there is an oil and an oils-for-unix package, each unique full packages. maybe keep the oil name to not affect existing configurations, but as an alias to oils-for-unix or something.
ahh oil is the python compile? ok that answers one question
maybe it would be good to have a home-manager or nixos module or both to configure default shopt and which pkgs between ysh/osh etc
Yes the difference between the two tarballs explained in the "packaging guidelines" - https://www.oilshell.org/release/0.22.0/
(the oil
tarball will go away eventually)
I'm not familiar with home-manager but there are a couple dirs to make for history and rc files - https://www.oilshell.org/release/0.22.0/doc/getting-started.html
works now dunno why
edit: leaving this closed unless i encounter again, but i realized my fork has the following added:
mainProgram = "osh";
hi i want to use ysh or maybe osh as my default shell in nixos, for nushell I just set it like so
doing the same doesn't work for oils.
I'm not sure if i need to make a nixos module, or maybe it's because oils-for-unix and oil both have multiple binaries? it may be that a package for ysh and osh is needed, or maybe the oils-for-unix package could have embedded functions? I dunno. I think I could hack this to work as a custom shell, but it would be nice if the nix package itself did it 'right'.
I know this isn't the nixpkgs repo, but it's uh.. a bit busy there. If I get time and find a solution I'll comment here.