Apparently I may have edited settings.json by hand, and omitted a comma just *before* the leoInteg settings.
That was the cause of the double-underlined setting. vs code itself lead me to the cause. There was a dialog that said, in part, "no quick fix possible", but another message, I don't remember which, even though I just saw it, said "missing comma". And at last I understood :-) Let me see if I can recreate the problem. I have just removed the required comma. Let's see what happens when I reload vs code...Oh, now I *do *remember. I had run leoInteg, then ran Open Leo Settings. I get (and got) this error: Command 'Leo: Open Settings' resulted in an error (command 'leointeg.showSettingsPage' not found) So then I did "Preferences: open settings". Bingo. I get the same message as before. And now I see how I got the last message: I hovered over the double underline! This gives a popup with really great diagnostics. It has three panes, whose texts I'll have to copy here by hand: - Specifies the command to start python (defaults to py3 on Windows and python3 otherwise) I remember this from the leoInteg settings page. - Expected comma (jsonc 514) Probably comes from vs code's json parser. - Peek Problem (Alt+F8) No quick fixes available. The first part is in blue, indicating a link. Clicking the link takes me to the supposedly offending line, but the real problem is the missing comma at the end of the previous line. *Important*: it's a bit tricky to bring up the dialog I have just described. Sometimes I get a smaller dialog (almost certainly from leoInteg) that merely says: "Specify who to allow session invitations from." In other words, I was a bit lucky to get the more informative dialog :-) *Summary* A missing comma in a previous line was the cause of the error indication (error indication) in the next line of settings.json. A slightly hard-to-raise dialog provided detailed, helpful diagnostics. Adding the comma fixed the problem. I am going into all the great detail mainly for reference. Experienced vs coders will likely not have been confused, but this newbie certainly was. This is just one example of the learning code involved in learning a new IDE. Imo, vs code seems worth the effort. Indeed, the diagnostics are impressing, if initially a bit confusing. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/1e5d4d23-6959-4943-8b78-564e21732522o%40googlegroups.com.
