Revision: 4540
http://geany.svn.sourceforge.net/geany/?rev=4540&view=rev
Author: eht16
Date: 2010-01-24 16:17:11 +0000 (Sun, 24 Jan 2010)
Log Message:
-----------
Describe the defined environment variables GEANY_FILETYPE, GEANY_FILENAME and GEANY_FUNCNAME.
Modified Paths:
--------------
trunk/doc/geany.html
trunk/doc/geany.txt
Modified: trunk/doc/geany.html
===================================================================
--- trunk/doc/geany.html 2010-01-24 14:52:46 UTC (rev 4539)
+++ trunk/doc/geany.html 2010-01-24 16:17:11 UTC (rev 4540)
@@ -6,7 +6,7 @@
<meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />
<title>Geany</title>
<meta name="authors" content="Enrico Tröger Nick Treleaven Frank Lanitz" />
-<meta name="date" content="2010-01-02" />
+<meta name="date" content="2010-01-24" />
<style type="text/css">
/*
@@ -139,7 +139,7 @@
<br />Nick Treleaven
<br />Frank Lanitz</td></tr>
<tr><th class="docinfo-name">Date:</th>
-<td>2010-01-02</td></tr>
+<td>2010-01-24</td></tr>
<tr><th class="docinfo-name">Version:</th>
<td>0.19</td></tr>
</tbody>
@@ -4930,6 +4930,16 @@
</pre>
<p>Using this wildcard you can insert nearly any arbitrary text into the
template.</p>
+<p>In the environment of the executed command the variables
+<tt class="docutils literal">GEANY_FILENAME</tt>, <tt class="docutils literal">GEANY_FILETYPE</tt> and <tt class="docutils literal">GEANY_FUNCNAME</tt> are set.
+The value of these variables is filled in only if Geany knows about it.
+For example, <tt class="docutils literal">GEANY_FUNCNAME</tt> is only filled within the function
+description template. However, these variables are <tt class="docutils literal">always</tt> set,
+just maybe with an empty value.
+You can easily access them e.g. within an executed shell script using:</p>
+<pre class="literal-block">
+$GEANY_FILENAME
+</pre>
<div class="note">
<p class="first admonition-title">Note</p>
<p class="last">If the specified command could not be found or not executed, the wildcard is substituted
@@ -5892,7 +5902,7 @@
<div class="footer">
<hr class="footer" />
<a class="reference external" href="geany.txt">View document source</a>.
-Generated on: 2010-01-24 14:49 UTC.
+Generated on: 2010-01-24 16:15 UTC.
Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
</div>
Modified: trunk/doc/geany.txt
===================================================================
--- trunk/doc/geany.txt 2010-01-24 14:52:46 UTC (rev 4539)
+++ trunk/doc/geany.txt 2010-01-24 16:17:11 UTC (rev 4540)
@@ -4245,6 +4245,17 @@
Using this wildcard you can insert nearly any arbitrary text into the
template.
+In the environment of the executed command the variables
+``GEANY_FILENAME``, ``GEANY_FILETYPE`` and ``GEANY_FUNCNAME`` are set.
+The value of these variables is filled in only if Geany knows about it.
+For example, ``GEANY_FUNCNAME`` is only filled within the function
+description template. However, these variables are ``always`` set,
+just maybe with an empty value.
+You can easily access them e.g. within an executed shell script using::
+
+ $GEANY_FILENAME
+
+
.. note::
If the specified command could not be found or not executed, the wildcard is substituted
by an empty string. In such cases, you can find the occurred error message on Geany's
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 4537
http://geany.svn.sourceforge.net/geany/?rev=4537&view=rev
Author: ntrel
Date: 2010-01-22 16:41:04 +0000 (Fri, 22 Jan 2010)
Log Message:
-----------
Fix GLib warning & beep if trying to insert multiline comment for a
filetype that doesn't support it.
Modified Paths:
--------------
trunk/ChangeLog
trunk/src/callbacks.c
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2010-01-22 16:23:12 UTC (rev 4536)
+++ trunk/ChangeLog 2010-01-22 16:41:04 UTC (rev 4537)
@@ -2,6 +2,9 @@
* src/build.c:
Prevent possible segfault in get_build_group().
+ * src/callbacks.c:
+ Fix GLib warning & beep if trying to insert multiline comment for a
+ filetype that doesn't support it.
2010-01-18 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
Modified: trunk/src/callbacks.c
===================================================================
--- trunk/src/callbacks.c 2010-01-22 16:23:12 UTC (rev 4536)
+++ trunk/src/callbacks.c 2010-01-22 16:41:04 UTC (rev 4537)
@@ -1394,7 +1394,10 @@
verify_click_pos(doc); /* make sure that the click_pos is valid */
- editor_insert_multiline_comment(doc->editor);
+ if (doc->file_type->comment_open)
+ editor_insert_multiline_comment(doc->editor);
+ else
+ utils_beep();
}
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 4535
http://geany.svn.sourceforge.net/geany/?rev=4535&view=rev
Author: ntrel
Date: 2010-01-19 15:48:42 +0000 (Tue, 19 Jan 2010)
Log Message:
-----------
Edit wording/section names.
Modified Paths:
--------------
trunk/doc/plugins.dox
Modified: trunk/doc/plugins.dox
===================================================================
--- trunk/doc/plugins.dox 2010-01-18 17:17:34 UTC (rev 4534)
+++ trunk/doc/plugins.dox 2010-01-19 15:48:42 UTC (rev 4535)
@@ -481,25 +481,25 @@
}
* @endcode
*
+ * If you think this plugin seems not to implement any functionality right now and only wastes
+ * some memory, you are right. But it should compile and load/unload in Geany nicely.
+ * Now you have the very basic layout of a new plugin. Great, isn't it?
+ *
* @section building Building
*
+ * First make plugin.o:
+ *
* @code gcc -c plugin.c -fPIC `pkg-config --cflags geany` @endcode
*
- * to make plugin.o, then:
+ * Then make the plugin library plugin.so (or plugin.dll on Windows):
*
* @code gcc plugin.o -o plugin.so -shared `pkg-config --libs geany` @endcode
*
- * to make the plugin library plugin.so (or plugin.dll on Windows).
+ * If all went OK, put the library into one of the paths Geany looks for plugins,
+ * e.g. $prefix/lib/geany. See @ref paths "Installation paths" for details.
*
- * Then just put the library into one of the paths Geany looks for plugins in, e.g. $prefix/lib/geany.
- * See @ref paths "Installation paths" for details.
+ * @section realfunc Adding functionality
*
- * @section realfunc Real functionality
- *
- * If you think this plugin seems not to implement any functionality right now and only wastes
- * some memory, you are right. But it should compile and load/unload in Geany nicely.
- * Now you have the very basic layout of a new plugin. Great, isn't it?
- *
* Let's go on and implement some real functionality.
*
* As mentioned before, plugin_init() will be called when the plugin is loaded in Geany.
@@ -573,7 +573,8 @@
* memory once your plugin is unloaded, so you don't leave any memory leaks.
* Once this is done, your first plugin is ready. Congratulations!
*
- * The complete listing (without comments):
+ * @section listing Complete listing (without comments)
+ *
* @code
#include "geanyplugin.h"
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 4534
http://geany.svn.sourceforge.net/geany/?rev=4534&view=rev
Author: ntrel
Date: 2010-01-18 17:17:34 +0000 (Mon, 18 Jan 2010)
Log Message:
-----------
Fix some spacing.
Modified Paths:
--------------
trunk/doc/plugins.dox
Modified: trunk/doc/plugins.dox
===================================================================
--- trunk/doc/plugins.dox 2010-01-18 17:05:13 UTC (rev 4533)
+++ trunk/doc/plugins.dox 2010-01-18 17:17:34 UTC (rev 4534)
@@ -481,20 +481,21 @@
}
* @endcode
*
- * @section building Building
- * @code gcc -c plugin.c -fPIC `pkg-config --cflags geany` @endcode
+ * @section building Building
*
- * to make plugin.o, then:
+ * @code gcc -c plugin.c -fPIC `pkg-config --cflags geany` @endcode
*
- * @code gcc plugin.o -o plugin.so -shared `pkg-config --libs geany`@endcode
+ * to make plugin.o, then:
*
- * to make the plugin library plugin.so (or plugin.dll on Windows).
+ * @code gcc plugin.o -o plugin.so -shared `pkg-config --libs geany` @endcode
*
- * Then just put the library into one of the paths Geany looks for plugins in, e.g. $prefix/lib/geany.
- * See @ref paths "Installation paths" for details.
+ * to make the plugin library plugin.so (or plugin.dll on Windows).
*
- * @section realfunc Real functionality
+ * Then just put the library into one of the paths Geany looks for plugins in, e.g. $prefix/lib/geany.
+ * See @ref paths "Installation paths" for details.
*
+ * @section realfunc Real functionality
+ *
* If you think this plugin seems not to implement any functionality right now and only wastes
* some memory, you are right. But it should compile and load/unload in Geany nicely.
* Now you have the very basic layout of a new plugin. Great, isn't it?
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 4532
http://geany.svn.sourceforge.net/geany/?rev=4532&view=rev
Author: ntrel
Date: 2010-01-18 16:57:37 +0000 (Mon, 18 Jan 2010)
Log Message:
-----------
Don't use VERSION macro as the demo plugin should be able to be built independently from Geany.
Modified Paths:
--------------
trunk/plugins/demoplugin.c
Modified: trunk/plugins/demoplugin.c
===================================================================
--- trunk/plugins/demoplugin.c 2010-01-18 16:55:49 UTC (rev 4531)
+++ trunk/plugins/demoplugin.c 2010-01-18 16:57:37 UTC (rev 4532)
@@ -50,7 +50,7 @@
PLUGIN_VERSION_CHECK(147)
/* All plugins must set name, description, version and author. */
-PLUGIN_SET_INFO(_("Demo"), _("Example plugin."), VERSION, _("The Geany developer team"))
+PLUGIN_SET_INFO(_("Demo"), _("Example plugin."), "0.1" , _("The Geany developer team"))
static GtkWidget *main_menu_item = NULL;
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 4531
http://geany.svn.sourceforge.net/geany/?rev=4531&view=rev
Author: ntrel
Date: 2010-01-18 16:55:49 +0000 (Mon, 18 Jan 2010)
Log Message:
-----------
Add gcc commands to build a plugin to the HowTo.
Modified Paths:
--------------
trunk/ChangeLog
trunk/doc/plugins.dox
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2010-01-17 21:55:46 UTC (rev 4530)
+++ trunk/ChangeLog 2010-01-18 16:55:49 UTC (rev 4531)
@@ -1,3 +1,9 @@
+2010-01-18 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
+
+ * doc/plugins.dox:
+ Add gcc commands to build a plugin to the HowTo.
+
+
2010-01-17 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de>
* scripts/plugin_test.c:
Modified: trunk/doc/plugins.dox
===================================================================
--- trunk/doc/plugins.dox 2010-01-17 21:55:46 UTC (rev 4530)
+++ trunk/doc/plugins.dox 2010-01-18 16:55:49 UTC (rev 4531)
@@ -481,6 +481,20 @@
}
* @endcode
*
+ * @section building Building
+ * @code gcc -c plugin.c -fPIC `pkg-config --cflags geany` @endcode
+ *
+ * to make plugin.o, then:
+ *
+ * @code gcc plugin.o -o plugin.so -shared `pkg-config --libs geany`@endcode
+ *
+ * to make the plugin library plugin.so (or plugin.dll on Windows).
+ *
+ * Then just put the library into one of the paths Geany looks for plugins in, e.g. $prefix/lib/geany.
+ * See @ref paths "Installation paths" for details.
+ *
+ * @section realfunc Real functionality
+ *
* If you think this plugin seems not to implement any functionality right now and only wastes
* some memory, you are right. But it should compile and load/unload in Geany nicely.
* Now you have the very basic layout of a new plugin. Great, isn't it?
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.