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

Clarion

by fushnisoft ST2/ST3

SublimeText package for Clarion

Details

Installs

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

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