3 ms·

It has a lot of sensible defaults out of the box, and the scripting language is less esoteric than bash. I'd go into more detail but it has honestly been nearly

It has a lot of sensible defaults out of the box, and the scripting language is less esoteric than bash. I'd go into more detail but it has honestly been nearly a decade since I switched, so I barely remember. From what I recall, you can setup bash or zsh to do most of the same things, but that requires addons or tweaking configurations. With fish you just get a sensible shell right out of the box.

nirvdrum 3y ago
Writing fish completions is really easy, too. I never bothered when I used Bash, but I write them for various utilities in Fish and it makes the shell more pleasant to use. Several of my custom ones have been supplanted by upstream completions having been added in a subsequent releases.
foobarian 3y ago
How is history recording in fish? I found that keeping an eternal history tagged with screen session ids is a huge productivity boost in my bash setup and hoping to see if it's feasible in other shells.
- e12e 3y ago
  Could you expand on?: > ... tagged with screen session ids
  - foobarian 3y ago
    I set a unique session ID in screen sessions, which get recorded in history, which lets me resume the session history streams across reboots/screen restarts.
    - e12e 3y ago
      So screen manages the history, not bash? I'm not aware of a way to tag bash history?
      - foobarian 3y ago
        No, bash does, using a bunch of hacks hooked to PROMPT_COMMAND. Which is why I would like a nicer way to handle this :-)
- alwillis 3y ago
  > How is history recording in fish? I'd say it's pretty good; history gets saved in a human-readable format (YAML) in $XDG_DATA_HOME, which is configurable. A feature I really like: when retrieving completions from history, Fish shows the commands that occurred for the particular directory you're in. Searching history is also nice [1]. [1]: https://fishshell.com/docs/current/interactive.html#history-search https://fishshell.com/docs/current/interactive.html#history-...

nirvdrum 3y ago

Writing fish completions is really easy, too. I never bothered when I used Bash, but I write them for various utilities in Fish and it makes the shell more pleasant to use. Several of my custom ones have been supplanted by upstream completions having been added in a subsequent releases.

foobarian 3y ago

How is history recording in fish? I found that keeping an eternal history tagged with screen session ids is a huge productivity boost in my bash setup and hoping to see if it's feasible in other shells.

e12e 3y ago
Could you expand on?: > ... tagged with screen session ids
- foobarian 3y ago
  I set a unique session ID in screen sessions, which get recorded in history, which lets me resume the session history streams across reboots/screen restarts.
  - e12e 3y ago
    So screen manages the history, not bash? I'm not aware of a way to tag bash history?
    - foobarian 3y ago
      No, bash does, using a bunch of hacks hooked to PROMPT_COMMAND. Which is why I would like a nicer way to handle this :-)
alwillis 3y ago
> How is history recording in fish? I'd say it's pretty good; history gets saved in a human-readable format (YAML) in $XDG_DATA_HOME, which is configurable. A feature I really like: when retrieving completions from history, Fish shows the commands that occurred for the particular directory you're in. Searching history is also nice [1]. [1]: https://fishshell.com/docs/current/interactive.html#history-search https://fishshell.com/docs/current/interactive.html#history-...