Escaping hyphens and apostrophes and other about jump HOT 8 CLOSED

I'm pretty sure the directory names with apostrophes and the like are handled fine in Jump's JSON database, however, these could be a problem in the shell integrations. What shell are you using?

from jump.

I'm using bash -- but I found out something more about what's the issue here. Jumping to directories with hyphens does actually work when I don't tab-complete the target directory. So if I just type "j search" I do land at the right target even if a parent directory has hyphens. I'd gotten used to tab completing the searches in order to see the full path, and when I do that it doesn't work. I just tested with zsh but I've probably not got it set up right because tab completion didn't do anything there. Completion without tab worked with hyphens in zsh too as for bash.

So I guess the question is if jumping to a directory after tab completion a feature in jump or something bash specific?

from jump.

It could be the missing escaping when generating the completion hints. Can you try changing this line to:

jump hint "$term"

You don't need to compile jump, but replace the integration in you bashrc from eval "$(jump shell bash)" to the bash script lines inside of the ` block.

from jump.

My .bashrc contained the lines
eval "$(jump shell)" (from the front page instructions)
When I first tried to change this to
eval "$(jump shell bash)"
I got the same behavior as before.
Further changing this line to
eval "$(jump hint $term)"
does not evaluate well, and I get an error when starting bash. Perhaps I didn't write what you intended?

from jump.

I'll test it locally and put a build for you to test as well. It will be easier than writing the integration script manually.

from jump.

I have tested it locally and have a fix for this. Will release a new version of Jump tomorrow with it.

from jump.

Thanks! Will test when out :)

from jump.

Thank you for bringing this up! This was a security issue as well. If a cleverly named directory existed in you jump database, going to the directory by following the autocompletion could have been dangerous! You can spawn shell commands with the directory name and that's not good. Again, thanks for the notice.

The autocompletion should be fixed for such cases in the new release, 0.40.0. Read the release notes for more details. I have attached a jump_osx OSX binary, because it will take a while for brew to pick up the new release.

from jump.