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

Clarion

by fushnisoft ST2/ST3

SublimeText package for Clarion

Details

Installs

  • Total 275
  • Win 224
  • OS X 26
  • Linux 25
Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11 May 10
Windows 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 0 0 0 0 0 0 0 0 0 0 0
OS X 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 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

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