stricter jumps

[aeosynth]

if i enter a path that doesn't exist in the jump db, i'd rather not jump, than jump to a seemingly random directory.

eg j xyz -> jump to /home/james/dl ???

[gsamokovarov]

I'll look into this, thanks!

[orefalo]

same issue, it jumps to a random location

[rkfg]

It's a pretty important issue that harms the program performance, I think I've never seen it in autojump. For example, I have two directories in scores.json:

• /mnt/2Tb/stable-diffusion-docker with score 122 (I often use it)
• /home/rkfg/soft/svn-soft/gddr6-core-junction-vram-temps with score 6 (it's a new directory)

When I type j ddr I end up in the first directory even though it's a fuzzy match with multiple characters between d, d, and r. In the second case the whole word is there but it doesn't match at all, even after a few j without arguments. I get other high score directories with these three letters spread along the name. Sure, I can quickly get to the second directory if I type j gddr but only because there are no other known random directories with these letters in this order.

I think the fuzzy match is way too lax and needs improvements or at least a configuration option to turn it off or make it stricter. Levenshtein distance looks like a good candidate for a limiting function.

[gsamokovarov]

That's an interesting observation.

For now, you can use a feature I had for a while but hadn't documented until recently. It's called pins – you can pin a specific directory to a search term. It's not fixing the problem, but it may make your jump life better.

See jump --help or the readme for more details about the pins.