• any caller can create it's own source

• it should have a name so we do not get linker issues (meaning it should be dynamic)

• the caller can specify at which position to insert his source in the sources cascade (by name, e.g. before "project")

• the cascade of build sources could be configurable (maybe with some kind of sanity check)

• it would be cool to see a graphic display of the cascade to find the place where a value comes from (for debugging, for users who are stuck understanding why they don't get the expected value). This could maybe be a dynamically generated SVG image

Well, given that some Geany contributors were saying it is already waaay too complicated and were pushing back any increase in features, good luck with the total re-write 😁

Perhaps it would be better for you to just reimplement it for your purposes and maybe at some point in the future you can make a simpler PR to disable Geanys features so only yours are available, if you think having both will confuse users.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.