This is something I wish I implemented as a hobby project but never found the time to do it. Congrats! I see you implement a directory as a file containing a b-tree. Could you provide more info on this?
Being able to type something like "z ab g f" to reach a fairly deeply nested directory is almost akin to magic. I absolutely hate cd'ing everywhere, and often I'm cd'ing between the same couple of directories for a number of projects, so I feel like it helps retain my sanity. I've also written scripts to take advantage of it, such as a cp clone that doesn't require an immediate target. So I can cp a file (or number of files, or a directory), z-jump to a different directory and paste it there instead of laboriously typing out all the directory paths. I love it.
What do you mean by "unix -r custom"? It's not like "-r" is some kind of standard, and many commands or programs have other ideas.
For example, GNU cp uses -r or -R for recursive copy, but OpenBSD cp only uses -R. ls uses -R only (-r is listing in reverse order). scp uses -r only (-R is remote copy). rm allows both -r and -R.
But then, commands like mv or find don't support anything like -r or -R, they implicitly affect the whole directory structure. Bash has * (with shopt -s globstar) for globbing with subdirectories. Make doesn't support any concept of recursive subdirectory traversal.
There. I did just learn it without following a tutorial or somethin. It's so simple, easy to remember. It's even faster to write that -R or -r.
reply