Explain errors in plain English
Confusing error messages get rewritten into a sentence that says what actually went wrong.
When you would want it
Compiler messages are written for people who already know the compiler. Most of the time the real meaning is simple and the wording is not.
Where to find it
- All Features → Explain errors in plain English
- Settings → adcode.editing.plainEnglishErrors
What you get out of it
- You get the meaning immediately, not after decoding jargon.
- The original message is never hidden, so web searches and issue reports still work.
- It applies to every diagnostic - errors, warnings, and lint output alike.
How to use it, step by step
- Write code that produces a compiler or linter error as usual.
- Read the first line under the squiggle - that is the plain-English rewrite.
- Hover the error, or check the Problems panel, to see the compiler's exact original wording underneath.
- Search for the original wording when you need the deeper explanation the compiler links to.
Why this beats the usual way
Other editors show you the compiler's raw output and leave the translating to a search engine. ADCode does the translation in place, keeps the source text for when precision matters, and never lets the rewrite replace the truth - it sits above it.
Find it in Universal Search
Explain errors in plain English · Editing