Richard Lawrence
Richard Lawrence
What you have described is exactly an integration test. I already have those. They are also important.
I want to combine multiple fuse filesystems to avoid lots of useless context switching. Example. Three fuse filesystems. Lots of useless context switching. ```mermaid flowchart TD A[Kernel] -->|Request| B(Branch FS)...
If i only wanted to be able to internally interface with my own filesystems, then that would be acceptable. I was hoping I could also compose fuser filesystems from other...
These are good suggestions I will look into.
After some thinking, I have realized that while it is theoretically possible to achieve my goal just by adding some pub statements to the fuser crate, the resulting code on...
I did a re-write in my fork so that the ReplyX are traits instead of structs, and Reply is a struct instead of a trait. ``` pub struct Reply {...
I have abandoned this strategy.
I usually do this by having multiple instances of unionfs-fuse running. I have a feeling it's not optimal, but it works great. they don't seem to mind if you start...
.clineignore doesn't even hide the files in subdirectories, it just adds the lock emoji. ``` # Current Working Directory ... 🔒 references/ 🔒 references/bubblewrap/ 🔒 references/bubblewrap/.dir-locals.el ... (File list truncated....
I created a solution that, while not quite exactly what you asked for, pretty much gives you what you wanted: a unified error function. #335