2,966 karma · joined March 3, 2021
they're literally just bash scripts so you don't need mise to run them. I've heard several users have setups where they have people with and without mise running them.
The very first line contains a much better title:
> how activating the brain’s serotonin center affects behavior and motivation
My (possibly wrong) interpretation is that people feel we shouldn't make weapons. That we should just stop fighting entirely. This is clearly an extremist position, I don't think many people in the west think that we should (for example), completely blockade Ukraine from even buying weapons.
Even if you believe we should stop manufacturing weapons, don't you think this isn't likely to be a popular opinion? That it's unreasonable to expect people to share it?
most of the aliases are not documented for this reason
> The cockpit voice recorder (CVR) was overwritten after the accident. The CVR on the aircraft records a two-hour loop, and the circuit breaker in the cockpit was not pulled to stop the recording after the aircraft landed.[20] NTSB chair Jennifer Homendy subsequently called for extending capacity to 25 hours, rather than the currently mandated two hours, on all new and existing aircraft. If implemented, the new rule will align with International Civil Aviation Organization (ICAO) and European Union Aviation Safety Agency's (EASA) current regulations.[42]
"Better every few months"—yeah right.
As a simple example of how this is possible: imagine you and I both have 0.1 BTC. We could simply swap wallets which would exchange tokens but that wouldn't be represented on the blockchain at all.
I always recommend rtx.
When people first try out fish they want to add their global env vars and PATH configuration to ~/.config/fish/config.fish. You can absolutely do this similar to how you do it in ~/.bashrc. However, it's not idiomatic and once you get used to universal variables, you'll see that it's a lot of yak shaving you really just don't need editing config.fish.
Instead, if you want to permanently set an env var across the current session and all new sessions, run: `set -Ux MY_ENV_VAR 1` (set a universal variable, and export it to subprocesses)
That will put it into a machine-readable file ~/.config/fish/fish_variables. You can open it if you want but this way you don't need to source your rc files, open a new shell, or even open your editor.
For PATH, just run: `fish_add_path ~/my-new-bin`. It uses universal variables by default.
For some reason I avoided universal variables as much as possible for years using fish and now I think that was really silly.
Nushell is really more about command output (my understanding, I haven't used it heavily). With Nushell you can do things like parse TOML files right in your shell:
open Cargo.toml | get package.version
Nushell understands the structure of data but fish is like bash/zsh in that it just deals with streams of text. Nushell can even interact directly with sqlite databases which is very cool.I think if you're just looking for a simple shell that behaves a lot like bash/zsh, use fish. I think Nushell is more targeted to people that want to use its powerful data pipeline features—or are generally interested in a bigger departure from bash/zsh.
Personally I prefer fish, but I should start using Nushell more since it could definitely help with some tasks. I probably would just run Nushell when I need it though, I don't see myself running chsh to switch over.