ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Clarion

by fushnisoft ALL

SublimeText package for Clarion

Details

Installs

  • Total 466
  • Win 379
  • Mac 46
  • Linux 41
Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7
Windows 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 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 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
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 1 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Discussion available on ClarionHub!

Read the announcment and join the discussion at ClarionHub

Installation - VSCode

Install the VSCode extention via the market place.

Either download it directly and install manually or from within VSCode as described on the Getting Started page.

Installation - SublimeText

via Package Control

This is the recommended installation method.

If you have Sublime Package Control, you should know what to do. read about it here.

After installing the package and restarting the editor:

  • Open the Command Pallete (ctrl+shift+P or cmd+shift+P).
  • Type “Install Package” and hit return.
  • Type “Clarion” and hit return.

CompileCW.cmd usage

Project->EditProject to open your .sublime-project and add the following, where you alter give the absolute path to YOUR .sln

"build_systems":
[
  {
      "name": "Clarion",

      //name your sublime-project the same as your .sln
       "cmd": [
                      "${packages}\\Clarion\\CompileCW.cmd",

                      // What to build, convention is the same folder and basename as this sublime-project file, but with a .sln instead
                    "${project/\\.sublime-project/\\.sln/}",
                      //or hard code the absolute path to the sln, for example; //   "c:\\HG\\TSI\\CW\\Est\\B47.sln",

                       // Build Configuration typcially Debug|Release
                         "Debug",
                        // "Release",

                        //CWRoot
                     "C:\\SV\\Clarion8",

                     //(Optional) CW_Ver, such as "8.0.9579" will default to current
                     ""
                 ],

      //Appropriate for MSBuild in general
      //uses perl style regex: (maybe this) http://www.cs.tut.fi/~jkorpela/perl/regexp.html
     "file_regex": "^\\s*(.*)\\(([0-9]*),([0-9]*)"

      //"working_dir": "${project_path}:${folder}}",
     //"shell" : true,

     //Documentation on build systems: see http://docs.sublimetext.info/en/latest/reference/build_systems.html
   }
]

Then you can use CTRL+B or F7 to compile You can double click on error lines to navigate to the bug