![]() ![]() Choose a name knowing that it is the one that will show up in the “Build Systems” menu and keep the file extension. Sublime will automatically show you the correct place to put it, in my case a configuration folder inside my home folder ( ~/.config/sublime-text-3/Packages/User/). This is only moving to the test folder and building/running the tests, exactly what we want while coding and testing. sublime-build file to this will get the work done: This is available internally as the tag $folder. Opening the folder comes with a bonus: now the repository folder for your project is known by Sublime since it is the folder you told it to open. hold CRTL key, press and release K key, press and release B key, release CTRL key.go to: “View » Side Bar » Show Side Bar”.Small tip: I’ve hidden the left side bar unwittingly before and had to learn how to get it visible again. This will show the folder tree in the window’s left side section. I’m used to (and recommend doing so) go to “File » Open Folder…” and selecting my repository folder when working on something. In my case it is bugfree_robot/test so the first step is getting inside this folder. The only required fix here is forcing this command to run inside the correct folder. It shows a make command already but it does not seem possible to be as simple as this, but it is almost that. ![]() ![]() Nothing more than the regular Java Script like structure that holds many other Sublime configuration profiles like default indentation procedure, language specific configurations and color syntax profile. sublime-build extension and this content: Clicking over this option will give you a new open file with a. Creating your own Build System is really easy though, and it is actually already listed in this same menu section as: “New build system”. It seams like almost all of them are able to build/run only single files and nothing more complex than this. The menu “Tools » Build System” lists a few languages that Sublime is able to build and run by default but I’d say that those default tools won’t get you very far. This problem was fixed as a side effect when I’ve decided to setup a build system inside Sublime to run my tests. This works pretty well and causes me no problems but one sometimes: building the tests after modifying a few files on sublime but forgetting to save one of them, getting test results that were not expected and taking a few minutes to realize this simple problem. My standard working setup has a Sublime window open showing the full repository folder tree in the left plus two vertical files open plus a terminal window (in another monitor preferentially) in the test folder so a simple make command will build and run my tests. ![]() By the way, for those able to read in portuguese, a friend of mine has shared a guide with many pointers in setting up an efficient vim working environment, check it out here. It may be a good tool after the “getting used to it” period but it never got me into really trying to acquire a relationship. I know many ones advocate against any kind of visual software for coding and will go hands tied with vim until death but I’ve never gotten there. It’s a software that provides many smart shortcuts that can get a lot done faster when you get used to them. I’m used to coding in Sublime Text 3 while developing code for the tests and the libraries for my projects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |