4 ms·

I'll switch to fish after it stops expanding `car TAB` to `blkdiscard` when I don't have `cargo` in path. Non-prefix completion for commands is plain evil.

dingnuts 1y ago
I bet this is configurable but I wanted to say that this is totally personal preference; I have the exact opposite opinion. Prefix only matching requires much more tab slapping in my experience.
- yencabulator 1y ago
  I believe you would lose that bet. I look every few years and I don't see it
  - natebc 1y ago
    interestingly this also seems to have come up pretty recently in their discussions. https://github.com/fish-shell/fish-shell/discussions/11670#discussioncomment-13904580 https://github.com/fish-shell/fish-shell/discussions/11670#d... > I'm not sure that subsequence matching ever produces results that people expect (I feel like we've discussed this before but haven't had time to go digging) No solution, but the discussion seems positive, from a maintainer too.
  - thiht 1y ago
    I gave up on fish after a few weeks because of a similar preference issue where the fish maintainers flat out refused to make a bad default configurable: https://github.com/fish-shell/fish-shell/issues/8618 https://github.com/fish-shell/fish-shell/issues/8618 > We don't really do config flags like this, as a philosophical point. > I would be against accepting such a PR. I do not believe this should be changed. I understand that they want to keep the list of configs short and manageable, but it means that's not a tool for me. I'm all for good, opinionated defaults but I want to be able to make some changes if I want to. They apparently reconsidered and implemented the change since migrating fish to rust though.
wpm 1y ago
I’ll switch to fish when it comes preinstalled on all of the computers I use so I can write scripts in it.
- yencabulator 1y ago
  I already avoid bash scripting so I lose very little. Shell scripting beyond throwaway one-liners is a problem not a solution. (Well that and all my machines come from the same NixOS configs.)
  - nothrabannosir 1y ago
    Ha that’s funny, considering nixos is 99% stdenv which is one of the worst bash monstrosities in existence, and drives people ever further into the swamp of bash. (Ever tried to debug stdenv setup hooks? I still have water damage from the tears.) I have personally embraced the insanity but let’s not kid ourselves about nixos basically just being three bashes in a trench coat. Basically https://xkcd.com/224/ https://xkcd.com/224/ , but s/lisp/nix/ s/perl/bash/
    - yencabulator 1y ago
      It's my daily driver, but I am holding my nose. Some year something better will show up from someone with more taste (and I know I am not alone in having thoughts on what it would look like), but for now the yak has already been shaven. At least the builds are sandboxed.
      - nothrabannosir 1y ago
        Guix if you can stomach it.
- kstrauser 1y ago
  Do you really limit your shell experience to plain POSIX? That sounds masochistic.

dingnuts 1y ago

I bet this is configurable but I wanted to say that this is totally personal preference; I have the exact opposite opinion. Prefix only matching requires much more tab slapping in my experience.

yencabulator 1y ago
I believe you would lose that bet. I look every few years and I don't see it
- natebc 1y ago
  interestingly this also seems to have come up pretty recently in their discussions. https://github.com/fish-shell/fish-shell/discussions/11670#discussioncomment-13904580 https://github.com/fish-shell/fish-shell/discussions/11670#d... > I'm not sure that subsequence matching ever produces results that people expect (I feel like we've discussed this before but haven't had time to go digging) No solution, but the discussion seems positive, from a maintainer too.
- thiht 1y ago
  I gave up on fish after a few weeks because of a similar preference issue where the fish maintainers flat out refused to make a bad default configurable: https://github.com/fish-shell/fish-shell/issues/8618 https://github.com/fish-shell/fish-shell/issues/8618 > We don't really do config flags like this, as a philosophical point. > I would be against accepting such a PR. I do not believe this should be changed. I understand that they want to keep the list of configs short and manageable, but it means that's not a tool for me. I'm all for good, opinionated defaults but I want to be able to make some changes if I want to. They apparently reconsidered and implemented the change since migrating fish to rust though.

wpm 1y ago

I’ll switch to fish when it comes preinstalled on all of the computers I use so I can write scripts in it.

yencabulator 1y ago
I already avoid bash scripting so I lose very little. Shell scripting beyond throwaway one-liners is a problem not a solution. (Well that and all my machines come from the same NixOS configs.)
- nothrabannosir 1y ago
  Ha that’s funny, considering nixos is 99% stdenv which is one of the worst bash monstrosities in existence, and drives people ever further into the swamp of bash. (Ever tried to debug stdenv setup hooks? I still have water damage from the tears.) I have personally embraced the insanity but let’s not kid ourselves about nixos basically just being three bashes in a trench coat. Basically https://xkcd.com/224/ https://xkcd.com/224/ , but s/lisp/nix/ s/perl/bash/
  - yencabulator 1y ago
    It's my daily driver, but I am holding my nose. Some year something better will show up from someone with more taste (and I know I am not alone in having thoughts on what it would look like), but for now the yak has already been shaven. At least the builds are sandboxed.
    - nothrabannosir 1y ago
      Guix if you can stomach it.
kstrauser 1y ago
Do you really limit your shell experience to plain POSIX? That sounds masochistic.