You no longer need a file before you can mount anything. Until now, trying
airfsat all meant opening an editor, writing asources.txt, saving it in the right place, and only then mounting. That is a lot of ceremony to answer "what does this thing actually do?" β so now you can say what your layers are on the command line and be looking at the result a second later.
- β‘
airfs mount -s, once per layer.airfs mount --target ~/scratch-ws -s ~/ai/personal -s ~/ai/projectcreates the target, writes itssources.txt, and serves the view. The order you pass the flags in is the precedence order, most general first β same rule as the file, because it is the file. - βοΈ What you typed is what gets written.
~/ai/personalstays~/ai/personalin the file instead of being frozen into/home/you/..., so the configuration you end up with is one you would have written by hand and can keep editing that way. - π A typo cannot cost you your configuration.
-sreplaces the file whole rather than appending to it β but the new list has to resolve first. Name a directory that is not there and you get exit2and the configuration you already had, untouched.
It replaces, it does not add. π₯ Every layer you want has to be on the command line; whatever the file said before, comments and ordering included, is gone, and there is no backup. That is deliberate β a flag that appended would build a precedence order nobody wrote β but point it at a workspace you care about only once you have read Declaring layers.