ITE - Integrated Toolset Environment

The goal is to create a Stable set of packages which can work together, leading your Sublime Text to be able to program/develop any language you ever need to.

Either its Stable or its Development version have been Stable for some time. Anyone interested in using it, can just follow the installation instructions at the Installation section.

Any interested in contributing, can just do so by creating a new issue with your new ideias or issues. You can check the issue tracker for a list of issues to be worked on. Note, there are some issues I already fixed, just forgot to close them yet.

Table of Contents

• ITE - Integrated Toolset Environment
  • Table of Contents
  • Installation
  • Stable Installation
    • Using the Sublime Project
    • Adding to git
  • Development Installation
    • git clone
    • Sublimehq/Packages
  • Disabled Packages
  • Debugging
  • License

• The table of contents used on this Markdown was generated by:
  1. git clone https://github.com/evandroforks/markdown-toc
  2. cd markdown-toc
  3. npm -g install
  4. cd ../repository-root
  5. markdown-toc README.MD

---

Installation _{_{Go to Top}}

When following the installation steps, you are going to be prompted to install either the Stable or Development version. If you are planning to fix bugs and contribute to Sublime Text plugins Development, you should choose the Development installation. But, if you are only looking to use things and report bugs, you can choose the Stable installation.

1. Download & Install Sublime Text 3 (https://www.sublimetext.com/3)
2. Go to the menu Tools -> Install Package Control, then, wait few seconds until the installation finishes up
3. Now, Go to the menu Preferences -> Package Control
4. Type Add Channel on the opened quick panel and press <kbd>Enter</kbd>
5. Then, input the following address and press <kbd>Enter</kbd>

   https://raw.githubusercontent.com/evandrocoan/StudioChannel/master/channel.json
   

6. Go to the menu Tools -> Command Palette... (Ctrl+Shift+P)
7. Type Preferences: Package Control Settings – User on the opened quick panel and press <kbd>Enter</kbd>
8. Then, find the following setting on your Package Control.sublime-settings file:

   "channels":
   [
       "https://packagecontrol.io/channel_v3.json",
       "https://raw.githubusercontent.com/evandrocoan/StudioChannel/master/channel.json",
   ],
   

9. And, change it to the following, i.e., put the https://raw.githubusercontent... line as first:

   "channels":
   [
       "https://raw.githubusercontent.com/evandrocoan/StudioChannel/master/channel.json",
       "https://packagecontrol.io/channel_v3.json",
   ],
   

   • The https://raw.githubusercontent... line must to be added before the https://packagecontrol.io... one, otherwise, you will not install this forked version of the package, but the original available on the Package Control default channel https://packagecontrol.io...
10. Now, go to the menu Preferences -> Package Control
11. Type Install Package on the opened quick panel and press <kbd>Enter</kbd>
12. Then, search for StudioChannel and press <kbd>Enter</kbd>
13. After finished installing the StudioChannel package, just follow the instructions on the screen.
14. You can also see this old video tutorial How to the Install Sublime Studio.

Stable Installation _{_{Go to Top}}

If you chose the Stable Installation, on this section you are going to be introduced with Stable installation tips.

While installing the Stable version, you can quickly edit any installed packages files by:

1. Opening the command palette and running the command PackageResourceViewer: Extract All Packages.
2. And setting the PackagesManager setting "extract_everything": true

Using the Sublime Project _{_{Go to Top}}

You can also open the SublimeStudio.sublime-project inside the Packages/StudioChannel package (git submodule) to quickly view/edit all installed packages. Just note, if you are using the Stable version and as all packages are distributed unpacked on the Stable version, all of your changes to the installed packages are going to be lost when they upgrade. If you would like to save them after the upgrade, you can use the OverrideUnpackedPackages feature. See: OverrideUnpackedPackages for more information.

Adding to git _{_{Go to Top}}

You can create a git repository on the root of your Stable Sublime Text installation by using the following .gitignore file:

/.sublime/
/Backup/
/Cache/
/Index/
/KEEPME
/Local/
/Settings/

/Packages/User/FileHistory*.json
/Packages/User/PackagesManager.cache/*

**/.git/**
*.sublime-package

This should exclude most undesired/binary things and allow you to fiercely control which changes happens with your Sublime Text Stable installation of the ITE.

Development Installation _{_{Go to Top}}

If you chose the Development Installation, on this section you are going to be introduced with Development instructions/tips.

If you installed the Development version, you need to have installed on your system path variable the following programs:

1. git
2. curl (linux/cygwin)
3. wget (linux/cygwin)
4. zip (linux/cygwin)
5. unzip (linux/cygwin)
6. date (linux/cygwin)

Beyond your local git client, it is recommended to install some git client interface as SmartGit, in order to manage this project because it has very complex submodules management. Also, your local git client need to have the user/login and password cached because some commands used by some packages like the Channel Manager, directly/unattended perform git operations like git pull and git push. Then, if your username or password is not cached, these packages commands which do git operations, are going to hang/block/not work properly.

To cache your git password you can use tools like:

1. https://github.com/Microsoft/Git-Credential-Manager-for-Windows
2. https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage

git clone _{_{Go to Top}}

It is not advised to use the git --clone command because git is buggy and cannot handle to clone this repository correctly. By following the installation instructions just above, you are going to be prompted whether you would like to install the Stable version or the Development version. And choosing the Development, this repository is going to programmatically and correctly be cloned by a Python Script. So, there is not need to directly use the git clone command. But, if you feel like manually using the git clone command, you need to pass the --recursive option and use it like this:

git clone --recursive -j4 https://github.com/evandrocoan/ITE

The -j4 parameter is to parallelly clone the repository using up to 4 threads or CPU cores.

Sublimehq/Packages _{_{Go to Top}}

Even if you choose to install the Development version, by the automated installer, it will not install the default upstream for Sublimehq/Packages. For it, you can just run these commands:

git clone --recursive https://github.com/evandroforks/Packages
mv Packages/.git "$SUBLIME_TEXT_DATA/Packages/.git"

Then, you will need to open the directory $SUBLIME_TEXT_DATA/Packages as a usual git repository, which is completely disconnected from the main ITE repository.

---

Disabled Packages _{_{Go to Top}}

For an updated list of packages to not enable see the issue:

1. https://github.com/evandrocoan/SublimeStudio/issues/50 Ignored packages to not enable!

---

Debugging _{_{Go to Top}}

Use on the console: (View -> Show Console)

sublime.log_input(True); sublime.log_commands(True); sublime.log_result_regex(True); sublime.log_indexing(True);

To disable it do:

sublime.log_input(False); sublime.log_commands(False); sublime.log_result_regex(False); sublime.log_indexing(False);

---

License _{_{Go to Top}}

All files in this repository are released under GNU General Public License v3.0 or the latest version available on http://www.gnu.org/licenses/gpl.html, except the files coming from git submodules (see .gitmodules file) and the files/directories which include their own license header/file.

Sublime Studio, A set of Settings and Packages for Sublime Text 3
Copyright (C) 2018 Evandro Coan <https://github.com/evandrocoan>

Redistributions of source code m