I'm not very familiar with SemanticUI - what does .overrides do?

right now, it's tracking what file the result is compiled from, so yeah, other files being touched won't trigger a re-render

definitely open to making that more robust, though

The other files are basically customizing the generated css...so abstracting would be to trigger a task based on when not just one but multiple files on the fileset change

hmm, well

there's still probably a way to do what you want -

perun will re-render a file if one of its :input-paths changes, like here: https://github.com/hashobject/perun/blob/master/src/io/perun.clj#L298

lessc uses that function to generate output paths, so for a quick fix, you could just wrap that function and add whatever you want to each entry's :input-paths, in your own lessc task, implemented almost exactly like perun's

for a longer fix, perhaps we could figure out a way for the end-user of of lessc to modify :input-paths, since for this kind of thing, it's not obvious to me how perun would know what files to watch

I like that longer fix idea

Yes I think the longer term idea is best. A regex to each task could specify what can retrigger a change or something...