The script editor
The Script tab is an editor that knows the engine. What it offers comes from an index verlet builds from the manual of your engine version, so it covers every command, style and keyword the manual does.
Completion
Section titled “Completion”Opens as you type and with Ctrl+Space:
- Commands at the start of a line, with a short description.
- Styles after a command that takes one:
fix 2 all nlistsnve,nvt,nptand the rest. - Keywords after a style, with their values as placeholders to tab through and what each means.
- Alternatives a command’s syntax lists, such as
lj,realormetalafterunits. - Names defined earlier in the script, where a command refers to one: groups, and
v_,c_,f_and${}references.
Continued lines are read as one command. Nothing is offered inside comments.
- Hover a command or style for its summary and syntax, with links to the page in the app and to the manual online.
- F1 or Ctrl+I (⌘I on macOS) opens the page of the command under the cursor in the Help tab next to Problems and Output: syntax, parameters, keywords, description, examples.
Your executable, not the manual’s
Section titled “Your executable, not the manual’s”An executable only has the styles of the packages it was built with. verlet records them when it scans a machine, and the editor uses the default environment’s executable: a style that binary lacks is still offered, marked “not in” followed by the executable’s name, and sorted last. A check catches the same thing, later.
Before the index is ready
Section titled “Before the index is ready”The index is built in the background after the first start. Until then the editor falls back to its built-in lists of commands and styles, and the Help tab says so.