71–80 of 154 posts
Can you split windows in fish shell? Or is that the job of an terminal emulator, not the job of a shell?
I like the idea of fish, but I've had issues with other programs assuming things about my shell. Like vim and I think even other programs. There's something fish doesn't do, that other shells like bash and zsh do, that breaks other programs. I can't remember the specifics, but fish breaks stuff for me when I tried it, and I tried it pretty recently.
There are two problems I've found that prevent me from using fish more: 1. Fish syntax breaks virtualenv (Edit: Okay, apparently this isn't actually a problem). 2. Fish does not have the equivalent of 'disown' in bash. This is fine if you exit the parent shell normally, but not if you send SIGKILL, which my window manager (wmii and i3) does.
. bin/activate.fishI tried fish for a while but found it jarring switching between it and bash when working on remote machines where fish is not installed. I was also surprised when I first started using fish that it can't synchronize history between shell instances, which is a killer feature for me. So after about a month with fish I've switched to zsh. https://github.com/fish-shell/fish-shell/issues/825 http://ptspts.blogspot.com/201…
"Previously, a single % would pid-expand to either all
backgrounded jobs, or all jobs owned by your user. Now it
expands to the last job backgrounded. If no job is in the
background, it will fail to expand. In particular, fg %
can be used to put the most recent background job in the
foreground."
Maybe it's just because I really like to customize my shell, but I can't stand the philosophy of fish [1]. The relevant part: "Configurability is the root of all evil." I can almost agree with this on many user facing consumer applications but a shell is so far from that. [1]: http://ridiculousfish.com/shell/user_doc/html/design.html#co...
Can anyone tell me if there is a substitute for history expansions such as "sudo !!" or "vi !$" ?
"Previously, a single % would pid-expand to either all backgrounded jobs, or all jobs owned by your user. Now it expands to the last job backgrounded. If no job is in the background, it will fail to expand. In particular, fg % can be used to put the most recent background job in the foreground." oh! Can fish background tasks now? I haven't being following very closely, I really should update my shell.
I am currently running fish version 2.0.0 (Love it btw!) - does anyone know if there is a way to manually self update to 2.1? Or do I need to reinstall the package.
brew update
brew upgrade fish
I just had an argument with some folks around Bash vs Fish, my argument was as simple as "i like it", their was "you won't learn anything, fish sucks, you can do anything it does with a modded bash" ... but that's the point, i don't want to modify and configure, i want it to work out of the box.