Live data from Hacker News

Fish shell

fishshell.com

181–188 of 188 posts

Re: Fish shell

#181

Earlier quoted context omitted.

It sounds amazing. Hey, since you are the lead dev of the fish shell, a serious problem occurred to me weeks ago, I was compiling a QT client in fish, and there is already an environment value called `LD_LIBRARY_PATH` (including other values the compilation needs) defined in /etc/ld.so.conf.d/ and /etc/profile.d/ but fish cannot find them, if I use `set -g ...` to set it in fish shell prompt and then do the compilati…

Thanks for sharing this. The files in the *.d directories are bourne-syntax, and so fish can't understand them; that's why fish doesn't read them (excepting /etc/paths.d). bash only reads the files in /etc/profile.d when launched interactively, so those files won't be read for #!/bin/sh scripts. Of course, if you launch the script from an interactive bash session, the script will inherit the variables that the profil…

/bin/sh isn't BASH always ?? I'm on a Debian derived Linux:

$ ls -l /bin/sh lrwxrwxrwx 1 root root 4 Feb 19 17:51 /bin/sh -> dash

Re: Fish shell

#182

Hey, I'm the lead dev of the fish shell. There's some great discussion in this thread! For those who are interested, the fish shell is about to release version 2.2, a very significant release that wraps up eighteen months of development. You can try the beta now: http://fishshell.com/beta/ A sampling of new features: - vi mode (yay!) - Abbreviations, fish's take on aliases. They expand as you type them. - A new "inli…

Can you explain why your website requires JS?

Re: Fish shell

#183
post #164

Fun with fish, frogs and fortunes: https://gist.github.com/montanaflynn/04246fc5da998d15e713

https://github.com/qznc/dot/blob/master/config/fish/config.f... I use something similar: tux instead of frogs and a personal fortunes file. Mine also prints the current date, hostname and uptime.

Nice! I've actually adopted a minimal approach as of late: https://gist.github.com/montanaflynn/da1f0565c95a5a37b458

Re: Fish shell

#184

Earlier quoted context omitted.

For crying out loud... another instance of the GNOME team's insistence that they know better than their users, no doubt.

I was just thinking about how no one even pretends GNOME Shell is a serious contender any more. Sad that they've squandered their installed base so thoroughly.

Been using Linux since 1998. GNOME 3 and GNOME Shell have been my favorite DE since then.

Re: Fish shell

#185
post #176

Earlier quoted context omitted.

Well, "ridiculous_fish", the guy who sort of revived the fish shell is an engineer on the AppKit team at Apple: http://ridiculousfish.com I remember installing and using fish 4 or 5 years ago; it was not a great experience -- but after he "took over", I switched and couldn't be happier with fish.

Interesting! My impression was that Apple engineers were prohibited from building anything outside of work.

According to Wikipedia[0], fish was originally created by Axel Liljencrantz in 2005. The commit history from GitHub does go back that far (I imagine it was imported somehow), so I assume it's complete. The first commit from ridiculous_fish is in 2011.

So if there is such a policy at Apple, I would expect that it doesn't prohibit contributing to already-public projects.

[0] http://en.wikipedia.org/wiki/Friendly_interactive_shell

Re: Fish shell

#186
post #167

Earlier quoted context omitted.

There's just one scenario: a completely absent #! line. It's an easy fix, just add the line, otherwise 0755 scripts with no #! do execute using the current shell.

That doesn't work for me (in Fish). > cat foo echo wat > ./foo Failed to execute process './foo'. Reason: exec: Exec format error The file './foo' is marked as an executable but could not be run by the operating system. It does however work in Bash. So this appears to be a bash-ism, rather than an OS feature.

Ah, bummer. I tested in csh too but not fish.

Re: Fish shell

#187
post #143

Earlier quoted context omitted.

> One construct in bash is absolutely super: process substitution. You can read the output of a program as if it were a file with the construct: Actually had to look that one up[1] -- unfortunately you're right, it's not posix (I don't think I would've tried it in a [ed: non-interactive] script, but I agree it is very nice). I wonder if you could make a function as a work-around, something like: r() { #r(first some a…

Apparantly it's built-in as psub for the https://news.ycombinator.com/item?id=9569730 ), not sure about >()

Indeed. Came across this:

http://arstechnica.com/information-technology/2005/12/linux-...

I hadn't really thought about that echo'ing the filename might be useful, but this is pretty equivalent to how things work in bash -- with "diff <(some) <(other)", diff gets two temporary file-handles to two fifos -- that are later cleaned up by the shell. As most good ideas, obvious when you think about it :-)

Re: Fish shell

#188

I've been a Linux command line (bash) user for 20+ years now and I must say, I would really consider switching to this. I haven't even started to dig into the features yet, but the filename and parameter completion alone is enough to stop me from pulling my hair out. Filenames are getting very long w/ so many special characters, this is great. I also like the idea of having a web based config. I really won't miss wre…

I've been using Unix (and mainly Linux) for 20+ years as well. First using bash, then zsh the last couple of years and I recently switched to fish. The switch was fairly effortless and it took maybe 2 days to not even notice the differences anymore. I do have to look up some things now and then but overall it has been an improvement. What I like about fish shell is the same why I use the i3 tiling window manager. It…

how long have you been using the i3 tiling window manager?
Post reply on HN