[keedot]

I have several bash functions that need to be sourced to be included. For instance, I use `cdc` to change to my code directory, where I keep my source for projects I am working on. If I type `cdc name` it changes it to my projects source directory, save me a lot of keystrokes in a day as I have many that I flip between. This sourcing of a function is required due to the way cd is handled, and in it's current form, not directly usable under fish. Maybe it's easier under fish, but fish isn't backwards compatible to make this work out of the box.

[techwizrd]

Have you tried Bashmarks[0] for Bash? I have also written a compatible version for Fish called Fishmarks[1].

0: https://github.com/huyng/bashmarks 1: https://github.com/techwizrd/fishmarks

[gry]

Alternatively, you may want to look into z.

    https://github.com/rupa/z (bash, zsh)
    https://github.com/sjl/z-fish

[StavrosK]

I swear by z.

[micampe]

You want $CDPATH for that in Bash.

[nmcfarl]

CDPATH is not a very good bookmarking system, as you can't bookmark several directories that have the same name, and you are forced to bookmark all the siblings of the item you wish to bookmark, which can be a problem with flat hierarchies. So if bookmarking directories is the goal, CDPATH might not be the best way. And one off bookmarking functions are easy to write.

Admittedly for the description given, it does sound like CDPATH would work. But I'm going to assume there's a reason, and functions that change the current working directory are the perfect example of functions that can not be run in a subshell, so will have to be rewritten to fish, which is what the author was providing.

[keedot]

I simplified the example, cdc does more than just a change the directory. `cdc -t name` changes to the directory and attaches to the tmux session of the same name if it exists, and if it doesn't, sets up my tmux layout for development.

[charles2013]

whilst reading your above comment i wondered why you chose not to use environment variables instead. e.g.:

  $ export cdc_stuff='/Users/me/src/project_stuff'
  $ cd $cdc_stuff

however, now it's clear.

in the event you're looking for alternatives, perhaps porting your code to (e.g.) ruby could work.

just in case, here's the isbn number of a book called, 'Build Awesome Command-Line Applications in Ruby 2,' from the pragmatic bookshelf: 978-1-93778-575-8

[micampe]

Ok. I didn't know about cdc.