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

Clarion

by fushnisoft ALL

SublimeText package for Clarion

Details

Installs

  • Total 469
  • Win 381
  • Mac 47
  • Linux 41
Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5
Windows 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 1 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 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