This section deals with questions concerning the use of jEdit's plugins. Plugins are applications that share jEdit's memory space and user interface and provide a wide variety of functions and services.
1. General plugin questions | |
| |
Q: | Where can I get information on the latest available “official” plugins? |
A: | To get a listing of the latest plugins available for downloading from jEdit Plugin Central, use the feature on jEdit's menu. You can also get more detailed descriptions of the plugins from the Plugin Central web site. |
Q: | Where can I get information on new plugins under development? |
A: | We encourage plugin developers to join the
|
Q: | How do I install a plugin manually, without using the Plugin Manager? |
A: | Copy the plugin's jar archive file (or files, if there
are more than one) to the |
Q: | How do I write a plugin? |
A: | Writing a plugin requires a working knowledge of Java and some familiarity with jEdit's Plugin API. There is a tutorial on plugin development in the jEdit User's Guide. The source code distribution for jEdit also includes the source for an example plugin, Quick Notepad, which is discussed in the tutorial. To learn more about plugin development, take a look at the source code for other plugins, particularly those whose features or user interface you might use as a model. The jedit-devel mailing list and the message boards at jEdit Community are also available for specific questions. |
Q: | Is there an IRC (Internet Relay Chat) plugin for jEdit? |
A: | Yes. Open the Plugin Manager, then select . You will find the IRC plugin which you can select for installation. |
Q: | Is it possible to execute my application from within jEdit? |
A: | Yes. You can use the System shell of the Console plugin to run your application. |
Q: | Can I work with cvs/svn/git/hg/bzr/Perforce under jEdit? Is there a plugin for my favorite SCCS system? How can I send a command and edit a commit message from jEdit to svn/git without leaving my editor? |
A: | When using command line tools, the Console plugin
documentation has some ideas on how to set your environment so that jEdit is the
The SVNPlugin supports Subversion browsing, diffing (via JDiff) and other common operations. The ProjectViewer plugin has some support for reading the "entries" in your working directory, and will use that as a filter for importing. CVS support is built-in, and svn, p4, bzr, git, and hg are supported via plugins. The
The You can use jEdit as your default editor from WinCVS:
specify GruntSpud and jEditCvs plugins are no longer supported. |
Q: | Is there a debugger plugin? |
A: | The GdbPlugin provides gdb/mi support for C/C++ programs. Also, the Console BeanShell can be used to debug Java classes in the current running JVM. A plugin based on the version 1.4 of the JSwat debugger application is currently available for download using jEdit's Plugin Manager feature. The developers would like to come up with a common debugger plugin that can be shared between java, gdb, and python, but such a thing does not exist at this time. |
Q: | Any development on integrating an XSL parser? It would be great to have the possibility to do XSL + XSLT -> XHTML development in the same environment as other development. |
A: | There is currently one plugin available called XSLT. The XSLT plugin provides features for: transforming XML using XSL transformation stylesheets; evaluating XPath expressions on XML and displaying results; and indenting XML. |
Q: | Is there a plugin to enable editing of remote files over FTP or SSH? |
A: | The FTP plugin allows remote editing of files over the
|