On Sat, 6 Apr 2024 at 22:05, Paul Eggert <egg...@cs.ucla.edu> wrote: > Thanks for the suggestion. Although I didn't go to the trouble of > writing code to generate the multiline diagnostic you suggested, it's > easy to change "possibly undefined macro" (which doesn't cover the > situation you mentioned) to the slightly less confusing "undefined or > overquoted macro". Since the diagnostic can be caused by misspelled > macro names, which do occur, I thought it wise to retain a mention of > that in the diagnostic. I installed the attached patch.
That's great, thanks! -- https://rrt.sc3d.org
