3 ms·
Am I understanding this right? This is basically just a command to call bash scripts that live in a certain directory? Why not just use: . path/to/ez_lisp.sh
by such_a_casual 11y ago
Am I understanding this right? This is basically just a command to call bash scripts that live in a certain directory? Why not just use:
. path/to/ez_lisp.sh
----------------------
or use an alias like:
desk() {
. path/to/$1
}
I'm a newb. So sorry if this is just over my head.
- semi-extrinsic 11y agoLooks like you're right. From TFA (in the Readme): "I have a hard time calling this a "workspace manager" with a straight face -- it's basically just a shell script that sources another shell script in a new shell."
- jobeirne 11y agoYes and no... the details are a little different, because we're using subshells and not sourcing scripts directly in the current process (cleanup is easier that way -- you just `exit`). But in effect, yeah, this is minor window dressing around executing an initializing shell script in a sandbox. I find the interface and the doc surfacing useful. In the nearterm I'm going to be working on supporting imports -- i.e., you `git clone` down a project that has a deskfile at its root, then you're able to import it (maybe as a fancy symlink) into your own deskfiles. That'd give you immediate, programmtic context for working on the project.