My workflow for getting around is just to type "z <fragment of directory name>" and I almost always end up where I want. If I just want to edit a file, not a project, I do vim `f <filename fragment>` and likewise get the file I want typically.
The readme makes it pretty clear how awesome it is and I've stuck with it after using autojump, z, and others.
I don't wanna sound negative, but just being realistic.
I don't rely on bookmarks primarily. I rely on "most frequently visited gets auto-completed first" and fuzzy search of Chrome Omnibox. If I do bookmark something, it's to indicate to the algorithm "I care about this, make it easier to fuzzy find it later".
But it's a good step in the right direction, good job!
Edit: From the description, it sounds like autojump does something close.
It also has lots of other features, like tab completion that tells you what the options of commands do. So reading the manpages or typing -h is generally not needed.
If you do try it, also try one of the themes of oh-my-fish, most of them have a git thing that lets you know if you have uncommitted stuff and on what branch you are.
Also, the built-in pushd and popd commands are enough sometimes.
I came here to say this. A small wrapper around these commands would make for a sufficient script.
One thing I'd like to add, if you're like me and don't want to install too much "extra" stuff on your machines: Bash has native commands called pushd and popd. They work as a stack, pushd will push the current directory onto the stack and jump to the new target, then you're free to move around, do whatever you want and then call popd to pop the latest directory from the stack.
I find these very useful, especially if I'm on a machine without additional installed software and just want to do my thing effortlessly.
I'm addicted to one/two-letter aliases, and between that and ZSH completion (https://github.com/akerl/dotfiles/blob/master/.completions/_...), the mark functions get me super-simple bookmarks
I also wish people would stop providing "curl this into .bashrc" as the primarily installation method. That's a really bad habit to get into, especially with a file like .bashrc. It's a bit less risky than piping the curl into bash, but still not a great plan.
pwd > /tmp/md_tmp
cd `cat /tmp/md_tmp`
Edit: I see that your script uses links, I'll check this out.
alias <name>='cd path/to/<name>'
Then you can just type:
You can even set up an alias to add a new alias ->
alias ea='vim ~/bash/alias'
In addition to the bookmarking style capabilities other people have already mentioned it also includes integration with the locate database, the mac spotlight/mds database, and the plain old find command. It can switch to a sub directory containing a particular file. It also supports bash completion.
I like a solution that goes where ever your dotfiles go, instead of having to install a fuzzy search on each system.
Metis will list all of your currently saved Metis aliases as well, just by typing "metis". You can also tell Metis which dotfile you want to save your aliases.
ln -s ~/super/long/nested/directory/name ~/short
ln -s ~/super/long/nested/directory/name ~/l/short
alias proj="cd /this/that/foo/projects/myproject/ && source .hsenv/bin/activate"
batch scripts in windows behave like scripts on unix do when you source them. That means that you can write a batch script called "foo.bat" with the contents of "cd \whatever\directory\you\please" and it will change your current directory when run.
From there, it would not be difficult to write a batch script that in turn wrote batch scripts like "foo.bat" above.
With bash, you would have to create functions or aliases to get the same effect.