Who are these for? People who use the terminal but don't like running shell commands?
OK sorry for throwing shade. If you use one of these, honestly, what features do you use that make it worthwhile?
Who are these for? People who use the terminal but don't like running shell commands?
OK sorry for throwing shade. If you use one of these, honestly, what features do you use that make it worthwhile?
I still kinda don't see the point. Like, typing cd /usr/share/xsessions is not that much slower than j xsessions or however it would work. Also, how does it actually work? What if I visit both $HOME/backgrounds and /usr/share/backgrounds very often?
It's for when you have really nested directories. It happens especially when you're working in a file space used by others. I used to have a folder I would often reach called /media/nas/documents/personal/school/foo/bar/foobar2001/projectA
I ended up going back to that project so many times, I could just do
j projectAand get there from anywhere. "Why not use a symlink?" I hear you say. Well it's because I often have to go to projectB or another which was in another really nested dir. Or I needed to jump to another directory which was equally as nested, and only had to use it frequently for like a week or so. Making and deleting symlinks all the time wasn't practical. Not to mention some software doesn't properly follow symlinksWhat I usually do for that sort of thing is define some variables that go to my most visited.
Aliases? That could work quite well imo, and I have some to launch my most frequently opened config files, such as my qtile config
alias qtile-conf="nvim ~/.config/qtile/config.py"