Search Results for "double-entry"

Hover over any piece of code; if an underline appears, you can press Ctrl to get a tooltip with function/class signature, module documentation or any other piece of information that the language server provides. Critical errors have red underline, warnings are orange, etc. Hover over the underlined code to see a more detailed message. Use the context menu entry, or Alt + 🖱️ to jump to definitions/references (you can change it to Ctrl/⌘ in settings); use Alt + o to jump back. Place your cursor on a variable, function, etc and all the usages will be highlighted. When a kernel is available the suggestions from the kernel (such as keys of a dict and columns of a DataFrame) are merged with the suggestions from the Language Server (in notebook). ...

...Ansible keywords, module names and module options, as well as standard YAML elements are recognized and highlighted distinctly. Jinja expressions are supported too, also those in Ansible conditionals (when, failed_when, changed_when, check_mode), which are not placed in double curly braces. While you type, the syntax of your Ansible scripts is verified and any feedback is provided instantaneously. On opening and saving a document, ansible-lint is executed in the background and any findings are presented as errors.