On Mon, Oct 11, 2021 at 11:25:13PM -0500, Jacob Bachmeyer wrote: > Patrice Dumas wrote: > > Actually it was probably simply an oversight. Note that I have kept the > > function names in other warning messages, as either it is useful to have > > the function name as the user should have used the function or the > > message should not actually happen, it is more like a bug. I am not > > 100% sure on the second case, but these messages are not supposed to > > happen in normal cases. > > What about making the message unique? "unknown variable set on command line: > OPEN_CODE_QUOTE"?
I used "unknown variable from command line: OPEN_CODE_QUOTE". I am not an english native speaker, though. Should I replace with "unknown variable set on command line"? -- Pat
