Menu
▾
▴
[ jEdit-commits ] SF.net SVN: jedit:[20470] jEdit/trunk/doc
|
From: <ez...@us...> - 2011-11-29 22:49:36
|
Revision: 20470
http://jedit.svn.sourceforge.net/jedit/?rev=20470&view=rev
Author: ezust
Date: 2011-11-29 22:49:30 +0000 (Tue, 29 Nov 2011)
Log Message:
-----------
Faq/tips related to source code control plugins.
Modified Paths:
--------------
jEdit/trunk/doc/FAQ/faq-plugins.xml
jEdit/trunk/doc/tips/tip84.html
Modified: jEdit/trunk/doc/FAQ/faq-plugins.xml
===================================================================
--- jEdit/trunk/doc/FAQ/faq-plugins.xml 2011-11-29 21:29:23 UTC (rev 20469)
+++ jEdit/trunk/doc/FAQ/faq-plugins.xml 2011-11-29 22:49:30 UTC (rev 20470)
@@ -106,20 +106,20 @@
<para>The SVNPlugin supports Subversion browsing, diffing
(via JDiff) and other common operations.</para>
<para>With *NIX (or cygwin), the Console plugin
- documentation has some ideas on how to use jEdit as the
- <literal>VISUAL</literal> editor when called from the
+ documentation has some ideas on how to set jEdit as the
+ <literal>VISUAL</literal> and <literal>EDITOR</literal> tool when called from the
cvs/svn/hg command-line tools, all of which can be run from
the Console dockable.</para>
<para>The ProjectViewer plugin has some support for reading
- the "entries" in your working directory, and will use that as a filter for importing. CVS/SVN support is built-in, and p4, bzr, git, and hg are also supported via plugins. </para>
- <para>The P4Plugin adds Perforce support to ProjectViewer,
- and has some other advanced features for working with
- Perforce repositories.</para>
+ the "entries" in your working directory, and will use that as a filter for importing. CVS/SVN support is built-in, and p4, bzr, git, and hg are supported via plugins. </para>
+ <para>The P4Plugin and SvnPlugin both add extensions to the ProjectViewer tree, and have some other features for working with repositories.</para>
+ <para><literal>SourceControl</literal> plugin has some features to work with Microsoft Visual SourceSafe.
+ </para>
+ <para> <literal>ClearCasePlugin</literal> is used with Rational ClearCase. </para>
<para>You can use jEdit as your default editor from WinCVS:
specify <userinput>jedit.exe</userinput> as your default
viewer and editor to automate the opening of file.</para>
- <para>GruntSpud and jEditCvs are not maintained, but do
- offer CVS support on jEdit 4.2final.</para>
+ <para>GruntSpud and jEditCvs plugins are no longer supported. </para>
</answer>
</qandaentry>
<qandaentry>
Modified: jEdit/trunk/doc/tips/tip84.html
===================================================================
--- jEdit/trunk/doc/tips/tip84.html 2011-11-29 21:29:23 UTC (rev 20469)
+++ jEdit/trunk/doc/tips/tip84.html 2011-11-29 22:49:30 UTC (rev 20470)
@@ -1,5 +1,8 @@
-<html><body>If you use a version control system, try the
-<b>Gruntspud</b> plugin (CVS), <b>SourceControl</b> (Perforce, Visual SourceSafe) or <b>ClearCase</b>.
-Plugins can
-be downloaded and installed from within jEdit using the plugin manager
-(<b>Plugins</b>><b>Plugin Manager</b>).</body></html>
+<html><body>
+<p> If you use a version control system, try the
+<b>SvnPlugin</b>, <b>P4Plugin</b>, or <b>ClearCasePlugin</b>.
+Or the <b>GitPlugin</b>, <b>HgPlugin</b>, or <b>BzrPlugin</b> for that matter.
+There's even a plugin for Visual SourceSafe, <b>SourceControl</b>.
+Plugins can be downloaded and installed from within jEdit using the plugin manager
+(<b>Plugins</b>><b>Plugin Manager</b>). </p>
+</body></html>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|