Will hopefully inspect and maybe even try "soon" but am re-building my development machine after an SSD death, and then will have to catch up the lost time first, but a couple of comments.

As said elsewhere, (many times over years) these days the distinction of programming vs script vs AOT vs JIT vs interpretor are meaningless for the language, they apply to the implementation, and in some cases there are multiple implementations, so those categories in the menu are meaningless for the filetype.

agree the menu should be hard coded. Some automajik method that totally reorganised the menu just because a user tried a custom filetype would be very annoying.
As the structure member is not individually documented its not in the API so any plugin that uses them is its own fault, and so long as the new member is the same size it won't change the ABI either and so no problems.
agree
agree
personally I don't care about "source file" etc. I only care about the filetype name. Geany does not edit anything but (UTF-8) text and it won't ever edit anything but a "file" so never eg "C++ object file" so why say "C++ source file". Lets see if anyone else who cares can make a cogent argument for keeping the extra text.
agree

Speculatively, perhaps there should be an "Other" for non-ASCII names, maybe the new language is named "Åland" for example.

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