-
Notifications
You must be signed in to change notification settings - Fork 146
Redcar plugins
- Strip Trailing Spaces (Strip trailing spaces when saving, like Gedit’s “Save Without Trailing Space”)
- Todo List (Adds a todo list to the Project menu. Configurable in Plugin Preferences.)
- Search and Replace (Search and Replace)
Here are all the third party plugins we know about:
- Github viewer ( View a Github repository in Redcar )
- Go to github (Show current file in github, and selects the same lines that are selected in RedcarEditor)
- Find in project (fast find in project plugin, grep required)
- GCCSense (highly precise code completion for C/C++, GCCSense required)
- RSense (highly precise code completion for Ruby)
- redcar-pastie (create a gist from Redcar)
- redcar-help (Displays a help file/user guide for Redcar)
- touchy (Adds a ‘Touch File’ option to the project context menu)
- Sparkup Adds Sparkup (similar to Zen Coding but better) functionalities to Redcar
(Feel free to add yours to the bottom.)
Plugins should be written with the “plugin.rb” file in the root of the repo, that way it is easy to install them straight from Github by cloning the plugin repo into their ~/.redcar/plugins.
Typical installation is something like
cd ~/.redcar/plugins git clone git://github.com/username/plugin-project-name.git
See Dan’s blog for some posts that help with writing plugins. And of course the existing plugins and existing source are great examples.
When you’ve written a plugin, send an email to the mailing list with a subject like: “[ANN] my great new plugin 0.1”, so we can all enjoy it!
Plugins that satisfy the following conditions we will try to integrate into Redcar core:
- They must work cross-platform.
- They must not add native dependencies to Redcar.
- They must be of general interest.
Currently you’ll want to vendor gem dependencies into your plugin itself.