On Fri, 13 Dec 2024, David Kastrup wrote: > Creative quoting games. I am out.
I wrote this: But one might well also ask, if there are useless properties with no effect, then why are there useless properties with no effect, and isn't the fact that such properties exist a much bigger problem than whether they should be listed in the document? You quoted and responded to just half of that, cutting the quote off in the middle of the sentence, and then YOU proceeded to accuse ME of "Creative quoting games." That's not a good look. But if anyone else is still interested in the original question about documentation, it seems quite reasonable to me that grob documentation could list all the properties that have an effect on each grob, including inherited properties, and not list (or not list in the same place) any inherited properties that don't have an effect. I'm not so interested in how many, if any, properties with no effect there might be. Requiring readers to trace back through the hierarchy to look at all interfaces supported by a grob in order to see which properties can be used, does seem like it makes the documentation harder to use. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before tribes. https://ansuz.sooke.bc.ca/
