Jump integrates with your shell and learns about your navigational habits by keeping track of the directories you visit. It gives you the most visited directory for the shortest search term you type.
Jump comes in packages for the following platforms.
Jump needs to be integrated with the shell. For
zsh, the the line
below in needs to be in
eval "$(jump shell)"
For fish shell, put the line below needs to be in
status --is-interactive; and source (jump shell fish | psub)
Once integrated, jump will automatically monitor directory changes and start building an internal database.
j is not my favourite letter!
This is fine, you can bind jump to
z, with this:
eval "$(jump shell --bind=z)"
And now, you can use
z dir and it would just work! This is only
an example, you can bind it to anything. If you are one of those persons that
likes to type a lot with their fingers, you can do:
eval "$(jump shell --bind=goto)"
goto dir becomes a thing. The possibilities are endless!
Once integrated, jump introduces the j helper. It accepts only search terms and as a design goal there are no arguments to j. Whatever you give it, it's treated as search term.
Jump uses fuzzy matching to find the desired directory to jump to. This means that your search terms are patterns that match the desired directory approximately rather than exactly. Typing 2 to 5 consecutive characters of the directory name is all that jump needs to find it.
The default search behavior of jump is to fuzzy match the directory name of a score. The match is case insenstive.
If you visit the directory
you can jump to it by:
$ j wc # or... $ j webc # or... $ j console # or... $ j b-c # or...
Using jump is all about saving key strokes. However, if you made the effort to type a directory base name exactly, jump will try to find the exact match, rather than fuzzy search.
$ j web-console $ pwd /Users/genadi/Development/rails/web-console
Given the following directories:
j site matches only the base names of the directories. The base name
website, the same as the
other absolute path above. The jump above will land on the most scrored path,
which is the
society one, however what if we wanted to land on the
$ j ch site $ pwd /Users/genadi/Development/chaos/website
This instructs jump to look for a
site match inside that is preceded by a
ch match in the parent directory. The search is normalized only on the last
two parts of the target paths. This will ensure a better match, because of the
shorter path to fuzzy match on.
There are no depth limitations though and a jump to
/Users/genadi/Development/society/website can look like:
$ j dev soc web $ pwd /Users/genadi/Development/society/website
In fact, every space passed to
j is converted to an OS separator. The last
search term can be expressed as:
$ j dev/soc/web $ pwd /Users/genadi/Development/society/website
Bad jumps happen. Somethimes we're looking for a directory the isn't the most scored one at the moment. Imagine the following jump database:
/Users/genadi/Development/society/website /Users/genadi/Development/chaos/website /Users/genadi/Development/hack/website
j web would lead to:
$ j web $ pwd /Users/genadi/Development/society/website
If we didn't expect this result, instead of another search term, typing j without any arguments will instruct jump to go the second best match.
$ j $ pwd /Users/genadi/Development/chaos/website
Case sensitive jump
To trigger a case-sensitive search, use a term that has a capital letter.
$ j Dev $ pwd /Users/genadi/Development
The jump will resolve to
/Users/genadi/Development even if there is
/Users/genadi/Development/dev-tools that scores better.
Is it like autojump or z?
Yes, it is! You can import your datafile from
$ jump import
This will try
z first then
autojump, so you can even combine all the
entries from both tools.
The command is safe to run on pre-existing jump database, because if an entry
exist in jump already, it won't be imported and it's score will remain
unchanged. You can be explicit and choose to import
$ jump import autojump $ jump import z