71–78 of 78 posts
I really liked fish, but as someone who is still learning bash/cli scripting, it makes things difficult when instructions from programs come only in Bash syntax, which does not work well with fish (some things with homebrew were an absolute nightmare to install).
The fact that you cannot redirect stderr to stdout and pipe to another command is a bit of a stumbling point for me. When I saw the bug[1] for the first time I thought that it must be some strange corner case, but it turns out it is a real bug. After reading the bug report I started to wonder if there were any other other unixy features that were missing. I/O redirection is a core unix concept in my opinion. [1] "Red…
I like the features it has, but every time someone post a link to fish shell, I wonder why I would switch from bash or zsh. Will this really be THAT MUCH BETTER? Will I just run into weird errors? Is it totally sh compliant? These are important things to know and should be on the homepage.
I am a year-or-two-old fishshell convert who is reasonably well versed in bash and tried using zsh and bash with a big .bashrc. A few things stand out to me as huge pluses: - It has a lot of cool functionality out of the box such as highlighting, smarter autocomplete (type in a partial word at the prompt and hit up instead of the cumbersome bash ctrl r/s history prompt that loves to beep at you), directory history (a…
bind '"\e[A":history-search-backward'
bind '"\e[B":history-search-forward'I've been using fish for a while now. Overall it's pretty great. Here's my fish config if you want to see an example: https://bitbucket.org/sjl/dotfiles/src/tip/fish/config.fish
As you'll see, I like the way Fish automatically loads functions from, "$HOME/.config/fish/functions/". It keeps my config.fish file pretty lean.
I've been using fish for a while and have generally been very happy, I'm even working on creating a set of functions for ROS to integrate with fish the way it currently does with bash and zsh. My one tiny gripe is the way that if I set foo this that "the other" then echo $faux; echo $faux[1] doesn't produce anything, but echo $foo[4] gives me an error message that I can't just pipe to /dev/null Also, writing autocomp…
It would be pretty amazing, considering the file resolution properties of ROS. I actually love it since I don't have to be in the same directory and it's easy to go through many projects.
Just curious what sort of work are you doing on ROS. Earlier this year I was working on simulation stuff in Gazebo.
I've been using fish for a while and have generally been very happy, I'm even working on creating a set of functions for ROS to integrate with fish the way it currently does with bash and zsh. My one tiny gripe is the way that if I set foo this that "the other" then echo $faux; echo $faux[1] doesn't produce anything, but echo $foo[4] gives me an error message that I can't just pipe to /dev/null Also, writing autocomp…
That's very interesting, especially for people interested in using ROS as an educational platform. It would be pretty amazing, considering the file resolution properties of ROS. I actually love it since I don't have to be in the same directory and it's easy to go through many projects. Just curious what sort of work are you doing on ROS. Earlier this year I was working on simulation stuff in Gazebo.
I've been using fish for a while now. Overall it's pretty great. Here's my fish config if you want to see an example: https://bitbucket.org/sjl/dotfiles/src/tip/fish/config.fish
Gotta say, this one is my favorite: 112 function hey_virtualbox_shut_down_or_i_will_fucking_cut_you 113 VBoxManage controlvm $argv poweroff 114 end
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sbin/sh...