Fish rules

fish, the friendly interactive shell, is a commandline shell intended to be interactive and user-friendly.

fish is intentionally not fully POSIX compliant, it aims at addressing POSIX inconsistencies (as perceived by the creators) with a simplified or a different syntax. This means that even simple POSIX compliant scripts may require some significant adaptation or even full rewriting to run with fish.

Source

Switching to dash

Then you’re just running bash scripts with bash. You’re not running bash scripts with fish.

Ask the maintainer to push the update to Factory.

basically a text expansion. I have g=git, so when I type “g push” after I hit space after g, it expands it to git in the terminal as if i just typed out git myself. My history doesnt show “g push” it shows “git push” before I push enter

https://fishshell.com/docs/current/cmds/abbr.html

It’s installed on my machine but really don’t know how to make use of it that much. Any tips and tricksters?

While using the fish shell you can just type ‘help’, and it’ll pull up an offline web page with their manuals and guides. But to be honest, I dont really use fish for anything but the fancy colors and auto-completion lol.
Also fish

I think that’s the point of the comment

I have no shell configs of any kind because it seemed like everytime I used another computer, I would not have them and I would end up having the re-learn everything.

What I do is store my dotfiles in a git repository, and leave symlinks to the files in that repository. Then, when I move to another computer, pulling over all my configuration consists of doing a git pull to pull the git repo over and then running a command to set up the symlinks on that new computer. I can also make changes and selectively push things in. Some things need to be specific to a computer, and those don’t go in.

I use a homebrew script to set up the symlinks. A number of people use GNU stow for this.

kagis for an example of someone using stow

https://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html?round=two

If you edit the symlinks in emacs (and I imagine vim), it picks up on the fact that they’re symlinks into a git repository and that they’re version-controlled.

So, like:

• Have a bare git repository on home machine, the “master” copy.

• Every machine with an account has a non-bare dotfiles git repository checked out and symlinks pointing into that repo.

• Make any changes on a given machine like you normally would, then git commit them to the local non-bare dotfiles git repo and push them to the master repository.

• If setting up on a new machine, pull the git repository, and then run the command to set up the symlinks.___

That does sound like a good plan and I do have my own git server but
Can I expect to be able to do this in the various work shells I come across ?
Or do I risk becoming afoul of IT security ?(especially as it is not practical to ask each of them)

using nushell is my little rebellion against POSIX tyranny

fish, the friendly interactive shell, is a commandline shell intended to be interactive and user-friendly.

fish is intentionally not fully POSIX compliant, it aims at addressing POSIX inconsistencies (as perceived by the creators) with a simplified or a different syntax. This means that even simple POSIX compliant scripts may require some significant adaptation or even full rewriting to run with fish.

Source

Exactly, use the shell you like (nushell in my case), write POSIX scripts for maintainability, and use shebangs so you don’t have to think about it.

If you like fish but don’t use it as your login shell because it’s not POSIX you’re missing the point of the shebang

#!/bin/sh #!/bin/bash?