RISC OS Command Syntax
RISC OS Command file syntax colouring for SublimeText 3
Details
Installs
- Total 72
- Win 41
- Mac 21
- Linux 10
Apr 17 | Apr 16 | Apr 15 | Apr 14 | Apr 13 | Apr 12 | Apr 11 | Apr 10 | Apr 9 | Apr 8 | Apr 7 | Apr 6 | Apr 5 | Apr 4 | Apr 3 | Apr 2 | Apr 1 | Mar 31 | Mar 30 | Mar 29 | Mar 28 | Mar 27 | Mar 26 | Mar 25 | Mar 24 | Mar 23 | Mar 22 | Mar 21 | Mar 20 | Mar 19 | Mar 18 | Mar 17 | Mar 16 | Mar 15 | Mar 14 | Mar 13 | Mar 12 | Mar 11 | Mar 10 | Mar 9 | Mar 8 | Mar 7 | Mar 6 | Mar 5 | Mar 4 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Sublime Syntax highlighting for RISC OS Command files.
A Sublime syntax definition for RISC OS command files to enable syntax highlighting. This is suitable for use with Command, Obey, TaskExec, TaskObey and Desktop files.
Colouring
The syntax colouring recognises many of the standard commands, and a few of the common library and system commands. The processor is generally not context sensitive, so a sequence that looks like a command will be coloured as one.
The coloured features are:
- Comments, prefixed by | at the start of a line.
- Common commands from the standard RISC OS modules.
- System variables with
<
/>
delimiters. - GSTrans characters in the form
|
followed by a letter. - Strings delimited by
"
. - Filenames, where they are obviously anchored, are preceded by a variable, or are preceded by a filesystem name, or path name.
- A few special cases, like
*FX
,*TV
,*Key
which do not require a separating space, and the controls in*If
statements (Then
,Else
).
File recognition
RISC OS files commonly use the NFS encoding format of suffixing the filename with ,xxx
for the filetype. These are not supported by the Sublime Text extensions syntax, so it is recommended that the ApplySyntax package (or similar) be used to select the syntax mode.
The following configuration is suitable for use within ApplySyntax.sublime-settings
:
{
// RISCOS Specific commands file (Obey, TaskObey, Command, TaskExec, Desktop)
"syntax": "RISCOSCommand/RISCOSCommand",
"rules": [
{"file_path": ".*(\\\\|/)*,(ffe|feb|fd7|fd6|fea)$"},
]
},
Install manually
- Place the
RISCOSCommand.sublime-syntax
file inside the Sublime Text packages User folder (Preferences | Browse Packages...
) - Restart Sublime Text
Install with Package Control
- Install Package Control
- Run “Package Control: Install Package” command, find and install
RISCOSCommand
plugin. - Restart Sublime Text if necessary
License
This package is licensed under the MIT License.