I was reading an article about fish at
http://arstechnica.com/information-technology/2005/12/linux-20051218/2/
which has:
Most other Unix shells include built-in implementations of common
commands like echo, kill, printf, pwd, time, and test. These internal
implementations are usually slightly
Hello Greg,
These commands have been made builtins to improve performance. We still try
to avoid unnecessarily adding more builtins to fish, but these commands are
so frequently used in fish that it was best for convert them to builtins.
Refer to 'The law of responsiveness' section from fish
2014-10-09 19:10 GMT+02:00 Greg Reagle greg.rea...@umbc.edu:
I was reading an article about fish at
http://arstechnica.com/information-technology/2005/12/linux-20051218/2/
which has:
Most other Unix shells include built-in implementations of common
commands like echo, kill, printf, pwd,
I have fish (2.1.1) set as my default login shell now on my Ubuntu (14.04.1)
host.
Mostly it works fine, but when I ssh into the host to run a command, so fish
runs
non-interactively, I get a bunch of errors:
andrex@helium ~ ssh helium w
set_color: Could not set up terminal
set_color: Could not
On Thu, 9 Oct 2014, Andrew Schulman wrote:
I have fish (2.1.1) set as my default login shell now on my Ubuntu (14.04.1)
host.
Mostly it works fine, but when I ssh into the host to run a command, so fish
runs
non-interactively, I get a bunch of errors:
andrex@helium ~ ssh helium w
On Thu, 9 Oct 2014, Andrew Schulman wrote:
I have fish (2.1.1) set as my default login shell now on my Ubuntu
(14.04.1) host.
Mostly it works fine, but when I ssh into the host to run a command, so
fish runs
non-interactively, I get a bunch of errors:
andrex@helium ~ ssh helium w
