We already read ignore files from other ltx2any daemons which already exist at startup. Already running daemons, however, don't update themselves with new ignore files, causing the older process to trigger rebuilds whenever the newer one rebuilds.
This is only a problem if two daemons run in the same directory, but still.
I see two options:
Create a second listen instance that watches for ignore files and updates the main listener as necessary.
Check for new ignore files before a re-run.
The second seems simpler and sufficient.
Note: What about a daemon that runs in a subfolder of another project? It won't pick up any dynamic file changes from the "outer" daemon, obviously, but the outer one can't find the inner one's ignore file. Should we watch for such or just have users which such setups deal with it?
We already read ignore files from other ltx2any daemons which already exist at startup. Already running daemons, however, don't update themselves with new ignore files, causing the older process to trigger rebuilds whenever the newer one rebuilds.
This is only a problem if two daemons run in the same directory, but still.
I see two options:
listen
instance that watches for ignore files and updates the main listener as necessary.The second seems simpler and sufficient.
Note: What about a daemon that runs in a subfolder of another project? It won't pick up any dynamic file changes from the "outer" daemon, obviously, but the outer one can't find the inner one's ignore file. Should we watch for such or just have users which such setups deal with it?