The pkill fishd is there to kill off older versions of fishd so you'll be
running the latest and greatest.
On of the first things fish does is see if fishd is running and if not it
starts it up. OS X uses a BSD
based ps, so you need to use bsd ps options( 'augx)' to see everything on
the system.
If you really don't want fishd running, then you probably don't want to be
using fish.
I wouldn't go that far. IIUC all fishd is responsible for is universal
variables. fish has lots of other desirable features, and you won't get
cleaner syntax by adding onto bash.
Hi Booker,
I know all of this, but on my machine I simply don’t have fishd installed, nor
running:
➜ ~ echo $FISH_VERSION
2.1.1-1089-g0ea80a3
➜ ~ ps agux | grep fishd
a10022 34066 0.0 0.0 2443012704 s001 S+ 11:13AM 0:00.00
grep fishd
➜ ~ which fishd
➜ ~ find /usr/local
On trunk, universal variables no longer require fishd (!) and so it doesn't get
launched. This was first enabled with commit 20d7a142, and will be the default
behavior in the next release.
_fish
On Nov 17, 2014, at 9:00 PM, Diego Zamboni di...@zzamboni.org wrote:
Hi Booker,
I know all
On Sun, 16 Nov 2014, Mario Castelán Castro wrote:
Is it possible to use fish without fishd even if it loses some
functionality?. Specifically, is it possible to configure fish so as
to not to start fishd and not to print an error message about lacking
fishd?.
On IRC, you mentioned that you
I see. Thanks for the clarification!
—Diego
On Nov 17, 2014, at 11:20 PM, ridiculous_fish corydo...@ridiculousfish.com
wrote:
On trunk, universal variables no longer require fishd (!) and so it doesn't
get launched. This was first enabled with commit 20d7a142, and will be the
default
