Live data from Hacker News

Fish shell 2.2

fishshell.com

41–50 of 73 posts

Re: Fish shell 2.2

#42
post #38

Earlier quoted context omitted.

I think the downvotes are because you completely failed to grasp what Fish shell is. It is a newer more modern shell than bash not some type of retro 90's toy.

I think you're failing to get his reference. The title of the fish shell home page: "Finally, a command line shell for the 90s".

Yes I got the reference very well thank you. I fear that he did not.

Re: Fish shell 2.2

#44
post #14
post #13

Earlier quoted context omitted.

But do you need to? Just write it for bash and run it from fish the same way you run python scripts from bash.

It seems a lot of people don't realize `bash`, `sh`, `zsh` etc... are executable binaries just like any other on the system, and that you don't need to be logged in to a bash shell to run bash scripts.

This isn't the case for sourced scripts. Running a script in bash from fish that changes your current directory will do one of two things: It'll move you to that directory but inside of a bash shell, or it will move you to that directory in a bash shell, bash's cd will return, and you'll be in the same directory as before, still in the fish shell.

Re: Fish shell 2.2

#47
post #41

Earlier quoted context omitted.

What's the issue with the web server?

Some people might think that it might represent an extra volume of code for bugs to creep in - and hence security issues?

It just makes Fish feel desktopy, a toy shell, and not something serious. Ask the vim crowd that even in 2015 uses vim in the terminal, even on desktops. You just don't do the things Fish does, it's that simple. Make the web server an addon and keep everybody happy!

Re: Fish shell 2.2

#48
post #39
post #36

Earlier quoted context omitted.

The built-in web server is optional anyway.

Via configuration, but it's bundled into the code. I'd rather have the web server as an optional install.

I don't think it automatically starts up. You have to run fish-config to start it yes?

    $ fish_config
    Web config started at 'file:///Users/bjorn/.cache/fish/web_config-6VIDFM.html'. Hit enter to stop.
    ::1 - - [12/Jul/2015 11:13:31] code 403, message Forbidden
When I kill this and refresh the config in the browser doesn't load anymore. So I don't see the problem.

Re: Fish shell 2.2

#49
post #9

Awesome! Remove the built-in web server and count me in!

The web server is only active if you run the command fish_config. When you run this command, if finds the next available port, starting at localhost:8000 and opens a web browser pointing to that port.

Once in the web interface, you can click around to implement some pre-supplied recipies to your fish configuration.

If you hit ctrl-c, the fish_config program exits and stops listening on the port.

It's something you either run or you don't.

Re: Fish shell 2.2

#50
post #47

Earlier quoted context omitted.

Some people might think that it might represent an extra volume of code for bugs to creep in - and hence security issues?

It just makes Fish feel desktopy, a toy shell, and not something serious. Ask the vim crowd that even in 2015 uses vim in the terminal, even on desktops. You just don't do the things Fish does, it's that simple. Make the web server an addon and keep everybody happy!

You want the web server to be an add-on so you can feel more hardcore?
Post reply on HN