Earlier quoted context omitted.
I think the "nushell/nushell" part makes it clear which repo it is talking about.
I didn't find it clear, I also thought it was a GitHub project.
Really seemed like a GH project to me.
GitHub – nushell/nushell: A new type of shell
211–220 of 411 posts
Re: GitHub – nushell/nushell: A new type of shell
#212It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least it works enough that I can stop trying to figure out how to install bash on windows or what's wrong with my laptop.
Re: GitHub – nushell/nushell: A new type of shell
#213It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least…
I installed wsl on like 10 machines, including "newer laptops", and never had problems with the setup. Instead of solving your actual problem you created a whole new problem domain, that seems... not like the way to go
Re: GitHub – nushell/nushell: A new type of shell
#214there's fair amount of comments here (and in other similar posts) which read like:
'nushell is basically a powershell something' 'bash/zsh is better/worse than pwsh/etcshell'
this is very unfair because pwsh allows control over of the all .NET/COM+ available in a system (well, .NET Core only on non-MS, but still).
while nushell stands on its own shoulders or if u like - allows control of other programs executed, but would not easily call into any API that is a language-specific one nor parse its output as structured one.
so when comparing bash, zsh, nushell, pwsh one should take into consideration that these have different foundations and goals even. like perl stands on top of CPAN, all the JVM stuff on top of all classes, etc.
although it is difficult to say why no one has created (to my knowledge) reasonable JVM-based shell, nor a python-based-one, since java targets such a large number of OS/platforms and provides such a broad library. perhaps because people assume that a shell program should follow the UNIX concept of one-program-does-one-thing-only. on the contrary - it would be a killer feature to have nushell be able to natively execute java/python/whatever API calls and use the structured output (like pwsh indeed).
in essence - is very limiting to compare bash to pwsh only in the sense of 'how much can be done with only few characters', because this always leads to very opinionated and biased arguments and eventually discussions taken out of context.
Re: GitHub – nushell/nushell: A new type of shell
#215It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least…
What was the problem with WSL? It's been trivial to install on every machine I've tried: work, personal, old, new, upgraded from Windows 7, local account, Microsoft account, etc.
Re: GitHub – nushell/nushell: A new type of shell
#216It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least…
I had problems with WSL on my newer laptop, and it all came down to disabling Secure Boot.
Re: GitHub – nushell/nushell: A new type of shell
#217It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least…
What was the problem with WSL? It's been trivial to install on every machine I've tried: work, personal, old, new, upgraded from Windows 7, local account, Microsoft account, etc.
Yes I had that experience until this one laptop, ironically it's a surface laptop. Most likely I screwed some setting up but now no tutorial for bash in windows or wsl works anymore and I have no idea how to work around.
Re: GitHub – nushell/nushell: A new type of shell
#218Earlier quoted context omitted.
powershell for unix is ... powershell: https://docs.microsoft.com/en-us/powershell/scripting/instal...
Am I missing something cool by not looking into PowerShell for Linux? Anyone using it could chime in and share how it improves their workflow? What kind of tools does it bring to the table?
Disclaimer: I use PowerShell on Windows, I've never tried it on Linux, but I don't see why its advantages wouldn't transfer.
That being said, I think it's main advantages are:
- Typed object streams, which gives you stuff like autocomplete, IDE support, and generally there's no need to muck about with sed/awk/xargs - Very fast, it's absolutely fine to read a file line by line, and parse it in a script, whereas doing the same in bash/awk is a ton slower than clever use of cat/grep/wc (and a myriad of other tools) - Due to type information being retained, it's a lot easier to figure out what a given script does, without having to know how the output of a given tool looks like, given it's particular command line switches.
This is just my opinion, but PowerShell is a lot more geared toward people like me, who only write a script once in a blue moon/muck about with the build scripts occasionally, while Bash is more geared toward veteran sysadmins who live and breathe this stuff.
Re: GitHub – nushell/nushell: A new type of shell
#219It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least…
I installed wsl on like 10 machines, including "newer laptops", and never had problems with the setup. Instead of solving your actual problem you created a whole new problem domain, that seems... not like the way to go
The "domain" I care about is for basic build scripts to work on Windows and Linux. Whichever way gets me back to regular work is the best way! I do not have the experience to debug when BoW or WSL do not work unfortunately.
Re: GitHub – nushell/nushell: A new type of shell
#220It's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least…
I had problems with WSL on my newer laptop, and it all came down to disabling Secure Boot.
Oh, thanks for sharing. Maybe I'll try that.