Syntax & Error Highlighting
Syntax Highlighting differentiate between sub-commands, options/flags, arguments, and variables. Error Highlighting automatically underlines any invalid commands with a dashed red underline.
Last updated
Was this helpful?
Syntax Highlighting differentiate between sub-commands, options/flags, arguments, and variables. Error Highlighting automatically underlines any invalid commands with a dashed red underline.
Last updated
Was this helpful?
Warp supports Syntax Highlighting in the Input Editor. It colors each part of a command to help differentiate between sub-commands, options/flags, arguments, and variables.
Newly installed apps or newly created aliases will not trigger syntax highlighting until you open a new Warp session (new window, tab, or pane), even if you source the RC files in the current session.
When Syntax Highlighting is enabled, Warp's Input Editor automatically recognizes each part of the command as you type it into the Input Editor, and syntactically highlight them.
Syntax highlighting is enabled by default, to toggle it:
Through the Command Palette, search for the "Syntax Highlighting" option and click it (or press enter) to enable/disable.
Through Settings > Features > Editor , toggle "Syntax highlighting for commands"
Warp highlights errors in commands that are typed within the Input Editor e.g. if the binary for the command you've typed does not exist.
Newly installed apps or newly created aliases will trigger error underlining until you open a new Warp session (new window, tab, or pane), even if you source the RC files in the current session.
When Error Underlining is enabled, Warp automatically underlines any invalid commands with a dashed red underline.
Error underlining is enabled by default, to toggle it:
Through the Command Palette, search for the "Syntax Highlighting" option and click it (or press enter) to enable/disable.
Through Settings > Features > Editor , toggle "Error underlining for commands"