-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Should <dir> in "autojump --add <dir>" be an absolute path? #45
Comments
Hi, short answer is "yes". According to upstream |
Aha, i knew i was missing something - i just installed it via scoop and was severely confused and left only with a single autojump.exe binary. |
I was looking for something cross-plat (windows, macos, linux) that could work in bash, zsh and windows-powershell.
I had to write the
j
script myself in powershell (because j.bat only works in CMD). I had to hook intocd
(set-location),pushd
(Push-Location) andpopd
(Pop-Location), such that the tool could learn how I navigate the filesystem. I have chosen to convert any new location to an absolute path before calling--add
sub-command, in order for..
,../..
and other relative paths to have universal meaning (at least at my windows pc).I wanted to avoid someting like this (because relative paths would loose all meaning in the dynamic config because the tool doesn't know relative to what folder!)
Is this how it should be done?
The text was updated successfully, but these errors were encountered: