SF.net SVN: geany-plugins:[1031] branches/geany-plugins/geany-plugins-0.18/ README
hyperair at users.sourceforge.net
hyperair at xxxxx
Mon Oct 26 11:30:08 UTC 2009
Revision: 1031
http://geany-plugins.svn.sourceforge.net/geany-plugins/?rev=1031&view=rev
Author: hyperair
Date: 2009-10-26 11:30:08 +0000 (Mon, 26 Oct 2009)
Log Message:
-----------
Correct typo and spelling errors in README
* plug-in => plugin
* Lu's-pkg => lua-pkg
Modified Paths:
--------------
branches/geany-plugins/geany-plugins-0.18/README
Modified: branches/geany-plugins/geany-plugins-0.18/README
===================================================================
--- branches/geany-plugins/geany-plugins-0.18/README 2009-10-26 11:29:34 UTC (rev 1030)
+++ branches/geany-plugins/geany-plugins-0.18/README 2009-10-26 11:30:08 UTC (rev 1031)
@@ -6,7 +6,7 @@
sudo make install
This will configure, build and install most of the Geany plugins. There is some
-auto-detection in place which automagically disables some of the plug-ins if
+auto-detection in place which automagically disables some of the plugins if
there are insufficient build dependencies. The following arguments can tweak the
behaviour of the configure script:-
@@ -29,18 +29,18 @@
Example:
./configure --enable-geanylua --enable-gtkspell --enable-spellcheck
-This will force all optional plug-ins to be enabled even if dependencies are missing.
+This will force all optional plugins to be enabled even if dependencies are missing.
== Other tweaks ==
The following options can be passed to ./configure in the form
--with-<option>=<argument>.
-* Lu's-pkg -- the name of the lua pkg-config package name.
+* lua-pkg -- the name of the lua pkg-config package name.
* geany-prefix -- Geany's prefix, used when compiling Geany.
-== Compiling Individual Plug-ins ==
-The Geany Plug-ins project uses a recursive automake build system, which means
+== Compiling Individual Plugins ==
+The Geany Plugins project uses a recursive automake build system, which means
that after running ./configure, you may compile each individual plug-in by cd-ing
into the respective plug-in directory and compiling it.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
More information about the Plugins-Commits
mailing list