Well, I am back with some more updates on my Sublime Text 2 Guard
Plugin. This is a smaller release
than the last as I have been very busy. Despite its small stature it is an
exciting one as we have another contribution to honor. The following are the
- Fixed comma, single quote, question mark color issues
- Fixed small color issue caused by
- Better console colors, change
0 failures from red to green (Thanks
A special thanks goes out to @lidanh for the code
contribution. The new colors are much nicer and the
0 failures being green
instead of red makes it easier to detect success vs failure.
Thanks also goes out to all the users of the Sublime Text 2 Guard
Plugin. Especially, the users that
have been submitting bug reports and feature requests. This plugin wouldn’t
exist without the direction and feedback from you all.
Please continue to provide feedback via Sublime Text 2 Guard Plugin
issues on our GitHub page.
Well, I got some more updates for you all.
My Sublime Text 2 Guard Plugin has recently been recognized as an essential
Sublime Text 2 plugin on a nettuts+ blog post. Thanks to this publicity and the
exposure via Package Control, Twitter, GitHub, and Google I have gotten some
decent feedback, especially around my recent addition of colored output. Thanks
to all that feedback I have pushed out the following improvements to the
Sublime Text 2 Guard Plugin:
- Support for directory paths with spaces (#19, Thanks @ffmike)
- Fixed dash based coloring issue (#16)
- Fixed single quote based coloring issue (#17)
- Fixed question mark based coloring issue (#20)
- Fixed period based coloring issue (#21)
- Fixed success dot section identification & coloring issue (#22)
- Fixed a second single quote based coloring issue (#23)
- Added command relativity (#24)
The above break down of improvements include primarily a bunch of coloring
fixes, command relativity, and one very important issue that deserves some
recognition, issue #19 by
@ffmike. This is the Sublime Text 2 Guard Plugin’s
first contribution. Much thanks goes out to @ffmike
for being our first contributor.
As usual if any of you have identified bugs or features that you would like
added please submit them on the GitHub Issues page for the Sublime Text 2
I know there are a number of you who have been eagerly awaiting this moment. I
sure have been. I am proud to announce the first release of the Sublime Text 2
Guard Plugin that provides colored
output. Basically, it ended up that I had to define a language file to identify
the entities in the output and then define a theme to color those identified
entities. Once, I did that I simply programatically set the color_scheme and
syntax options for the output panel and like magic colors worked. Given the
complexity of the language definition and the limited test cases I had when
developing I am sure there are going to be some bugs to work out. So, as usual
please create issues if you find any of these
My Sublime Text 2 Guard plugin has been out for a couple weeks now and it has
definitely gotten some more usage under its belt. Thanks to everyone for your
usage and feedback. As a result of the feedback and user generated issues I
have released a new version to tighten it up a bit both from a user experience
stand point as well as a stability standpoint. This release includes the
- Now installable via Package Control
- Fixed Guard won’t start when installled via Package Control (issue #11)
- Added auto show output feature (issue #12)
#!/bin/bash in internal scripts
For info on how to get the latest version or how to report bugs, feature
requsts, etc. Please check out the GitHub page for the sublime_guard project.
I was having some difficulties with a couple bugs in the Sublime Text 2 Guard
plugin I have been working on. So, I decided I would drop Jon Skinner,
developer of Sublime Text 2, an e-mail and see if he knew about the issues I
was having and hopefully of solutions/work arounds for them. Jon, was very
helpful in terms of better understanding the issues as well as suggesting some
Anyways, given the input from Jon I took another look at the bugs/features of
the Guard plugin and decided to tackle them tonight. The following items show
the progress that I made tonight with respect to the Sublime Text 2 Guard
- Enabled native Sublime Text 2 word wrap in the Guard output view.
- Guard now exits properly when Sublime Text 2 exits/dies.
- Added default key bindings to show Guard output view (super+shift+c)
- Submitted a pull request to get the Guard plugin added to the Package
Control repository list.
As usual I am looking for feedback issues (feature requests, bug fixes, etc.)
You can find the project as
sublime_guard on GitHub. As of
tonight I am down to two feature requests. So, please create bugs in the issues
if you run into any so that I can work on fixing them sooner rather than later.