Revision: 5065
http://geany.svn.sourceforge.net/geany/?rev=5065&view=rev
Author: ntrel
Date: 2010-06-25 16:50:27 +0000 (Fri, 25 Jun 2010)
Log Message:
-----------
Move plugin signals docs to pluginsignals.c, using function
pointer syntax instead of @signaldef as this puts a summary of
the signal names at the top of the page and sorts alphabetically.
(Note: the syntax is similar to Vala signal syntax).
Modified Paths:
--------------
trunk/ChangeLog
trunk/doc/Makefile.am
trunk/doc/plugins.dox
trunk/doc/pluginsymbols.c
trunk/src/main.c
trunk/src/plugindata.h
trunk/src/pluginutils.c
trunk/src/sciwrappers.c
Added Paths:
-----------
trunk/doc/pluginsignals.c
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/ChangeLog 2010-06-25 16:50:27 UTC (rev 5065)
@@ -1,3 +1,14 @@
+2010-06-25 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
+
+ * src/sciwrappers.c, src/plugindata.h, src/pluginutils.c, src/main.c,
+ doc/pluginsignals.c, doc/pluginsymbols.c, doc/Makefile.am,
+ doc/plugins.dox:
+ Move plugin signals docs to pluginsignals.c, using function
+ pointer syntax instead of @signaldef as this puts a summary of
+ the signal names at the top of the page and sorts alphabetically.
+ (Note: the syntax is similar to Vala signal syntax).
+
+
2010-06-24 Lex Trotman <elextr(at)gmail(dot)com>
* src/build.c
Modified: trunk/doc/Makefile.am
===================================================================
--- trunk/doc/Makefile.am 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/doc/Makefile.am 2010-06-25 16:50:27 UTC (rev 5065)
@@ -1,9 +1,10 @@
man_MANS=geany.1
DOCDIR = $(DESTDIR)$(docdir)
IMAGE_FILES = images/*.png
-EXTRA_DIST = geany.html geany.css geany.txt geany.1 plugins.dox pluginsymbols.c \
- stash-example.c \
- $(srcdir)/$(IMAGE_FILES)
+EXTRA_DIST = geany.html geany.css geany.txt geany.1 \
+ plugins.dox pluginsymbols.c pluginsignals.c \
+ stash-example.c \
+ $(srcdir)/$(IMAGE_FILES)
pdf: geany.txt
rst2latex -stg --documentoptions="10pt,a4paper" --output-encoding=utf8 $(srcdir)/geany.txt geany.tex
Modified: trunk/doc/plugins.dox
===================================================================
--- trunk/doc/plugins.dox 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/doc/plugins.dox 2010-06-25 16:50:27 UTC (rev 5065)
@@ -44,7 +44,7 @@
* - @link howto Plugin HowTo @endlink - get started
* - @link pluginsymbols.c Plugin Symbols @endlink
* - @link plugindata.h Plugin Datatypes and Macros @endlink
- * - @link signals Plugin Signals @endlink
+ * - @link pluginsignals.c Plugin Signals @endlink
* - @link pluginutils.h Plugin Utility Functions @endlink
* - @link guidelines Plugin Writing Guidelines @endlink
* - <b>plugins/demoplugin.c</b> - in Geany's source, bigger than the howto example
@@ -71,267 +71,6 @@
*/
/**
- * @page signals Plugin Signals
- *
- *
- * @section Usage
- *
- * To use plugin signals in Geany, you have two options:
- *
- * -# Create a PluginCallback array with the @ref plugin_callbacks symbol. List the signals
- * you want to listen to and create the appropiate signal callbacks for each signal.
- * The callback array is read @a after plugin_init() has been called.
- * -# Use plugin_signal_connect(), which can be called at any time and can also connect
- * to non-Geany signals (such as GTK widget signals).
- *
- * The following code demonstrates how to use signals in Geany plugins. The code can be inserted
- * in your plugin code at any desired position.
- *
- * @code
-static void on_document_open(GObject *obj, GeanyDocument *doc, gpointer user_data)
-{
- printf("Example: %s was opened\n", DOC_FILENAME(doc));
-}
-
-PluginCallback plugin_callbacks[] =
-{
- { "document-open", (GCallback) &on_document_open, FALSE, NULL },
- { NULL, NULL, FALSE, NULL }
-};
- * @endcode
- * @note The PluginCallback array has to be ended with a final @c NULL entry.
- *
- * @section Signals
- *
- * @signaldef document-new
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent when a new document is created.
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the new document.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef document-open
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent when a new document is opened.
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the opened document.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef document-before-save
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent before a document is saved.
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the document to be saved.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef document-save
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent when a new document is saved.
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the saved document.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef document-filetype-set
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, GeanyFiletype *filetype_old, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent after the filetype of a document has been changed.
- * The previous filetype object is passed but it can be NULL (e.g. at startup).
- * The new filetype can be read with: @code
- * GeanyFiletype *ft = doc->file_type;
- * @endcode
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the saved document.
- * @param filetype_old the previous filetype of the document.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef document-activate
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent when switching notebook pages.
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the current document.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef document-close
- * @signalproto
- * void user_function(GObject *obj, GeanyDocument *doc, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent before closing a document.
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param doc the document about to be closed.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef project-open
- * @signalproto
- * void user_function(GObject *obj, GKeyFile *config, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent after a project is opened but before session files are loaded.
- * @param obj a GeanyObject instance, should be ignored.
- * @param config an exising GKeyFile object which can be used to read and write data.
- * It must not be closed or freed.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef project-save
- * @signalproto
- * void user_function(GObject *obj, GKeyFile *config, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent when a project is saved(happens when the project is created, the properties
- * dialog is closed or Geany is exited). This signal is emitted shortly before Geany
- * will write the contents of the GKeyFile to the disc.
- * @param obj a GeanyObject instance, should be ignored.
- * @param config an exising GKeyFile object which can be used to read and write data.
- * It must not be closed or freed.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef project-close
- * @signalproto
- * void user_function(GObject *obj, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent after a project is closed.
- * @param obj a GeanyObject instance, should be ignored.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef geany-startup-complete
- * @signalproto
- * void user_function(GObject *obj, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent once Geany has finished all initialization and startup tasks and the GUI has been
- * realized. This signal is the very last step in the startup process and is sent once
- * the GTK main event loop has been entered.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef build-start
- * @signalproto
- * void user_function(GObject *obj, gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent before build is started. Plugins can use this signal e.g. to save the opened documents
- * before the build starts.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef update-editor-menu
- * @signalproto
- * void user_function(GObject *obj, const gchar *word, gint pos, GeanyDocument *doc,
- * gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * Sent before the popup menu of the editing widget is shown. This can be used to modify or extend
- * the popup menu.
- *
- * @note You can add menu items from @c plugin_init() using @c geany->main_widgets->editor_menu,
- * remembering to destroy them in @c plugin_cleanup().
- *
- * You need to include "document.h" for the declaration of GeanyDocument.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param word the current word (in UTF-8 encoding) below the cursor position
- where the popup menu will be opened.
- * @param click_pos the cursor position where the popup will be opened.
- * @param doc the current document.
- * @param user_data user data.
- * @endsignaldef
- *
- * @signaldef editor-notify
- * @signalproto
- * gboolean user_function(GObject *obj, GeanyEditor *editor, SCNotification *nt,
- * gpointer user_data);
- * @endsignalproto
- * @signaldesc
- * This signal is sent whenever something in the editor widget changes (character added,
- * fold level changes, clicks to the line number margin, ...).
- * A detailed description of possible notifications and the SCNotification can be found at
- * http://www.scintilla.org/ScintillaDoc.html#Notifications.
- *
- * If you connect to this signal, you must check @c nt->nmhdr.code for the notification type
- * to prevent handling unwanted notifications. This is important because for instance SCN_UPDATEUI
- * is sent very often whereas you probably don't want to handle this notification.
- *
- * By default, the signal is sent before Geany's default handler is processing the event.
- * Your callback function should return FALSE to allow Geany processing the event as well. If you
- * want to prevent this for some reason, return TRUE.
- * Please use this with care as it can break basic functionality of Geany.
- *
- * The signal can be sent after Geany's default handler has been run when you set
- * PluginCallback::after field to TRUE.
- *
- * An example callback implemention of this signal can be found in the Demo plugin.
- *
- * @warning This signal has much power and should be used carefully. You should especially
- * care about the return value; make sure to return TRUE only if it is necessary
- * and in the correct situations.
- *
- * You need to include "editor.h" for the declaration of GeanyEditor and "Scintilla.h" for
- * SCNotification.
- *
- * @param obj a GeanyObject instance, should be ignored.
- * @param editor The current GeanyEditor.
- * @param nt A pointer to the SCNotification struct which holds additional information for
- * the event.
- * @param user_data user data.
- * @return @c TRUE to stop other handlers from being invoked for the event.
- * @c FALSE to propagate the event further.
- *
- * @since 0.16
- * @endsignaldef
- *
- *
- *
* @page guidelines Plugin Writing Guidelines
*
* @section intro Introduction
Added: trunk/doc/pluginsignals.c
===================================================================
--- trunk/doc/pluginsignals.c (rev 0)
+++ trunk/doc/pluginsignals.c 2010-06-25 16:50:27 UTC (rev 5065)
@@ -0,0 +1,235 @@
+/*
+ * pluginsignals.c - this file is part of Geany, a fast and lightweight IDE
+ *
+ * Copyright 2008-2010 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de>
+ * Copyright 2008-2010 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ * MA 02110-1301, USA.
+ *
+ * $Id$
+ */
+
+/* Note: this file is for Doxygen only. */
+
+/**
+ * @file pluginsignals.c
+ * Plugin Signals
+ *
+ *
+ * @section Usage
+ *
+ * To use plugin signals in Geany, you have two options:
+ *
+ * -# Create a PluginCallback array with the @ref plugin_callbacks symbol. List the signals
+ * you want to listen to and create the appropiate signal callbacks for each signal.
+ * The callback array is read @a after plugin_init() has been called.
+ * -# Use plugin_signal_connect(), which can be called at any time and can also connect
+ * to non-Geany signals (such as GTK widget signals).
+ *
+ * This page lists the signal prototypes, but you connect to them using the
+ * string name (which by convention uses @c - hyphens instead of @c _ underscores).
+ *
+ * E.g. @c "document-open" for @ref document_open.
+ *
+ * The following code demonstrates how to use signals in Geany plugins. The code can be inserted
+ * in your plugin code at any desired position.
+ *
+ * @code
+static void on_document_open(GObject *obj, GeanyDocument *doc, gpointer user_data)
+{
+ printf("Example: %s was opened\n", DOC_FILENAME(doc));
+}
+
+PluginCallback plugin_callbacks[] =
+{
+ { "document-open", (GCallback) &on_document_open, FALSE, NULL },
+ { NULL, NULL, FALSE, NULL }
+};
+ * @endcode
+ * @note The PluginCallback array has to be ended with a final @c NULL entry.
+ */
+
+/** Sent when a new document is created.
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the new document.
+ * @param user_data user data.
+ */
+signal void (*document_new)(GObject *obj, GeanyDocument *doc, gpointer user_data);
+
+/** Sent when a new document is opened.
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the opened document.
+ * @param user_data user data.
+ */
+signal void (*document_open)(GObject *obj, GeanyDocument *doc, gpointer user_data);
+
+/** Sent before a document is saved.
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the document to be saved.
+ * @param user_data user data.
+ */
+signal void (*document_before_save)(GObject *obj, GeanyDocument *doc, gpointer user_data);
+
+/** Sent when a new document is saved.
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the saved document.
+ * @param user_data user data.
+ */
+signal void (*document_save)(GObject *obj, GeanyDocument *doc, gpointer user_data);
+
+
+/** Sent after the filetype of a document has been changed.
+ * The previous filetype object is passed but it can be NULL (e.g. at startup).
+ * The new filetype can be read with: @code
+ * GeanyFiletype *ft = doc->file_type;
+ * @endcode
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the saved document.
+ * @param filetype_old the previous filetype of the document.
+ * @param user_data user data.
+ */
+signal void (*document_filetype_set)(GObject *obj, GeanyDocument *doc, GeanyFiletype *filetype_old, gpointer user_data);
+
+/** Sent when switching notebook pages.
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the current document.
+ * @param user_data user data.
+ */
+signal void (*document_activate)(GObject *obj, GeanyDocument *doc, gpointer user_data);
+
+/** Sent before closing a document.
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param doc the document about to be closed.
+ * @param user_data user data.
+ */
+signal void (*document_close)(GObject *obj, GeanyDocument *doc, gpointer user_data);
+
+/** Sent after a project is opened but before session files are loaded.
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param config an exising GKeyFile object which can be used to read and write data.
+ * It must not be closed or freed.
+ * @param user_data user data.
+ */
+signal void (*project_open)(GObject *obj, GKeyFile *config, gpointer user_data);
+
+/** Sent when a project is saved(happens when the project is created, the properties
+ * dialog is closed or Geany is exited). This signal is emitted shortly before Geany
+ * will write the contents of the GKeyFile to the disc.
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param config an exising GKeyFile object which can be used to read and write data.
+ * It must not be closed or freed.
+ * @param user_data user data.
+ */
+signal void (*project_save)(GObject *obj, GKeyFile *config, gpointer user_data);
+
+/** Sent after a project is closed.
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param user_data user data.
+ */
+signal void (*project_close)(GObject *obj, gpointer user_data);
+
+/** Sent once Geany has finished all initialization and startup tasks and the GUI has been
+ * realized. This signal is the very last step in the startup process and is sent once
+ * the GTK main event loop has been entered.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param user_data user data.
+ */
+signal void (*geany_startup_complete)(GObject *obj, gpointer user_data);
+
+/** Sent before build is started. Plugins can use this signal e.g. to save the opened documents
+ * before the build starts.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param user_data user data.
+ */
+signal void (*build_start)(GObject *obj, gpointer user_data);
+
+/** Sent before the popup menu of the editing widget is shown. This can be used to modify or extend
+ * the popup menu.
+ *
+ * @note You can add menu items from @c plugin_init() using @c geany->main_widgets->editor_menu,
+ * remembering to destroy them in @c plugin_cleanup().
+ *
+ * You need to include "document.h" for the declaration of GeanyDocument.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param word the current word (in UTF-8 encoding) below the cursor position
+ where the popup menu will be opened.
+ * @param click_pos the cursor position where the popup will be opened.
+ * @param doc the current document.
+ * @param user_data user data.
+ */
+signal void (*update_editor_menu)(GObject *obj, const gchar *word, gint pos, GeanyDocument *doc,
+ gpointer user_data);
+
+/** Sent whenever something in the editor widget changes.
+ * E.g. Character added, fold level changes, clicks to the line number margin.
+ * A detailed description of possible notifications and the SCNotification can be found at
+ * http://www.scintilla.org/ScintillaDoc.html#Notifications.
+ *
+ * If you connect to this signal, you must check @c nt->nmhdr.code for the notification type
+ * to prevent handling unwanted notifications. This is important because for instance SCN_UPDATEUI
+ * is sent very often whereas you probably don't want to handle this notification.
+ *
+ * By default, the signal is sent before Geany's default handler is processing the event.
+ * Your callback function should return FALSE to allow Geany processing the event as well. If you
+ * want to prevent this for some reason, return TRUE.
+ * Please use this with care as it can break basic functionality of Geany.
+ *
+ * The signal can be sent after Geany's default handler has been run when you set
+ * PluginCallback::after field to TRUE.
+ *
+ * An example callback implemention of this signal can be found in the Demo plugin.
+ *
+ * @warning This signal has much power and should be used carefully. You should especially
+ * care about the return value; make sure to return TRUE only if it is necessary
+ * and in the correct situations.
+ *
+ * You need to include "editor.h" for the declaration of GeanyEditor and "Scintilla.h" for
+ * SCNotification.
+ *
+ * @param obj a GeanyObject instance, should be ignored.
+ * @param editor The current GeanyEditor.
+ * @param nt A pointer to the SCNotification struct which holds additional information for
+ * the event.
+ * @param user_data user data.
+ * @return @c TRUE to stop other handlers from being invoked for the event.
+ * @c FALSE to propagate the event further.
+ *
+ * @since 0.16
+ */
+signal gboolean (*editor_notify)(GObject *obj, GeanyEditor *editor, SCNotification *nt,
+ gpointer user_data);
Property changes on: trunk/doc/pluginsignals.c
___________________________________________________________________
Added: svn:keywords
+ Author Date Id Revision
Added: svn:eol-style
+ native
Modified: trunk/doc/pluginsymbols.c
===================================================================
--- trunk/doc/pluginsymbols.c 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/doc/pluginsymbols.c 2010-06-25 16:50:27 UTC (rev 5065)
@@ -66,7 +66,7 @@
PluginFields *plugin_fields;
/** An array for connecting GeanyObject events, which should be terminated with
- * @c {NULL, NULL, FALSE, NULL}. See @link signals Signal documentation @endlink.
+ * @c {NULL, NULL, FALSE, NULL}. See @link pluginsignals.c Signal documentation @endlink.
* @see plugin_signal_connect(). */
PluginCallback plugin_callbacks[];
Modified: trunk/src/main.c
===================================================================
--- trunk/src/main.c 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/src/main.c 2010-06-25 16:50:27 UTC (rev 5065)
@@ -400,8 +400,8 @@
* This is because the main window is realized (i.e. actually drawn on the screen) at the
* end of the startup process.
*
- * @note Maybe you want to use the @ref geany-startup-complete signal to get notified about
- * the completed startup process.
+ * @note Maybe you want to use the @link pluginsignals.c @c "geany-startup-complete" signal @endlink
+ * to get notified about the completed startup process.
*
* @return @c TRUE if the Geany main window has been realized or @c FALSE otherwise.
*
Modified: trunk/src/plugindata.h
===================================================================
--- trunk/src/plugindata.h 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/src/plugindata.h 2010-06-25 16:50:27 UTC (rev 5065)
@@ -173,7 +173,7 @@
typedef struct PluginCallback
{
/** The name of signal, must be an existing signal. For a list of available signals,
- * please see the @link signals Signal documentation @endlink. */
+ * please see the @link pluginsignals.c Signal documentation @endlink. */
const gchar *signal_name;
/** A callback function which is called when the signal is emitted. */
GCallback callback;
Modified: trunk/src/pluginutils.c
===================================================================
--- trunk/src/pluginutils.c 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/src/pluginutils.c 2010-06-25 16:50:27 UTC (rev 5065)
@@ -100,9 +100,9 @@
/** Connects a signal which will be disconnected on unloading the plugin, to prevent a possible segfault.
* @param plugin Must be @ref geany_plugin.
- * @param object Object to connect to, or @c NULL when using @link signals Geany signals @endlink.
+ * @param object Object to connect to, or @c NULL when using @link pluginsignals.c Geany signals @endlink.
* @param signal_name The name of the signal. For a list of available
- * signals, please see the @link signals Signal documentation @endlink.
+ * signals, please see the @link pluginsignals.c Signal documentation @endlink.
* @param after Set to @c TRUE to call your handler after the main signal handlers have been called
* (if supported by @a signal_name).
* @param callback The function to call when the signal is emitted.
Modified: trunk/src/sciwrappers.c
===================================================================
--- trunk/src/sciwrappers.c 2010-06-24 06:39:24 UTC (rev 5064)
+++ trunk/src/sciwrappers.c 2010-06-25 16:50:27 UTC (rev 5065)
@@ -25,7 +25,8 @@
* Wrapper functions for the Scintilla editor widget @c SCI_* messages.
* You should also check the http://scintilla.org documentation, as it is more detailed.
*
- * To get Scintilla notifications, use the @c editor-notify @link signals Geany Signal @endlink.
+ * To get Scintilla notifications, use the
+ * @link pluginsignals.c @c "editor-notify" signal @endlink.
*
* @note These functions were originally from the cssed project
* (http://cssed.sf.net, thanks).
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5060
http://geany.svn.sourceforge.net/geany/?rev=5060&view=rev
Author: ntrel
Date: 2010-06-23 12:34:11 +0000 (Wed, 23 Jun 2010)
Log Message:
-----------
Implement Find in Files file pattern search.
Modified Paths:
--------------
trunk/ChangeLog
trunk/doc/geany.html
trunk/doc/geany.txt
trunk/src/search.c
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2010-06-22 16:51:01 UTC (rev 5059)
+++ trunk/ChangeLog 2010-06-23 12:34:11 UTC (rev 5060)
@@ -1,3 +1,9 @@
+2010-06-23 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
+
+ * src/search.c, doc/geany.txt, doc/geany.html:
+ Implement Find in Files file pattern search.
+
+
2010-06-22 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
* src/search.c:
Modified: trunk/doc/geany.html
===================================================================
--- trunk/doc/geany.html 2010-06-22 16:51:01 UTC (rev 5059)
+++ trunk/doc/geany.html 2010-06-23 12:34:11 UTC (rev 5060)
@@ -3,10 +3,10 @@
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />
+<meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
<title>Geany</title>
<meta name="authors" content="Enrico Tröger Nick Treleaven Frank Lanitz" />
-<meta name="date" content="2010-06-04" />
+<meta name="date" content="2010-06-21" />
<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-06-04</td></tr>
+<td>2010-06-21</td></tr>
<tr><th class="docinfo-name">Version:</th>
<td>0.20</td></tr>
</tbody>
@@ -149,343 +149,343 @@
License as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version. A copy of this
license can be found in the file COPYING included with the source code
-of this program, and also in the chapter <a class="reference internal" href="#gnu-general-public-license">GNU General Public License</a>.</p>
-<div class="contents topic" id="contents">
-<p class="topic-title first">Contents</p>
+of this program, and also in the chapter <a class="reference" href="#gnu-general-public-license">GNU General Public License</a>.</p>
+<div class="contents topic">
+<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
<ul class="simple">
-<li><a class="reference internal" href="#introduction" id="id8">Introduction</a><ul>
-<li><a class="reference internal" href="#about-geany" id="id9">About Geany</a></li>
-<li><a class="reference internal" href="#where-to-get-it" id="id10">Where to get it</a></li>
-<li><a class="reference internal" href="#license" id="id11">License</a></li>
-<li><a class="reference internal" href="#about-this-document" id="id12">About this document</a></li>
+<li><a class="reference" href="#introduction" id="id8" name="id8">Introduction</a><ul>
+<li><a class="reference" href="#about-geany" id="id9" name="id9">About Geany</a></li>
+<li><a class="reference" href="#where-to-get-it" id="id10" name="id10">Where to get it</a></li>
+<li><a class="reference" href="#license" id="id11" name="id11">License</a></li>
+<li><a class="reference" href="#about-this-document" id="id12" name="id12">About this document</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#installation" id="id13">Installation</a><ul>
-<li><a class="reference internal" href="#requirements" id="id14">Requirements</a></li>
-<li><a class="reference internal" href="#binary-packages" id="id15">Binary packages</a></li>
-<li><a class="reference internal" href="#source-compilation" id="id16">Source compilation</a><ul>
-<li><a class="reference internal" href="#autotools-based-build-system" id="id17">Autotools based build system</a></li>
-<li><a class="reference internal" href="#waf-based-build-system" id="id18">Waf based build system</a><ul>
-<li><a class="reference internal" href="#waf-cache" id="id19">Waf Cache</a><ul>
-<li><a class="reference internal" href="#cleaning-the-cache" id="id20">Cleaning the Cache</a></li>
+<li><a class="reference" href="#installation" id="id13" name="id13">Installation</a><ul>
+<li><a class="reference" href="#requirements" id="id14" name="id14">Requirements</a></li>
+<li><a class="reference" href="#binary-packages" id="id15" name="id15">Binary packages</a></li>
+<li><a class="reference" href="#source-compilation" id="id16" name="id16">Source compilation</a><ul>
+<li><a class="reference" href="#autotools-based-build-system" id="id17" name="id17">Autotools based build system</a></li>
+<li><a class="reference" href="#waf-based-build-system" id="id18" name="id18">Waf based build system</a><ul>
+<li><a class="reference" href="#waf-cache" id="id19" name="id19">Waf Cache</a><ul>
+<li><a class="reference" href="#cleaning-the-cache" id="id20" name="id20">Cleaning the Cache</a></li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#custom-installation" id="id21">Custom installation</a></li>
-<li><a class="reference internal" href="#dynamic-linking-loader-support-and-vte" id="id22">Dynamic linking loader support and VTE</a></li>
-<li><a class="reference internal" href="#build-problems" id="id23">Build problems</a></li>
+<li><a class="reference" href="#custom-installation" id="id21" name="id21">Custom installation</a></li>
+<li><a class="reference" href="#dynamic-linking-loader-support-and-vte" id="id22" name="id22">Dynamic linking loader support and VTE</a></li>
+<li><a class="reference" href="#build-problems" id="id23" name="id23">Build problems</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#installation-prefix" id="id24">Installation prefix</a></li>
+<li><a class="reference" href="#installation-prefix" id="id24" name="id24">Installation prefix</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#usage" id="id25">Usage</a><ul>
-<li><a class="reference internal" href="#getting-started" id="id26">Getting started</a></li>
-<li><a class="reference internal" href="#the-geany-workspace" id="id27">The Geany workspace</a></li>
-<li><a class="reference internal" href="#command-line-options" id="id28">Command line options</a></li>
-<li><a class="reference internal" href="#general" id="id29">General</a><ul>
-<li><a class="reference internal" href="#startup" id="id30">Startup</a></li>
-<li><a class="reference internal" href="#opening-files-from-the-command-line-in-a-running-instance" id="id31">Opening files from the command-line in a running instance</a></li>
-<li><a class="reference internal" href="#virtual-terminal-emulator-widget-vte" id="id32">Virtual terminal emulator widget (VTE)</a></li>
-<li><a class="reference internal" href="#defining-own-widget-styles-using-gtkrc-2-0" id="id33">Defining own widget styles using .gtkrc-2.0</a></li>
+<li><a class="reference" href="#usage" id="id25" name="id25">Usage</a><ul>
+<li><a class="reference" href="#getting-started" id="id26" name="id26">Getting started</a></li>
+<li><a class="reference" href="#the-geany-workspace" id="id27" name="id27">The Geany workspace</a></li>
+<li><a class="reference" href="#command-line-options" id="id28" name="id28">Command line options</a></li>
+<li><a class="reference" href="#general" id="id29" name="id29">General</a><ul>
+<li><a class="reference" href="#startup" id="id30" name="id30">Startup</a></li>
+<li><a class="reference" href="#opening-files-from-the-command-line-in-a-running-instance" id="id31" name="id31">Opening files from the command-line in a running instance</a></li>
+<li><a class="reference" href="#virtual-terminal-emulator-widget-vte" id="id32" name="id32">Virtual terminal emulator widget (VTE)</a></li>
+<li><a class="reference" href="#defining-own-widget-styles-using-gtkrc-2-0" id="id33" name="id33">Defining own widget styles using .gtkrc-2.0</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#documents" id="id34">Documents</a><ul>
-<li><a class="reference internal" href="#switching-between-documents" id="id35">Switching between documents</a></li>
+<li><a class="reference" href="#documents" id="id34" name="id34">Documents</a><ul>
+<li><a class="reference" href="#switching-between-documents" id="id35" name="id35">Switching between documents</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#character-sets-and-unicode-byte-order-mark-bom" id="id36">Character sets and Unicode Byte-Order-Mark (BOM)</a><ul>
-<li><a class="reference internal" href="#using-character-sets" id="id37">Using character sets</a></li>
-<li><a class="reference internal" href="#in-file-encoding-specification" id="id38">In-file encoding specification</a></li>
-<li><a class="reference internal" href="#special-encoding-none" id="id39">Special encoding "None"</a></li>
-<li><a class="reference internal" href="#unicode-byte-order-mark-bom" id="id40">Unicode Byte-Order-Mark (BOM)</a></li>
+<li><a class="reference" href="#character-sets-and-unicode-byte-order-mark-bom" id="id36" name="id36">Character sets and Unicode Byte-Order-Mark (BOM)</a><ul>
+<li><a class="reference" href="#using-character-sets" id="id37" name="id37">Using character sets</a></li>
+<li><a class="reference" href="#in-file-encoding-specification" id="id38" name="id38">In-file encoding specification</a></li>
+<li><a class="reference" href="#special-encoding-none" id="id39" name="id39">Special encoding "None"</a></li>
+<li><a class="reference" href="#unicode-byte-order-mark-bom" id="id40" name="id40">Unicode Byte-Order-Mark (BOM)</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#editing" id="id41">Editing</a><ul>
-<li><a class="reference internal" href="#folding" id="id42">Folding</a></li>
-<li><a class="reference internal" href="#column-mode-editing-rectangular-selections" id="id43">Column mode editing (rectangular selections)</a></li>
-<li><a class="reference internal" href="#drag-and-drop-of-text" id="id44">Drag and drop of text</a></li>
-<li><a class="reference internal" href="#indentation" id="id45">Indentation</a></li>
-<li><a class="reference internal" href="#auto-indentation" id="id46">Auto-indentation</a></li>
-<li><a class="reference internal" href="#bookmarks" id="id47">Bookmarks</a></li>
-<li><a class="reference internal" href="#code-navigation-history" id="id48">Code navigation history</a></li>
-<li><a class="reference internal" href="#sending-text-through-custom-commands" id="id49">Sending text through custom commands</a></li>
-<li><a class="reference internal" href="#context-actions" id="id50">Context actions</a></li>
-<li><a class="reference internal" href="#autocompletion" id="id51">Autocompletion</a><ul>
-<li><a class="reference internal" href="#word-part-completion" id="id52">Word part completion</a></li>
-<li><a class="reference internal" href="#scope-autocompletion" id="id53">Scope autocompletion</a></li>
+<li><a class="reference" href="#editing" id="id41" name="id41">Editing</a><ul>
+<li><a class="reference" href="#folding" id="id42" name="id42">Folding</a></li>
+<li><a class="reference" href="#column-mode-editing-rectangular-selections" id="id43" name="id43">Column mode editing (rectangular selections)</a></li>
+<li><a class="reference" href="#drag-and-drop-of-text" id="id44" name="id44">Drag and drop of text</a></li>
+<li><a class="reference" href="#indentation" id="id45" name="id45">Indentation</a></li>
+<li><a class="reference" href="#auto-indentation" id="id46" name="id46">Auto-indentation</a></li>
+<li><a class="reference" href="#bookmarks" id="id47" name="id47">Bookmarks</a></li>
+<li><a class="reference" href="#code-navigation-history" id="id48" name="id48">Code navigation history</a></li>
+<li><a class="reference" href="#sending-text-through-custom-commands" id="id49" name="id49">Sending text through custom commands</a></li>
+<li><a class="reference" href="#context-actions" id="id50" name="id50">Context actions</a></li>
+<li><a class="reference" href="#autocompletion" id="id51" name="id51">Autocompletion</a><ul>
+<li><a class="reference" href="#word-part-completion" id="id52" name="id52">Word part completion</a></li>
+<li><a class="reference" href="#scope-autocompletion" id="id53" name="id53">Scope autocompletion</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#user-definable-snippets" id="id54">User-definable snippets</a></li>
-<li><a class="reference internal" href="#inserting-unicode-characters" id="id55">Inserting Unicode characters</a></li>
+<li><a class="reference" href="#user-definable-snippets" id="id54" name="id54">User-definable snippets</a></li>
+<li><a class="reference" href="#inserting-unicode-characters" id="id55" name="id55">Inserting Unicode characters</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#search-replace-and-go-to" id="id56">Search, replace and go to</a><ul>
-<li><a class="reference internal" href="#toolbar-entries" id="id57">Toolbar entries</a><ul>
-<li><a class="reference internal" href="#search-bar" id="id58">Search bar</a></li>
+<li><a class="reference" href="#search-replace-and-go-to" id="id56" name="id56">Search, replace and go to</a><ul>
+<li><a class="reference" href="#toolbar-entries" id="id57" name="id57">Toolbar entries</a><ul>
+<li><a class="reference" href="#search-bar" id="id58" name="id58">Search bar</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#find" id="id59">Find</a><ul>
-<li><a class="reference internal" href="#matching-options" id="id60">Matching options</a></li>
-<li><a class="reference internal" href="#find-all" id="id61">Find all</a></li>
-<li><a class="reference internal" href="#change-font-in-search-dialog-text-fields" id="id62">Change font in search dialog text fields</a></li>
+<li><a class="reference" href="#find" id="id59" name="id59">Find</a><ul>
+<li><a class="reference" href="#matching-options" id="id60" name="id60">Matching options</a></li>
+<li><a class="reference" href="#find-all" id="id61" name="id61">Find all</a></li>
+<li><a class="reference" href="#change-font-in-search-dialog-text-fields" id="id62" name="id62">Change font in search dialog text fields</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#find-usage" id="id63">Find usage</a></li>
-<li><a class="reference internal" href="#find-in-files" id="id64">Find in files</a><ul>
-<li><a class="reference internal" href="#filtering-out-version-control-files" id="id65">Filtering out version control files</a></li>
+<li><a class="reference" href="#find-usage" id="id63" name="id63">Find usage</a></li>
+<li><a class="reference" href="#find-in-files" id="id64" name="id64">Find in files</a><ul>
+<li><a class="reference" href="#filtering-out-version-control-files" id="id65" name="id65">Filtering out version control files</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#replace" id="id66">Replace</a><ul>
-<li><a class="reference internal" href="#replace-all" id="id67">Replace all</a></li>
+<li><a class="reference" href="#replace" id="id66" name="id66">Replace</a><ul>
+<li><a class="reference" href="#replace-all" id="id67" name="id67">Replace all</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#go-to-tag-definition" id="id68">Go to tag definition</a></li>
-<li><a class="reference internal" href="#go-to-tag-declaration" id="id69">Go to tag declaration</a></li>
-<li><a class="reference internal" href="#go-to-line" id="id70">Go to line</a></li>
-<li><a class="reference internal" href="#regular-expressions" id="id71">Regular expressions</a></li>
+<li><a class="reference" href="#go-to-tag-definition" id="id68" name="id68">Go to tag definition</a></li>
+<li><a class="reference" href="#go-to-tag-declaration" id="id69" name="id69">Go to tag declaration</a></li>
+<li><a class="reference" href="#go-to-line" id="id70" name="id70">Go to line</a></li>
+<li><a class="reference" href="#regular-expressions" id="id71" name="id71">Regular expressions</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#tags" id="id72">Tags</a><ul>
-<li><a class="reference internal" href="#workspace-tags" id="id73">Workspace tags</a></li>
-<li><a class="reference internal" href="#global-tags" id="id74">Global tags</a><ul>
-<li><a class="reference internal" href="#default-global-tags-files" id="id75">Default global tags files</a></li>
-<li><a class="reference internal" href="#global-tags-file-format" id="id76">Global tags file format</a></li>
-<li><a class="reference internal" href="#generating-a-global-tags-file" id="id77">Generating a global tags file</a></li>
+<li><a class="reference" href="#tags" id="id72" name="id72">Tags</a><ul>
+<li><a class="reference" href="#workspace-tags" id="id73" name="id73">Workspace tags</a></li>
+<li><a class="reference" href="#global-tags" id="id74" name="id74">Global tags</a><ul>
+<li><a class="reference" href="#default-global-tags-files" id="id75" name="id75">Default global tags files</a></li>
+<li><a class="reference" href="#global-tags-file-format" id="id76" name="id76">Global tags file format</a></li>
+<li><a class="reference" href="#generating-a-global-tags-file" id="id77" name="id77">Generating a global tags file</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#ignore-tags" id="id78">Ignore tags</a></li>
+<li><a class="reference" href="#ignore-tags" id="id78" name="id78">Ignore tags</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#preferences" id="id79">Preferences</a><ul>
-<li><a class="reference internal" href="#general-startup-preferences" id="id80">General Startup preferences</a><ul>
-<li><a class="reference internal" href="#id1" id="id81">Startup</a></li>
-<li><a class="reference internal" href="#shutdown" id="id82">Shutdown</a></li>
-<li><a class="reference internal" href="#paths" id="id83">Paths</a></li>
+<li><a class="reference" href="#preferences" id="id79" name="id79">Preferences</a><ul>
+<li><a class="reference" href="#general-startup-preferences" id="id80" name="id80">General Startup preferences</a><ul>
+<li><a class="reference" href="#id1" id="id81" name="id81">Startup</a></li>
+<li><a class="reference" href="#shutdown" id="id82" name="id82">Shutdown</a></li>
+<li><a class="reference" href="#paths" id="id83" name="id83">Paths</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#general-miscellaneous-preferences" id="id84">General Miscellaneous preferences</a><ul>
-<li><a class="reference internal" href="#miscellaneous" id="id85">Miscellaneous</a></li>
-<li><a class="reference internal" href="#search" id="id86">Search</a></li>
-<li><a class="reference internal" href="#projects" id="id87">Projects</a></li>
+<li><a class="reference" href="#general-miscellaneous-preferences" id="id84" name="id84">General Miscellaneous preferences</a><ul>
+<li><a class="reference" href="#miscellaneous" id="id85" name="id85">Miscellaneous</a></li>
+<li><a class="reference" href="#search" id="id86" name="id86">Search</a></li>
+<li><a class="reference" href="#projects" id="id87" name="id87">Projects</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#interface-preferences" id="id88">Interface preferences</a><ul>
-<li><a class="reference internal" href="#sidebar" id="id89">Sidebar</a></li>
-<li><a class="reference internal" href="#fonts" id="id90">Fonts</a></li>
-<li><a class="reference internal" href="#editor-tabs" id="id91">Editor tabs</a></li>
-<li><a class="reference internal" href="#tab-positions" id="id92">Tab positions</a></li>
-<li><a class="reference internal" href="#id2" id="id93">Miscellaneous</a></li>
+<li><a class="reference" href="#interface-preferences" id="id88" name="id88">Interface preferences</a><ul>
+<li><a class="reference" href="#sidebar" id="id89" name="id89">Sidebar</a></li>
+<li><a class="reference" href="#fonts" id="id90" name="id90">Fonts</a></li>
+<li><a class="reference" href="#editor-tabs" id="id91" name="id91">Editor tabs</a></li>
+<li><a class="reference" href="#tab-positions" id="id92" name="id92">Tab positions</a></li>
+<li><a class="reference" href="#id2" id="id93" name="id93">Miscellaneous</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#toolbar-preferences" id="id94">Toolbar preferences</a><ul>
-<li><a class="reference internal" href="#toolbar" id="id95">Toolbar</a></li>
-<li><a class="reference internal" href="#appearance" id="id96">Appearance</a></li>
+<li><a class="reference" href="#toolbar-preferences" id="id94" name="id94">Toolbar preferences</a><ul>
+<li><a class="reference" href="#toolbar" id="id95" name="id95">Toolbar</a></li>
+<li><a class="reference" href="#appearance" id="id96" name="id96">Appearance</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#editor-features-preferences" id="id97">Editor Features preferences</a><ul>
-<li><a class="reference internal" href="#features" id="id98">Features</a></li>
+<li><a class="reference" href="#editor-features-preferences" id="id97" name="id97">Editor Features preferences</a><ul>
+<li><a class="reference" href="#features" id="id98" name="id98">Features</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#editor-indentation-preferences" id="id99">Editor Indentation preferences</a><ul>
-<li><a class="reference internal" href="#indentation-group" id="id100">Indentation group</a></li>
+<li><a class="reference" href="#editor-indentation-preferences" id="id99" name="id99">Editor Indentation preferences</a><ul>
+<li><a class="reference" href="#indentation-group" id="id100" name="id100">Indentation group</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#editor-completions-preferences" id="id101">Editor Completions preferences</a><ul>
-<li><a class="reference internal" href="#completions" id="id102">Completions</a></li>
-<li><a class="reference internal" href="#auto-close-quotes-and-brackets" id="id103">Auto-close quotes and brackets</a></li>
+<li><a class="reference" href="#editor-completions-preferences" id="id101" name="id101">Editor Completions preferences</a><ul>
+<li><a class="reference" href="#completions" id="id102" name="id102">Completions</a></li>
+<li><a class="reference" href="#auto-close-quotes-and-brackets" id="id103" name="id103">Auto-close quotes and brackets</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#editor-display-preferences" id="id104">Editor Display preferences</a><ul>
-<li><a class="reference internal" href="#display" id="id105">Display</a></li>
-<li><a class="reference internal" href="#long-line-marker" id="id106">Long line marker</a></li>
-<li><a class="reference internal" href="#virtual-spaces" id="id107">Virtual spaces</a></li>
+<li><a class="reference" href="#editor-display-preferences" id="id104" name="id104">Editor Display preferences</a><ul>
+<li><a class="reference" href="#display" id="id105" name="id105">Display</a></li>
+<li><a class="reference" href="#long-line-marker" id="id106" name="id106">Long line marker</a></li>
+<li><a class="reference" href="#virtual-spaces" id="id107" name="id107">Virtual spaces</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#files-preferences" id="id108">Files preferences</a><ul>
-<li><a class="reference internal" href="#new-files" id="id109">New files</a></li>
-<li><a class="reference internal" href="#saving-files" id="id110">Saving files</a></li>
-<li><a class="reference internal" href="#id3" id="id111">Miscellaneous</a></li>
+<li><a class="reference" href="#files-preferences" id="id108" name="id108">Files preferences</a><ul>
+<li><a class="reference" href="#new-files" id="id109" name="id109">New files</a></li>
+<li><a class="reference" href="#saving-files" id="id110" name="id110">Saving files</a></li>
+<li><a class="reference" href="#id3" id="id111" name="id111">Miscellaneous</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#tools-preferences" id="id112">Tools preferences</a><ul>
-<li><a class="reference internal" href="#tool-paths" id="id113">Tool paths</a></li>
-<li><a class="reference internal" href="#commands" id="id114">Commands</a></li>
+<li><a class="reference" href="#tools-preferences" id="id112" name="id112">Tools preferences</a><ul>
+<li><a class="reference" href="#tool-paths" id="id113" name="id113">Tool paths</a></li>
+<li><a class="reference" href="#commands" id="id114" name="id114">Commands</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#template-preferences" id="id115">Template preferences</a><ul>
-<li><a class="reference internal" href="#template-data" id="id116">Template data</a></li>
+<li><a class="reference" href="#template-preferences" id="id115" name="id115">Template preferences</a><ul>
+<li><a class="reference" href="#template-data" id="id116" name="id116">Template data</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#keybinding-preferences" id="id117">Keybinding preferences</a></li>
-<li><a class="reference internal" href="#printing-preferences" id="id118">Printing preferences</a></li>
-<li><a class="reference internal" href="#terminal-vte-preferences" id="id119">Terminal (VTE) preferences</a><ul>
-<li><a class="reference internal" href="#terminal-widget" id="id120">Terminal widget</a></li>
+<li><a class="reference" href="#keybinding-preferences" id="id117" name="id117">Keybinding preferences</a></li>
+<li><a class="reference" href="#printing-preferences" id="id118" name="id118">Printing preferences</a></li>
+<li><a class="reference" href="#terminal-vte-preferences" id="id119" name="id119">Terminal (VTE) preferences</a><ul>
+<li><a class="reference" href="#terminal-widget" id="id120" name="id120">Terminal widget</a></li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#project-management" id="id121">Project Management</a><ul>
-<li><a class="reference internal" href="#new-project" id="id122">New Project</a></li>
-<li><a class="reference internal" href="#project-properties" id="id123">Project Properties</a><ul>
-<li><a class="reference internal" href="#set-base-path-button" id="id124">Set Base Path Button</a></li>
+<li><a class="reference" href="#project-management" id="id121" name="id121">Project Management</a><ul>
+<li><a class="reference" href="#new-project" id="id122" name="id122">New Project</a></li>
+<li><a class="reference" href="#project-properties" id="id123" name="id123">Project Properties</a><ul>
+<li><a class="reference" href="#set-base-path-button" id="id124" name="id124">Set Base Path Button</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#open-project" id="id125">Open Project</a></li>
-<li><a class="reference internal" href="#close-project" id="id126">Close Project</a></li>
+<li><a class="reference" href="#open-project" id="id125" name="id125">Open Project</a></li>
+<li><a class="reference" href="#close-project" id="id126" name="id126">Close Project</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#build-menu" id="id127">Build Menu</a><ul>
-<li><a class="reference internal" href="#indicators" id="id128">Indicators</a></li>
-<li><a class="reference internal" href="#default-build-menu-items" id="id129">Default Build Menu Items</a><ul>
-<li><a class="reference internal" href="#compile" id="id130">Compile</a></li>
-<li><a class="reference internal" href="#build" id="id131">Build</a></li>
-<li><a class="reference internal" href="#make" id="id132">Make</a></li>
-<li><a class="reference internal" href="#make-custom-target" id="id133">Make custom target</a></li>
-<li><a class="reference internal" href="#make-object" id="id134">Make object</a></li>
-<li><a class="reference internal" href="#next-error" id="id135">Next Error</a></li>
-<li><a class="reference internal" href="#previous-error" id="id136">Previous Error</a></li>
-<li><a class="reference internal" href="#execute" id="id137">Execute</a></li>
-<li><a class="reference internal" href="#stopping-running-processes" id="id138">Stopping running processes</a><ul>
-<li><a class="reference internal" href="#terminal-emulators" id="id139">Terminal emulators</a></li>
+<li><a class="reference" href="#build-menu" id="id127" name="id127">Build Menu</a><ul>
+<li><a class="reference" href="#indicators" id="id128" name="id128">Indicators</a></li>
+<li><a class="reference" href="#default-build-menu-items" id="id129" name="id129">Default Build Menu Items</a><ul>
+<li><a class="reference" href="#compile" id="id130" name="id130">Compile</a></li>
+<li><a class="reference" href="#build" id="id131" name="id131">Build</a></li>
+<li><a class="reference" href="#make" id="id132" name="id132">Make</a></li>
+<li><a class="reference" href="#make-custom-target" id="id133" name="id133">Make custom target</a></li>
+<li><a class="reference" href="#make-object" id="id134" name="id134">Make object</a></li>
+<li><a class="reference" href="#next-error" id="id135" name="id135">Next Error</a></li>
+<li><a class="reference" href="#previous-error" id="id136" name="id136">Previous Error</a></li>
+<li><a class="reference" href="#execute" id="id137" name="id137">Execute</a></li>
+<li><a class="reference" href="#stopping-running-processes" id="id138" name="id138">Stopping running processes</a><ul>
+<li><a class="reference" href="#terminal-emulators" id="id139" name="id139">Terminal emulators</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#set-build-commands" id="id140">Set Build Commands</a></li>
+<li><a class="reference" href="#set-build-commands" id="id140" name="id140">Set Build Commands</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#build-menu-configuration" id="id141">Build Menu Configuration</a></li>
-<li><a class="reference internal" href="#build-menu-commands-dialog" id="id142">Build Menu Commands Dialog</a><ul>
-<li><a class="reference internal" href="#substitutions-in-commands-and-working-directories" id="id143">Substitutions in Commands and Working Directories</a></li>
-<li><a class="reference internal" href="#build-menu-keyboard-shortcuts" id="id144">Build Menu Keyboard Shortcuts</a></li>
-<li><a class="reference internal" href="#configuration-files" id="id145">Configuration Files</a></li>
+<li><a class="reference" href="#build-menu-configuration" id="id141" name="id141">Build Menu Configuration</a></li>
+<li><a class="reference" href="#build-menu-commands-dialog" id="id142" name="id142">Build Menu Commands Dialog</a><ul>
+<li><a class="reference" href="#substitutions-in-commands-and-working-directories" id="id143" name="id143">Substitutions in Commands and Working Directories</a></li>
+<li><a class="reference" href="#build-menu-keyboard-shortcuts" id="id144" name="id144">Build Menu Keyboard Shortcuts</a></li>
+<li><a class="reference" href="#configuration-files" id="id145" name="id145">Configuration Files</a></li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#printing-support" id="id146">Printing support</a></li>
-<li><a class="reference internal" href="#plugins" id="id147">Plugins</a></li>
-<li><a class="reference internal" href="#keybindings" id="id148">Keybindings</a><ul>
-<li><a class="reference internal" href="#switching-documents" id="id149">Switching documents</a></li>
-<li><a class="reference internal" href="#configurable-keybindings" id="id150">Configurable keybindings</a><ul>
-<li><a class="reference internal" href="#file-keybindings" id="id151">File keybindings</a></li>
-<li><a class="reference internal" href="#editor-keybindings" id="id152">Editor keybindings</a></li>
-<li><a class="reference internal" href="#clipboard-keybindings" id="id153">Clipboard keybindings</a></li>
-<li><a class="reference internal" href="#select-keybindings" id="id154">Select keybindings</a></li>
-<li><a class="reference internal" href="#insert-keybindings" id="id155">Insert keybindings</a></li>
-<li><a class="reference internal" href="#format-keybindings" id="id156">Format keybindings</a></li>
-<li><a class="reference internal" href="#settings-keybindings" id="id157">Settings keybindings</a></li>
-<li><a class="reference internal" href="#search-keybindings" id="id158">Search keybindings</a></li>
-<li><a class="reference internal" href="#go-to-keybindings" id="id159">Go to keybindings</a></li>
-<li><a class="reference internal" href="#view-keybindings" id="id160">View keybindings</a></li>
-<li><a class="reference internal" href="#focus-keybindings" id="id161">Focus keybindings</a></li>
-<li><a class="reference internal" href="#notebook-tab-keybindings" id="id162">Notebook tab keybindings</a></li>
-<li><a class="reference internal" href="#document-keybindings" id="id163">Document keybindings</a></li>
-<li><a class="reference internal" href="#build-keybindings" id="id164">Build keybindings</a></li>
-<li><a class="reference internal" href="#tools-keybindings" id="id165">Tools keybindings</a></li>
-<li><a class="reference internal" href="#help-keybindings" id="id166">Help keybindings</a></li>
+<li><a class="reference" href="#printing-support" id="id146" name="id146">Printing support</a></li>
+<li><a class="reference" href="#plugins" id="id147" name="id147">Plugins</a></li>
+<li><a class="reference" href="#keybindings" id="id148" name="id148">Keybindings</a><ul>
+<li><a class="reference" href="#switching-documents" id="id149" name="id149">Switching documents</a></li>
+<li><a class="reference" href="#configurable-keybindings" id="id150" name="id150">Configurable keybindings</a><ul>
+<li><a class="reference" href="#file-keybindings" id="id151" name="id151">File keybindings</a></li>
+<li><a class="reference" href="#editor-keybindings" id="id152" name="id152">Editor keybindings</a></li>
+<li><a class="reference" href="#clipboard-keybindings" id="id153" name="id153">Clipboard keybindings</a></li>
+<li><a class="reference" href="#select-keybindings" id="id154" name="id154">Select keybindings</a></li>
+<li><a class="reference" href="#insert-keybindings" id="id155" name="id155">Insert keybindings</a></li>
+<li><a class="reference" href="#format-keybindings" id="id156" name="id156">Format keybindings</a></li>
+<li><a class="reference" href="#settings-keybindings" id="id157" name="id157">Settings keybindings</a></li>
+<li><a class="reference" href="#search-keybindings" id="id158" name="id158">Search keybindings</a></li>
+<li><a class="reference" href="#go-to-keybindings" id="id159" name="id159">Go to keybindings</a></li>
+<li><a class="reference" href="#view-keybindings" id="id160" name="id160">View keybindings</a></li>
+<li><a class="reference" href="#focus-keybindings" id="id161" name="id161">Focus keybindings</a></li>
+<li><a class="reference" href="#notebook-tab-keybindings" id="id162" name="id162">Notebook tab keybindings</a></li>
+<li><a class="reference" href="#document-keybindings" id="id163" name="id163">Document keybindings</a></li>
+<li><a class="reference" href="#build-keybindings" id="id164" name="id164">Build keybindings</a></li>
+<li><a class="reference" href="#tools-keybindings" id="id165" name="id165">Tools keybindings</a></li>
+<li><a class="reference" href="#help-keybindings" id="id166" name="id166">Help keybindings</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#id4" id="id167">Configuration files</a><ul>
-<li><a class="reference internal" href="#tools-menu-items" id="id168">Tools menu items</a></li>
-<li><a class="reference internal" href="#global-configuration-file" id="id169">Global configuration file</a></li>
-<li><a class="reference internal" href="#filetype-definition-files" id="id170">Filetype definition files</a><ul>
-<li><a class="reference internal" href="#custom-filetypes" id="id171">Custom filetypes</a></li>
-<li><a class="reference internal" href="#system-files" id="id172">System files</a></li>
-<li><a class="reference internal" href="#user-files" id="id173">User files</a></li>
-<li><a class="reference internal" href="#format" id="id174">Format</a><ul>
-<li><a class="reference internal" href="#styling-section" id="id175">[styling] Section</a><ul>
-<li><a class="reference internal" href="#using-a-named-style" id="id176">Using a named style</a></li>
+<li><a class="reference" href="#id4" id="id167" name="id167">Configuration files</a><ul>
+<li><a class="reference" href="#tools-menu-items" id="id168" name="id168">Tools menu items</a></li>
+<li><a class="reference" href="#global-configuration-file" id="id169" name="id169">Global configuration file</a></li>
+<li><a class="reference" href="#filetype-definition-files" id="id170" name="id170">Filetype definition files</a><ul>
+<li><a class="reference" href="#custom-filetypes" id="id171" name="id171">Custom filetypes</a></li>
+<li><a class="reference" href="#system-files" id="id172" name="id172">System files</a></li>
+<li><a class="reference" href="#user-files" id="id173" name="id173">User files</a></li>
+<li><a class="reference" href="#format" id="id174" name="id174">Format</a><ul>
+<li><a class="reference" href="#styling-section" id="id175" name="id175">[styling] Section</a><ul>
+<li><a class="reference" href="#using-a-named-style" id="id176" name="id176">Using a named style</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#keywords-section" id="id177">[keywords] Section</a></li>
-<li><a class="reference internal" href="#lexer-properties-section" id="id178">[lexer_properties] Section</a></li>
-<li><a class="reference internal" href="#settings-section" id="id179">[settings] Section</a></li>
-<li><a class="reference internal" href="#build-settings-section" id="id180">[build_settings] Section</a></li>
+<li><a class="reference" href="#keywords-section" id="id177" name="id177">[keywords] Section</a></li>
+<li><a class="reference" href="#lexer-properties-section" id="id178" name="id178">[lexer_properties] Section</a></li>
+<li><a class="reference" href="#settings-section" id="id179" name="id179">[settings] Section</a></li>
+<li><a class="reference" href="#build-settings-section" id="id180" name="id180">[build_settings] Section</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#special-file-filetypes-common" id="id181">Special file filetypes.common</a><ul>
-<li><a class="reference internal" href="#named-styles-section" id="id182">[named_styles] Section</a></li>
-<li><a class="reference internal" href="#id5" id="id183">[styling] Section</a></li>
-<li><a class="reference internal" href="#id6" id="id184">[settings] Section</a></li>
+<li><a class="reference" href="#special-file-filetypes-common" id="id181" name="id181">Special file filetypes.common</a><ul>
+<li><a class="reference" href="#named-styles-section" id="id182" name="id182">[named_styles] Section</a></li>
+<li><a class="reference" href="#id5" id="id183" name="id183">[styling] Section</a></li>
+<li><a class="reference" href="#id6" id="id184" name="id184">[settings] Section</a></li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#filetype-extensions" id="id185">Filetype extensions</a></li>
-<li><a class="reference internal" href="#preferences-file-format" id="id186">Preferences File Format</a><ul>
-<li><a class="reference internal" href="#hidden-preferences" id="id187">Hidden preferences</a></li>
-<li><a class="reference internal" href="#build-menu-section" id="id188">[build-menu] Section</a></li>
+<li><a class="reference" href="#filetype-extensions" id="id185" name="id185">Filetype extensions</a></li>
+<li><a class="reference" href="#preferences-file-format" id="id186" name="id186">Preferences File Format</a><ul>
+<li><a class="reference" href="#hidden-preferences" id="id187" name="id187">Hidden preferences</a></li>
+<li><a class="reference" href="#build-menu-section" id="id188" name="id188">[build-menu] Section</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#project-file-format" id="id189">Project File Format</a><ul>
-<li><a class="reference internal" href="#build-menu-additions" id="id190">[build-menu] Additions</a></li>
+<li><a class="reference" href="#project-file-format" id="id189" name="id189">Project File Format</a><ul>
+<li><a class="reference" href="#build-menu-additions" id="id190" name="id190">[build-menu] Additions</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#templates" id="id191">Templates</a><ul>
-<li><a class="reference internal" href="#template-meta-data" id="id192">Template meta data</a></li>
-<li><a class="reference internal" href="#file-templates" id="id193">File templates</a><ul>
-<li><a class="reference internal" href="#custom-file-templates" id="id194">Custom file templates</a></li>
-<li><a class="reference internal" href="#filetype-templates" id="id195">Filetype templates</a></li>
+<li><a class="reference" href="#templates" id="id191" name="id191">Templates</a><ul>
+<li><a class="reference" href="#template-meta-data" id="id192" name="id192">Template meta data</a></li>
+<li><a class="reference" href="#file-templates" id="id193" name="id193">File templates</a><ul>
+<li><a class="reference" href="#custom-file-templates" id="id194" name="id194">Custom file templates</a></li>
+<li><a class="reference" href="#filetype-templates" id="id195" name="id195">Filetype templates</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#customizing-templates" id="id196">Customizing templates</a><ul>
-<li><a class="reference internal" href="#template-wildcards" id="id197">Template wildcards</a><ul>
-<li><a class="reference internal" href="#special-command-wildcard" id="id198">Special {command:} wildcard</a></li>
+<li><a class="reference" href="#customizing-templates" id="id196" name="id196">Customizing templates</a><ul>
+<li><a class="reference" href="#template-wildcards" id="id197" name="id197">Template wildcards</a><ul>
+<li><a class="reference" href="#special-command-wildcard" id="id198" name="id198">Special {command:} wildcard</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#customizing-the-toolbar" id="id199">Customizing the toolbar</a><ul>
-<li><a class="reference internal" href="#manually-editing-of-the-toolbar-layout" id="id200">Manually editing of the toolbar layout</a></li>
-<li><a class="reference internal" href="#available-toolbar-elements" id="id201">Available toolbar elements</a></li>
+<li><a class="reference" href="#customizing-the-toolbar" id="id199" name="id199">Customizing the toolbar</a><ul>
+<li><a class="reference" href="#manually-editing-of-the-toolbar-layout" id="id200" name="id200">Manually editing of the toolbar layout</a></li>
+<li><a class="reference" href="#available-toolbar-elements" id="id201" name="id201">Available toolbar elements</a></li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#plugin-documentation" id="id202">Plugin documentation</a><ul>
-<li><a class="reference internal" href="#save-actions" id="id203">Save Actions</a><ul>
-<li><a class="reference internal" href="#instant-save" id="id204">Instant Save</a></li>
-<li><a class="reference internal" href="#backup-copy" id="id205">Backup Copy</a></li>
+<li><a class="reference" href="#plugin-documentation" id="id202" name="id202">Plugin documentation</a><ul>
+<li><a class="reference" href="#save-actions" id="id203" name="id203">Save Actions</a><ul>
+<li><a class="reference" href="#instant-save" id="id204" name="id204">Instant Save</a></li>
+<li><a class="reference" href="#backup-copy" id="id205" name="id205">Backup Copy</a></li>
</ul>
</li>
</ul>
</li>
-<li><a class="reference internal" href="#contributing-to-this-document" id="id206">Contributing to this document</a></li>
-<li><a class="reference internal" href="#scintilla-keyboard-commands" id="id207">Scintilla keyboard commands</a><ul>
-<li><a class="reference internal" href="#keyboard-commands" id="id208">Keyboard commands</a></li>
+<li><a class="reference" href="#contributing-to-this-document" id="id206" name="id206">Contributing to this document</a></li>
+<li><a class="reference" href="#scintilla-keyboard-commands" id="id207" name="id207">Scintilla keyboard commands</a><ul>
+<li><a class="reference" href="#keyboard-commands" id="id208" name="id208">Keyboard commands</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#tips-and-tricks" id="id209">Tips and tricks</a><ul>
-<li><a class="reference internal" href="#document-notebook" id="id210">Document notebook</a></li>
-<li><a class="reference internal" href="#editor" id="id211">Editor</a></li>
-<li><a class="reference internal" href="#interface" id="id212">Interface</a></li>
-<li><a class="reference internal" href="#gtk-related" id="id213">GTK-related</a></li>
+<li><a class="reference" href="#tips-and-tricks" id="id209" name="id209">Tips and tricks</a><ul>
+<li><a class="reference" href="#document-notebook" id="id210" name="id210">Document notebook</a></li>
+<li><a class="reference" href="#editor" id="id211" name="id211">Editor</a></li>
+<li><a class="reference" href="#interface" id="id212" name="id212">Interface</a></li>
+<li><a class="reference" href="#gtk-related" id="id213" name="id213">GTK-related</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#compile-time-options" id="id214">Compile-time options</a><ul>
-<li><a class="reference internal" href="#src-geany-h" id="id215">src/geany.h</a></li>
-<li><a class="reference internal" href="#project-h" id="id216">project.h</a></li>
-<li><a class="reference internal" href="#editor-h" id="id217">editor.h</a></li>
-<li><a class="reference internal" href="#keyfile-c" id="id218">keyfile.c</a></li>
-<li><a class="reference internal" href="#build-h" id="id219">build.h</a></li>
-<li><a class="reference internal" href="#build-c" id="id220">build.c</a></li>
+<li><a class="reference" href="#compile-time-options" id="id214" name="id214">Compile-time options</a><ul>
+<li><a class="reference" href="#src-geany-h" id="id215" name="id215">src/geany.h</a></li>
+<li><a class="reference" href="#project-h" id="id216" name="id216">project.h</a></li>
+<li><a class="reference" href="#editor-h" id="id217" name="id217">editor.h</a></li>
+<li><a class="reference" href="#keyfile-c" id="id218" name="id218">keyfile.c</a></li>
+<li><a class="reference" href="#build-h" id="id219" name="id219">build.h</a></li>
+<li><a class="reference" href="#build-c" id="id220" name="id220">build.c</a></li>
</ul>
</li>
-<li><a class="reference internal" href="#gnu-general-public-license" id="id221">GNU General Public License</a></li>
-<li><a class="reference internal" href="#license-for-scintilla-and-scite" id="id222">License for Scintilla and SciTE</a></li>
+<li><a class="reference" href="#gnu-general-public-license" id="id221" name="id221">GNU General Public License</a></li>
+<li><a class="reference" href="#license-for-scintilla-and-scite" id="id222" name="id222">License for Scintilla and SciTE</a></li>
</ul>
</div>
-<div class="section" id="introduction">
-<h1><a class="toc-backref" href="#id8">Introduction</a></h1>
-<div class="section" id="about-geany">
-<h2><a class="toc-backref" href="#id9">About Geany</a></h2>
+<div class="section">
+<h1><a class="toc-backref" href="#id8" id="introduction" name="introduction">Introduction</a></h1>
+<div class="section">
+<h2><a class="toc-backref" href="#id9" id="about-geany" name="about-geany">About Geany</a></h2>
<p>Geany is a small and lightweight Integrated Development Environment. It
was developed to provide a small and fast IDE, which has only a few
dependencies on other packages. Another goal was to be as independent
@@ -508,56 +508,56 @@
<li>Plugin interface</li>
</ul>
</div>
-<div class="section" id="where-to-get-it">
-<h2><a class="toc-backref" href="#id10">Where to get it</a></h2>
-<p>You can obtain Geany from <a class="reference external" href="http://www.geany.org/">http://www.geany.org/</a> or perhaps also from
+<div class="section">
+<h2><a class="toc-backref" href="#id10" id="where-to-get-it" name="where-to-get-it">Where to get it</a></h2>
+<p>You can obtain Geany from <a class="reference" href="http://www.geany.org/">http://www.geany.org/</a> or perhaps also from
your distribution. For a list of available packages, please see
-<a class="reference external" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
+<a class="reference" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
</div>
-<div class="section" id="license">
-<h2><a class="toc-backref" href="#id11">License</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id11" id="license" name="license">License</a></h2>
<p>Geany is distributed under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2 of
the License, or (at your option) any later version. A copy of this
license can be found in the file COPYING included with the source
-code of this program and in the chapter, <a class="reference internal" href="#gnu-general-public-license">GNU General Public License</a>.</p>
+code of this program and in the chapter, <a class="reference" href="#gnu-general-public-license">GNU General Public License</a>.</p>
<p>The included Scintilla library (found in the subdirectory
-<tt class="docutils literal">scintilla/</tt>) has its own license, which can be found in the chapter,
-<a class="reference internal" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
+<tt class="docutils literal"><span class="pre">scintilla/</span></tt>) has its own license, which can be found in the chapter,
+<a class="reference" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
</div>
-<div class="section" id="about-this-document">
-<h2><a class="toc-backref" href="#id12">About this document</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id12" id="about-this-document" name="about-this-document">About this document</a></h2>
<p>This documentation is available in HTML and text formats.
-The latest version can always be found at <a class="reference external" href="http://www.geany.org/">http://www.geany.org/</a>.</p>
-<p>If you want to contribute to it, see <a class="reference internal" href="#contributing-to-this-document">Contributing to this document</a>.</p>
+The latest version can always be found at <a class="reference" href="http://www.geany.org/">http://www.geany.org/</a>.</p>
+<p>If you want to contribute to it, see <a class="reference" href="#contributing-to-this-document">Contributing to this document</a>.</p>
</div>
</div>
-<div class="section" id="installation">
-<h1><a class="toc-backref" href="#id13">Installation</a></h1>
-<div class="section" id="requirements">
-<h2><a class="toc-backref" href="#id14">Requirements</a></h2>
+<div class="section">
+<h1><a class="toc-backref" href="#id13" id="installation" name="installation">Installation</a></h1>
+<div class="section">
+<h2><a class="toc-backref" href="#id14" id="requirements" name="requirements">Requirements</a></h2>
<p>You will need the GTK (>= 2.8.0) libraries and their dependencies
(Pango, GLib and ATK). Your distro should provide packages for these,
usually installed by default. For Windows, you can download an installer
from the website which bundles these libraries.</p>
</div>
-<div class="section" id="binary-packages">
-<h2><a class="toc-backref" href="#id15">Binary packages</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id15" id="binary-packages" name="binary-packages">Binary packages</a></h2>
<p>There are many binary packages available. For an up-to-date but maybe
-incomplete list see <a class="reference external" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
+incomplete list see <a class="reference" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
</div>
-<div class="section" id="source-compilation">
-<h2><a class="toc-backref" href="#id16">Source compilation</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id16" id="source-compilation" name="source-compilation">Source compilation</a></h2>
<p>Compiling Geany is quite easy.
To do so, you need the GTK (>= 2.8.0) libraries and header files.
You also need the Pango, GLib and ATK libraries and header files.
-All these files are available at <a class="reference external" href="http://www.gtk.org">http://www.gtk.org</a>, but very often
+All these files are available at <a class="reference" href="http://www.gtk.org">http://www.gtk.org</a>, but very often
your distro will provide development packages to save the trouble of
building these yourself.</p>
<p>Furthermore you need, of course, a C and C++ compiler. The GNU versions
of these tools are recommended.</p>
-<div class="section" id="autotools-based-build-system">
-<h3><a class="toc-backref" href="#id17">Autotools based build system</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id17" id="autotools-based-build-system" name="autotools-based-build-system">Autotools based build system</a></h3>
<p>The Autotools based build system is very mature and has been well tested.
To use it, you just need the Make tool, preferably GNU Make.</p>
<p>Then run the following commands:</p>
@@ -570,8 +570,8 @@
% make install
</pre>
</div>
-<div class="section" id="waf-based-build-system">
-<h3><a class="toc-backref" href="#id18">Waf based build system</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id18" id="waf-based-build-system" name="waf-based-build-system">Waf based build system</a></h3>
<p>The Waf build system is still quite young and under heavy development but already in a
usable state. In contrast to the Autotools system, Waf needs Python. So before using Waf, you need
to install Python on your system.
@@ -579,7 +579,7 @@
build process might be a bit faster. Especially when you use the Waf
cache feature for repetitive builds (e.g. when changing only a few source files
to test something) will become much faster since Waf will cache and re-use the
-unchanged built files and only compile the changed code again. See <a class="reference internal" href="#waf-cache">Waf Cache</a> for details.
+unchanged built files and only compile the changed code again. See <a class="reference" href="#waf-cache">Waf Cache</a> for details.
To build Geany with Waf as run:</p>
<pre class="literal-block">
$ ./waf configure
@@ -589,13 +589,13 @@
<pre class="literal-block">
% ./waf install
</pre>
-<div class="section" id="waf-cache">
-<h4><a class="toc-backref" href="#id19">Waf Cache</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id19" id="waf-cache" name="waf-cache">Waf Cache</a></h4>
<p>The Waf build system has a nice and interesting feature which can help to avoid
a lot of unnecessary rebuilding of unchanged code. This often happens when developing new features
or trying to debug something in Geany.
Waf is able to store and retrieve the object files from a cache. This cache is declared
-using the environment variable <tt class="docutils literal">WAFCACHE</tt>.
+using the environment variable <tt class="docutils literal"><span class="pre">WAFCACHE</span></tt>.
A possible location of the cache directory could be <tt class="docutils literal"><span class="pre">~/.cache/waf</span></tt>. In order to make use of
this, you first need to create this directory:</p>
<pre class="literal-block">
@@ -606,11 +606,11 @@
<pre class="literal-block">
export WAFCACHE=/home/username/.cache/waf
</pre>
-<p>Remember to replace <tt class="docutils literal">username</tt> with your actual username.</p>
+<p>Remember to replace <tt class="docutils literal"><span class="pre">username</span></tt> with your actual username.</p>
<p>More information about the Waf cache feature are available at
-<a class="reference external" href="http://code.google.com/p/waf/wiki/CacheObjectFiles">http://code.google.com/p/waf/wiki/CacheObjectFiles</a>.</p>
-<div class="section" id="cleaning-the-cache">
-<h5><a class="toc-backref" href="#id20">Cleaning the Cache</a></h5>
+<a class="reference" href="http://code.google.com/p/waf/wiki/CacheObjectFiles">http://code.google.com/p/waf/wiki/CacheObjectFiles</a>.</p>
+<div class="section">
+<h5><a class="toc-backref" href="#id20" id="cleaning-the-cache" name="cleaning-the-cache">Cleaning the Cache</a></h5>
<p>You should be careful about the size of the cache directory as it may
grow rapidly over time.
Waf doesn't do any cleaning or other house-keeping of the cache yet, so you need to keep it
@@ -621,12 +621,12 @@
$ find /home/username/.cache/waf -mtime +14 -exec rm {} \;
</pre>
<p>This will delete all files in the cache directory which are older than 14 days.</p>
-<p>For details about the <tt class="docutils literal">find</tt> command and its options, check its manual page.</p>
+<p>For details about the <tt class="docutils literal"><span class="pre">find</span></tt> command and its options, check its manual page.</p>
</div>
</div>
</div>
-<div class="section" id="custom-installation">
-<h3><a class="toc-backref" href="#id21">Custom installation</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id21" id="custom-installation" name="custom-installation">Custom installation</a></h3>
<p>The configure script supports several common options, for a detailed
list, type:</p>
<pre class="literal-block">
@@ -640,40 +640,40 @@
<p>You may also want to read the INSTALL file for advanced installation
options.</p>
<ul class="simple">
-<li>See also <a class="reference internal" href="#compile-time-options">Compile-time options</a>.</li>
+<li>See also <a class="reference" href="#compile-time-options">Compile-time options</a>.</li>
</ul>
</div>
-<div class="section" id="dynamic-linking-loader-support-and-vte">
-<h3><a class="toc-backref" href="#id22">Dynamic linking loader support and VTE</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id22" id="dynamic-linking-loader-support-and-vte" name="dynamic-linking-loader-support-and-vte">Dynamic linking loader support and VTE</a></h3>
<p>In the case that your system lacks dynamic linking loader support, you
-probably want to pass the option <tt class="docutils literal"><span class="pre">--disable-vte</span></tt> to the <tt class="docutils literal">configure</tt>
+probably want to pass the option <tt class="docutils literal"><span class="pre">--disable-vte</span></tt> to the <tt class="docutils literal"><span class="pre">configure</span></tt>
script. This prevents compiling Geany with dynamic linking loader
-support for automatically loading <tt class="docutils literal">libvte.so.4</tt> if available.</p>
+support for automatically loading <tt class="docutils literal"><span class="pre">libvte.so.4</span></tt> if available.</p>
</div>
-<div class="section" id="build-problems">
-<h3><a class="toc-backref" href="#id23">Build problems</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id23" id="build-problems" name="build-problems">Build problems</a></h3>
<p>If there are any errors during compilation, check your build
environment and try to find the error, otherwise contact the mailing
list or one the authors. Sometimes you might need to ask for specific
help from your distribution.</p>
</div>
</div>
-<div class="section" id="installation-prefix">
-<h2><a class="toc-backref" href="#id24">Installation prefix</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id24" id="installation-prefix" name="installation-prefix">Installation prefix</a></h2>
<p>If you want to edit any of Geany's system configuration files after
installation you will need to know the installation prefix. Usually this
is not necessary as you can just use per user configuration files and
you will not need root permissions.</p>
-<p>Use the <tt class="docutils literal"><span class="pre">--print-prefix</span></tt> option to Geany to check - see <a class="reference internal" href="#command-line-options">Command line
+<p>Use the <tt class="docutils literal"><span class="pre">--print-prefix</span></tt> option to Geany to check - see <a class="reference" href="#command-line-options">Command line
options</a>. The first path is the prefix.</p>
-<p>This is commonly <tt class="docutils literal">/usr</tt> if you installed from a binary package, or
-<tt class="docutils literal">/usr/local</tt> if you build from source.</p>
+<p>This is commonly <tt class="docutils literal"><span class="pre">/usr</span></tt> if you installed from a binary package, or
+<tt class="docutils literal"><span class="pre">/usr/local</span></tt> if you build from source.</p>
</div>
</div>
-<div class="section" id="usage">
-<h1><a class="toc-backref" href="#id25">Usage</a></h1>
-<div class="section" id="getting-started">
-<h2><a class="toc-backref" href="#id26">Getting started</a></h2>
+<div class="section">
+<h1><a class="toc-backref" href="#id25" id="usage" name="usage">Usage</a></h1>
+<div class="section">
+<h2><a class="toc-backref" href="#id26" id="getting-started" name="getting-started">Getting started</a></h2>
<p>You can start Geany in the following ways:</p>
<ul>
<li><p class="first">From the Desktop Environment menu:</p>
@@ -689,8 +689,8 @@
</li>
</ul>
</div>
-<div class="section" id="the-geany-workspace">
-<h2><a class="toc-backref" href="#id27">The Geany workspace</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id27" id="the-geany-workspace" name="the-geany-workspace">The Geany workspace</a></h2>
<p>The Geany window is shown in the following figure:</p>
<img alt="./images/main_window.png" src="./images/main_window.png" />
<p>The workspace has the following parts:</p>
@@ -718,8 +718,8 @@
<p>The sizes of the sidebar and message window can be adjusted by
dragging the dividers.</p>
</div>
-<div class="section" id="command-line-options">
-<h2><a class="toc-backref" href="#id28">Command line options</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id28" id="command-line-options" name="command-line-options">Command line options</a></h2>
<table border="1" class="docutils">
<colgroup>
<col width="9%" />
@@ -748,7 +748,7 @@
<td>--config=directory_name</td>
<td>Use an alternate configuration directory. The default
configuration directory is <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt> and that
-is where <tt class="docutils literal">geany.conf</tt> and other configuration files
+is where <tt class="docutils literal"><span class="pre">geany.conf</span></tt> and other configuration files
reside.</td>
</tr>
<tr><td><em>none</em></td>
@@ -759,7 +759,7 @@
<tr><td>-g</td>
<td>--generate-tags</td>
<td>Generate a global tags file (see
-<a class="reference internal" href="#generating-a-global-tags-file">Generating a global tags file</a>).</td>
+<a class="reference" href="#generating-a-global-tags-file">Generating a global tags file</a>).</td>
</tr>
<tr><td>-P</td>
<td>--no-preprocessing</td>
@@ -815,7 +815,7 @@
<td>--no-terminal</td>
<td>Do not load terminal support. Use this option if you do
not want to load the virtual terminal emulator widget
-at startup. If you do not have <tt class="docutils literal">libvte.so.4</tt> installed,
+at startup. If you do not have <tt class="docutils literal"><span class="pre">libvte.so.4</span></tt> installed,
then terminal-support is automatically disabled. Only
available if Geany was compiled with support for VTE.</td>
</tr>
@@ -833,7 +833,7 @@
<td>--vte-lib</td>
<td>Specify explicitly the path including filename or only
the filename to the VTE library, e.g.
-<tt class="docutils literal">/usr/lib/libvte.so</tt> or <tt class="docutils literal">libvte.so</tt>. This option is
+<tt class="docutils literal"><span class="pre">/usr/lib/libvte.so</span></tt> or <tt class="docutils literal"><span class="pre">libvte.so</span></tt>. This option is
only needed when the auto-detection does not work. Only
available if Geany was compiled with support for VTE.</td>
</tr>
@@ -872,13 +872,13 @@
<p>Geany supports all generic GTK options, a list is available on the
help screen.</p>
</div>
-<div class="section" id="general">
-<h2><a class="toc-backref" href="#id29">General</a></h2>
-<div class="section" id="startup">
-<h3><a class="toc-backref" href="#id30">Startup</a></h3>
+<div class="section">
+<h2><a class="toc-backref" href="#id29" id="general" name="general">General</a></h2>
+<div class="section">
+<h3><a class="toc-backref" href="#id30" id="startup" name="startup">Startup</a></h3>
<p>At startup, Geany loads all files from the last time Geany was
launched. You can disable this feature in the preferences dialog
-(see <a class="reference internal" href="#general-startup-preferences">General Startup preferences</a>). If you specify some
+(see <a class="reference" href="#general-startup-preferences">General Startup preferences</a>). If you specify some
files on the command line, only these files will be opened, but you
can find the files from the last session in the file menu under the
"Recent files" item. By default this contains the last 10 recently
@@ -889,8 +889,8 @@
do not specify any filenames on the command-line, or disable opening
files in a running instance using the appropriate command line option.</p>
</div>
-<div class="section" id="opening-files-from-the-command-line-in-a-running-instance">
-<h3><a class="toc-backref" href="#id31">Opening files from the command-line in a running instance</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id31" id="opening-files-from-the-command-line-in-a-running-instance" name="opening-files-from-the-command-line-in-a-running-instance">Opening files from the command-line in a running instance</a></h3>
<p>Geany detects if there is an an instance of itself already running and opens files
from the command-line in that instance. So, Geany can
be used to view and edit files by opening them from other programs
@@ -899,22 +899,22 @@
<pre class="literal-block">
geany some_file.foo:55:4
</pre>
-<p>This would open the file <tt class="docutils literal">some_file.foo</tt> with the cursor on line 55,
+<p>This would open the file <tt class="docutils literal"><span class="pre">some_file.foo</span></tt> with the cursor on line 55,
column 4.</p>
<p>If you do not like this for some reason, you can disable using the first
instance by using the appropriate command line option -- see the section
-called <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
+called <a class="reference" href="#command-line-options">Command line options</a>.</p>
</div>
-<div class="section" id="virtual-terminal-emulator-widget-vte">
-<h3><a class="toc-backref" href="#id32">Virtual terminal emulator widget (VTE)</a></h3>
-<p>If you have installed <tt class="docutils literal">libvte.so</tt> on your system, it is loaded
+<div class="section">
+<h3><a class="toc-backref" href="#id32" id="virtual-terminal-emulator-widget-vte" name="virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a></h3>
+<p>If you have installed <tt class="docutils literal"><span class="pre">libvte.so</span></tt> on your system, it is loaded
automatically by Geany, and you will have a terminal widget in the
notebook at the bottom.</p>
-<p>If Geany cannot find any <tt class="docutils literal">libvte.so</tt> at startup, the terminal widget
+<p>If Geany cannot find any <tt class="docutils literal"><span class="pre">libvte.so</span></tt> at startup, the terminal widget
will not be loaded. So there is no need to install the package containing
this file in order to run Geany. Additionally, you can disable the use
of the terminal widget by command line option, for more information
-see the section called <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
+see the section called <a class="reference" href="#command-line-options">Command line options</a>.</p>
<p>You can use this terminal (from now on called VTE) much as you would
a terminal program like xterm. There is basic clipboard support. You
can paste the contents of the clipboard by pressing the right mouse
@@ -931,26 +931,26 @@
you can use the argument <tt class="docutils literal"><span class="pre">--login</span></tt>.</p>
<div class="note">
<p class="first admonition-title">Note</p>
-<p class="last">Geany tries to load <tt class="docutils literal">libvte.so</tt>. If this fails, it tries to load
+<p class="last">Geany tries to load <tt class="docutils literal"><span class="pre">libvte.so</span></tt>. If this fails, it tries to load
some other filenames. If this fails too, you should check whether you
installed libvte correctly. Again note, Geany will run without this
library.</p>
</div>
<p>It could be, that the library is called something else than
-<tt class="docutils literal">libvte.so</tt> (e.g. on FreeBSD 6.0 it is called <tt class="docutils literal">libvte.so.8</tt>). If so
+<tt class="docutils literal"><span class="pre">libvte.so</span></tt> (e.g. on FreeBSD 6.0 it is called <tt class="docutils literal"><span class="pre">libvte.so.8</span></tt>). If so
please set a link to the correct file (as root):</p>
<pre class="literal-block">
# ln -s /usr/lib/libvte.so.X /usr/lib/libvte.so
</pre>
<p>Obviously, you have to adjust the paths and set X to the number of your
-<tt class="docutils literal">libvte.so</tt>.</p>
+<tt class="docutils literal"><span class="pre">libvte.so</span></tt>.</p>
<p>You can also specify the filename of the VTE library to use on the command
-line (see the section called <a class="reference internal" href="#command-line-options">Command line options</a>) or at compile time
+line (see the section called <a class="reference" href="#command-line-options">Command line options</a>) or at compile time
by specifying the command line option <tt class="docutils literal"><span class="pre">--with-vte-module-path</span></tt> to
./configure.</p>
</div>
-<div class="section" id="defining-own-widget-styles-using-gtkrc-2-0">
-<h3><a class="toc-backref" href="#id33">Defining own widget styles using .gtkrc-2.0</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id33" id="defining-own-widget-styles-using-gtkrc-2-0" name="defining-own-widget-styles-using-gtkrc-2-0">Defining own widget styles using .gtkrc-2.0</a></h3>
<p>You can define your widget style for many of Geany's GUI parts. To
do this, just edit your <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt> (usually found in your home
directory on UNIX-like systems and in the etc subdirectory of your
@@ -990,10 +990,10 @@
</pre>
</div>
</div>
-<div class="section" id="documents">
-<h2><a class="toc-backref" href="#id34">Documents</a></h2>
-<div class="section" id="switching-between-documents">
-<h3><a class="toc-backref" href="#id35">Switching between documents</a></h3>
+<div class="section">
+<h2><a class="toc-backref" href="#id34" id="documents" name="documents">Documents</a></h2>
+<div class="section">
+<h3><a class="toc-backref" href="#id35" id="switching-between-documents" name="switching-between-documents">Switching between documents</a></h3>
<p>The documents list and the editor tabs are two different ways
to switch between documents using the mouse. When you hit the key
combination to move between tabs, the order is determined by the tab
@@ -1001,14 +1001,14 @@
(regardless of whether or not editor tabs are visible).</p>
<p>The tabs can be positioned at the top, bottom, left, or right of the
main editing window, by a selection in the interface preferences.</p>
-<p>See the <a class="reference internal" href="#notebook-tab-keybindings">Notebook tab keybindings</a> section for useful
+<p>See the <a class="reference" href="#notebook-tab-keybindings">Notebook tab keybindings</a> section for useful
shortcuts including for Most-Recently-Used document switching.</p>
</div>
</div>
-<div class="section" id="character-sets-and-unicode-byte-order-mark-bom">
-<h2><a class="toc-backref" href="#id36">Character sets and Unicode Byte-Order-Mark (BOM)</a></h2>
-<div class="section" id="using-character-sets">
-<h3><a class="toc-backref" href="#id37">Using character sets</a></h3>
+<div class="section">
+<h2><a class="toc-backref" href="#id36" id="character-sets-and-unicode-byte-order-mark-bom" name="character-sets-and-unicode-byte-order-mark-bom">Character sets and Unicode Byte-Order-Mark (BOM)</a></h2>
+<div class="section">
+<h3><a class="toc-backref" href="#id37" id="using-character-sets" name="using-character-sets">Using character sets</a></h3>
<p>Geany provides support for detecting and converting character sets. So
you can open and save files in different character sets, and even
convert a file from one character set to another. To do this,
@@ -1054,8 +1054,8 @@
</li>
</ul>
</div>
-<div class="section" id="in-file-encoding-specification">
-<h3><a class="toc-backref" href="#id38">In-file encoding specification</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id38" id="in-file-encoding-specification" name="in-file-encoding-specification">In-file encoding specification</a></h3>
<p>Geany detects meta tags of HTML files which contain charset information
like:</p>
<pre class="literal-block">
@@ -1082,7 +1082,7 @@
correctly the next time.</p>
<p>Since Geany 0.15 you can also use lines which match the
regular expression used to find the encoding string:
-<tt class="docutils literal"><span class="pre">coding[\t</span> <span class="pre">]*[:=][\t</span> <span class="pre">]*([a-z0-9-]+)[\t</span> ]*</tt></p>
+<tt class="docutils literal"><span class="pre">coding[\t</span> <span class="pre">]*[:=][\t</span> <span class="pre">]*([a-z0-9-]+)[\t</span> <span class="pre">]*</span></tt></p>
<div class="note">
<p class="first admonition-title">Note</p>
<p class="last">These specifications must be in the first 512 bytes of the file.
@@ -1097,8 +1097,8 @@
# coding: ISO-8859-15
</pre>
</div>
-<div class="section" id="special-encoding-none">
-<h3><a class="toc-backref" href="#id39">Special encoding "None"</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id39" id="special-encoding-none" name="special-encoding-none">Special encoding "None"</a></h3>
<p>There is a special encoding "None" which uses no
encoding. It is useful when you know that Geany cannot auto-detect
the encoding of a file and it is not displayed correctly. Especially
@@ -1107,10 +1107,10 @@
of the first NULL-byte. Using this encoding opens the file as it is
without any character conversion.</p>
</div>
-<div class="section" id="unicode-byte-order-mark-bom">
-<h3><a class="toc-backref" href="#id40">Unicode Byte-Order-Mark (BOM)</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id40" id="unicode-byte-order-mark-bom" name="unicode-byte-order-mark-bom">Unicode Byte-Order-Mark (BOM)</a></h3>
<p>Furthermore, Geany detects a Unicode Byte Order Mark (see
-<a class="reference external" href="http://en.wikipedia.org/wiki/Byte_Order_Mark">http://en.wikipedia.org/wiki/Byte_Order_Mark</a> for details). Of course,
+<a class="reference" href="http://en.wikipedia.org/wiki/Byte_Order_Mark">http://en.wikipedia.org/wiki/Byte_Order_Mark</a> for details). Of course,
this feature is only available if the opened file is in a Unicode
encoding. The Byte Order Mark helps to detect the encoding of a file,
e.g. whether it is UTF-16LE or UTF-16BE and so on. On Unix-like systems
@@ -1130,10 +1130,10 @@
</div>
</div>
</div>
-<div class="section" id="editing">
-<h2><a class="toc-backref" href="#id41">Editing</a></h2>
-<div class="section" id="folding">
-<h3><a class="toc-backref" href="#id42">Folding</a></h3>
+<div class="section">
+<h2><a class="toc-backref" href="#id41" id="editing" name="editing">Editing</a></h2>
+<div class="section">
+<h3><a class="toc-backref" href="#id42" id="folding" name="folding">Folding</a></h3>
<p>Geany provides basic code folding support. Folding means the ability to
show and hide parts of the text in the current file. You can hide
unimportant code sections and concentrate on the parts you are working on
@@ -1147,7 +1147,7 @@
<div class="note">
<p class="first admonition-title">Note</p>
<p class="last">You can customize the folding icon and line styles - see the
-filetypes.common <a class="reference internal" href="#folding-settings">Folding Settings</a>.</p>
+filetypes.common <a class="reference" href="#folding-settings">Folding Settings</a>.</p>
</div>
<p>If you don't like it or don't need it at all, you can simply disable
folding support completely in the preferences dialog.</p>
@@ -1162,8 +1162,8 @@
children of a fold point" option is enabled, pressing Shift will disable
it for this click and vice versa.</p>
</div>
-<div class="section" id="column-mode-editing-rectangular-selections">
-<h3><a class="toc-backref" href="#id43">Column mode editing (rectangular selections)</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id43" id="column-mode-editing-rectangular-selections" name="column-mode-editing-rectangular-selections">Column mode editing (rectangular selections)</a></h3>
<p>There is basic support for column mode editing. To use it, create a
rectangular selection by holding down the Control and Shift keys
(or Control and Alt if it doesn't work) while
@@ -1172,18 +1172,18 @@
this selection and the modifications will be done for every line in the
selection.</p>
</div>
-<div class="section" id="drag-and-drop-of-text">
-<h3><a class="toc-backref" href="#id44">Drag and drop of text</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id44" id="drag-and-drop-of-text" name="drag-and-drop-of-text">Drag and drop of text</a></h3>
<p>If you drag selected text in the editor widget of Geany the text is
moved to the position where the mouse pointer is when releasing the
mouse button. Holding Control when releasing the mouse button will
copy the text instead. This behaviour was changed in Geany 0.11 -
before the selected text was copied to the new position.</p>
</div>
-<div class="section" id="indentation">
-<h3><a class="toc-backref" href="#id45">Indentation</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id45" id="indentation" name="indentation">Indentation</a></h3>
<p>Geany allows each document to indent either with a tab character or
-multiple spaces. The default indent mode is set in the <a class="reference internal" href="#editor-features-preferences">Editor Features
+multiple spaces. The default indent mode is set in the <a class="reference" href="#editor-features-preferences">Editor Features
preferences</a> (see the link for more information). But
this can be overridden using either the <em>Document->Indent Type</em> menu,
or by using the <em>Detect from file</em> indentation preference. When enabled,
@@ -1201,8 +1201,8 @@
on a line.</dd>
</dl>
</div>
-<div class="section" id="auto-indentation">
-<h3><a class="toc-backref" href="#id46">Auto-indentation</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id46" id="auto-indentation" name="auto-indentation">Auto-indentation</a></h3>
<p>When enabled, auto-indentation happens when pressing <em>Enter</em> in the
Editor. It adds a certain amount of indentation to the new line so the
user doesn't always have to indent each line manually.</p>
@@ -1222,8 +1222,8 @@
match the indentation of the line with the opening brace.</dd>
</dl>
</div>
-<div class="section" id="bookmarks">
-<h3><a class="toc-backref" href="#id47">Bookmarks</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id47" id="bookmarks" name="bookmarks">Bookmarks</a></h3>
<p>Geany provides a handy bookmarking feature that lets you mark one
or more lines in a document, and return the cursor to them using a
key combination.</p>
@@ -1240,14 +1240,14 @@
(Ctrl-PgUp/PgDn and Ctrl-Tab) provides a particularly fast way to
navigate around multiple files.</p>
</div>
-<div class="section" id="code-navigation-history">
-<h3><a class="toc-backref" href="#id48">Code navigation history</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id48" id="code-navigation-history" name="code-navigation-history">Code navigation history</a></h3>
<p>To ease navigation in source files and especially between
different files, Geany lets you jump between different navigation
points. Currently, this works for the following:</p>
<ul class="simple">
-<li><a class="reference internal" href="#go-to-tag-declaration">Go to tag declaration</a></li>
-<li><a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a></li>
+<li><a class="reference" href="#go-to-tag-declaration">Go to tag declaration</a></li>
+<li><a class="reference" href="#go-to-tag-definition">Go to tag definition</a></li>
<li>Symbol list items</li>
<li>Build errors</li>
<li>Message items</li>
@@ -1259,8 +1259,8 @@
location". This makes it easier to navigate in e.g. foreign code
and between different files.</p>
</div>
-<div class="section" id="sending-text-through-custom-commands">
-<h3><a class="toc-backref" href="#id49">Sending text through custom commands</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id49" id="sending-text-through-custom-commands" name="sending-text-through-custom-commands">Sending text through custom commands</a></h3>
<p>You can define several custom commands in Geany and send the current
selection to one of these commands using the "Edit->Format->Send
Selection to" menu or keybindings.
@@ -1278,17 +1278,17 @@
some command line options. To delete a command, just clear the text
entry and press OK. It will be deleted automatically.</p>
</div>
-<div class="section" id="context-actions">
-<h3><a class="toc-backref" href="#id50">Context actions</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id50" id="context-actions" name="context-actions">Context actions</a></h3>
<p>You can execute the context action command on the current word at the
cursor position or the available selection. This word or selection
can be used as an argument to the command.
The context action is invoked by a menu entry in the popup menu of the
editor and also a keyboard shortcut (see the section called
-<a class="reference internal" href="#keybindings">Keybindings</a>).</p>
+<a class="reference" href="#keybindings">Keybindings</a>).</p>
<p>The command can be specified in the preferences dialog and also for
each filetype (see "context_action_cmd" in the section called
-<a class="reference internal" href="#format">Format</a>). When the context action is invoked, the filetype
+<a class="reference" href="#format">Format</a>). When the context action is invoked, the filetype
specific command is used if available, otherwise the command
specified in the preferences dialog is executed.</p>
<p>The current word or selection can be referred with the wildcard "%s"
@@ -1303,19 +1303,19 @@
<p>when executing the command, the %s is substituted by the word near
the cursor position or by the current selection. If the cursor is at
the word "echo", a browser window will open(assumed your browser is
-called firefox) and it will open the address: <a class="reference external" href="http://www.php.net/echo">http://www.php.net/echo</a>.</p>
+called firefox) and it will open the address: <a class="reference" href="http://www.php.net/echo">http://www.php.net/echo</a>.</p>
</div>
-<div class="section" id="autocompletion">
-<h3><a class="toc-backref" href="#id51">Autocompletion</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id51" id="autocompletion" name="autocompletion">Autocompletion</a></h3>
<p>Geany can offer a list of possible completions for symbols defined in the
tags and for all words in a document.</p>
<p>The autocompletion list for symbols is presented when the first few
-characters of the symbol are typed (configurable, see <a class="reference internal" href="#editor-completions-preferences">Editor Completions
+characters of the symbol are typed (configurable, see <a class="reference" href="#editor-completions-preferences">Editor Completions
preferences</a>, default 4) or when the <em>Complete word</em>
-keybinding is pressed (configurable, see <a class="reference internal" href="#editor-keybindings">Editor keybindings</a>,
+keybinding is pressed (configurable, see <a class="reference" href="#editor-keybindings">Editor keybindings</a>,
default Ctrl-Space).</p>
<p>When the defined keybinding is typed and the <em>Autocomplete all words in
-document</em> preference (in <a class="reference internal" href="#editor-completions-preferences">Editor Completions preferences</a>)
+document</em> preference (in <a class="reference" href="#editor-completions-preferences">Editor Completions preferences</a>)
is selected then the autocompletion list will show all matching words
in the document, if there are no matching symbols.</p>
<p>If you don't want to use autocompletion it can be dismissed until
@@ -1327,13 +1327,13 @@
item on the autocompletion list can be chosen from the list by pressing
Enter/Return. You can also double-click to select an item. The sequence
will be completed to match the chosen item, and if the <em>Drop rest of
-word on completion</em> preference is set (in <a class="reference internal" href="#editor-completions-preferences">Editor Completions
+word on completion</em> preference is set (in <a class="reference" href="#editor-completions-preferences">Editor Completions
preferences</a>) then any characters after the cursor that match
a symbol or word are deleted.</p>
-<div class="section" id="word-part-completion">
-<h4><a class="toc-backref" href="#id52">Word part completion</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id52" id="word-part-completion" name="word-part-completion">Word part completion</a></h4>
<p>By default, pressing Tab will complete the selected item by word part;
-useful e.g. for adding the prefix <tt class="docutils literal">gtk_combo_box_entry_</tt> without typing it
+useful e.g. for adding the prefix <tt class="docutils literal"><span class="pre">gtk_combo_box_entry_</span></tt> without typing it
manually:</p>
<ul class="simple">
<li>gtk_com<TAB></li>
@@ -1342,12 +1342,12 @@
<li>gtk_combo_box_entry_<s><ENTER></li>
<li>gtk_combo_box_entry_set_text_column</li>
</ul>
-<p>The key combination can be changed from Tab - See <a class="reference internal" href="#editor-keybindings">Editor keybindings</a>.
+<p>The key combination can be changed from Tab - See <a class="reference" href="#editor-keybindings">Editor keybindings</a>.
If you clear/change the key combination for word part completion, Tab
will complete the whole word instead, like Enter.</p>
</div>
-<div class="section" id="scope-autocompletion">
-<h4><a class="toc-backref" href="#id53">Scope autocompletion</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id53" id="scope-autocompletion" name="scope-autocompletion">Scope autocompletion</a></h4>
<p>E.g.:</p>
<pre class="literal-block">
struct
@@ -1356,7 +1356,7 @@
char c;
} foo;
</pre>
-<p>When you type <tt class="docutils literal">foo.</tt> it will show an autocompletion list with 'i' and
+<p>When you type <tt class="docutils literal"><span class="pre">foo.</span></tt> it will show an autocompletion list with 'i' and
'c' symbols.</p>
<p>It only works for languages that set parent scope names for e.g. struct
members. Currently this means C-like languages. The C tag parser only
@@ -1364,27 +1364,27 @@
in local scope.</p>
</div>
</div>
-<div class="section" id="user-definable-snippets">
-<h3><a class="toc-backref" href="#id54">User-definable snippets</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id54" id="user-definable-snippets" name="user-definable-snippets">User-definable snippets</a></h3>
<p>Snippets are small strings or code constructs which can be replaced or
completed to a more complex string. So you can save a lot of time when
typing common strings and letting Geany do the work for you.
To know what to complete or replace Geany reads a configuration file
-called <tt class="docutils literal">snippets.conf</tt> at startup.</p>
+called <tt class="docutils literal"><span class="pre">snippets.conf</span></tt> at startup.</p>
<p>Maybe you need to often type your name, so define a snippet like this:</p>
<pre class="literal-block">
[Default]
myname=Enrico Tröger
</pre>
-<p>Every time you write <tt class="docutils literal">myname</tt> <TAB> in Geany, it will replace "myname"
+<p>Every time you write <tt class="docutils literal"><span class="pre">myname</span></tt> <TAB> in Geany, it will replace "myname"
with "Enrico Tröger". The key to start autocompletion can be changed
in the preferences dialog, by default it is TAB. The corresponding keybinding
-is called <tt class="docutils literal">Complete snippet</tt>.</p>
+is called <tt class="docutils literal"><span class="pre">Complete</span> <span class="pre">snippet</span></tt>.</p>
<p>The system-wide configuration file can be found in
-<tt class="docutils literal">$prefix/share/geany</tt>, where <tt class="docutils literal">$prefix</tt> is the path where Geany is
-installed (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>). It is not recommended to edit the
+<tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>, where <tt class="docutils literal"><span class="pre">$prefix</span></tt> is the path where Geany is
+installed (see <a class="reference" href="#installation-prefix">Installation prefix</a>). It is not recommended to edit the
system-wide file, because it will be overridden when Geany is updated.</p>
-<p>To change the settings, copy the file from <tt class="docutils literal">$prefix/share/geany</tt>
+<p>To change the settings, copy the file from <tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>
in your configuration directory (usually <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt>).</p>
<p>For example:</p>
<pre class="literal-block">
@@ -1395,15 +1395,15 @@
configuration directory. Alternatively, you can create a file
<tt class="docutils literal"><span class="pre">~/.config/geany/snippets.conf</span></tt> and add only these settings you want
to change. All missing settings will be read from the global snippets
-file in <tt class="docutils literal">$prefix/share/geany</tt>.</p>
-<p>The file <tt class="docutils literal">snippets.conf</tt> contains sections defining snippets that
+file in <tt class="docutils literal"><span class="pre">$prefix/share/geany</span></tt>.</p>
+<p>The file <tt class="docutils literal"><span class="pre">snippets.conf</span></tt> contains sections defining snippets that
are available for particular filetypes and in general.</p>
<p>The two sections "Default" and "Special" apply to all filetypes.
"Default" contains all snippets which are available for every
filetype and "Special" contains snippets which can only be used in
other snippets. So you can define often used parts of snippets and
just use the special snippet as a placeholder (see the
-<tt class="docutils literal">snippets.conf</tt> for details).</p>
+<tt class="docutils literal"><span class="pre">snippets.conf</span></tt> for details).</p>
<p>You can define sections with the name of a filetype eg "C++". The
snippets in that section are only available for use in files with that
filetype. Snippets in filetype sections will hide snippets with the
@@ -1433,7 +1433,7 @@
<tr><td>%cursor%</td>
<td>Place the cursor at this position after completion has
been done. You can define multiple %cursor% wildcards
-and use the keybinding <tt class="docutils literal">Move cursor in snippet</tt> to jump
+and use the keybinding <tt class="docutils literal"><span class="pre">Move</span> <span class="pre">cursor</span> <span class="pre">in</span> <span class="pre">snippet</span></tt> to jump
to the next defined cursor position in the completed
snippet.</td>
</tr>
@@ -1447,18 +1447,18 @@
<p>Snippet names must not contain spaces otherwise they won't
work correctly. But beside that you can define almost any
string as a snippet and use it later in Geany. It is not limited
-to existing contructs of certain programming languages(like <tt class="docutils literal">if</tt>,
-<tt class="docutils literal">for</tt>, <tt class="docutils literal">switch</tt>). Define whatever you need.</p>
+to existing contructs of certain programming languages(like <tt class="docutils literal"><span class="pre">if</span></tt>,
+<tt class="docutils literal"><span class="pre">for</span></tt>, <tt class="docutils literal"><span class="pre">switch</span></tt>). Define whatever you need.</p>
<p>Since Geany 0.15 you can also use most of the available templates wildcards
-listed in <a class="reference internal" href="#template-wildcards">Template wildcards</a>. All wildcards which are listed as
+listed in <a class="reference" href="#template-wildcards">Template wildcards</a>. All wildcards which are listed as
<cite>available in snippets</cite> can be used. For instance to improve the above example:</p>
<pre class="literal-block">
[Default]
myname=My name is {developer}
mysystem=My system: {command:uname -a}
</pre>
-<p>this will replace <tt class="docutils literal">myname</tt> with "My name is " and the value of the template
-preference <tt class="docutils literal">developer</tt>.</p>
+<p>this will replace <tt class="docutils literal"><span class="pre">myname</span></tt> with "My name is " and the value of the template
+preference <tt class="docutils literal"><span class="pre">developer</span></tt>.</p>
<p>You can change the way Geany recognizes the word to complete,
that is how the start and end of a word is recognised when the
snippet completion is requested. The section "Special" may
@@ -1467,8 +1467,8 @@
default characters or define it to add or remove characters to fit your
needs.</p>
</div>
-<div class="section" id="inserting-unicode-characters">
-<h3><a class="toc-backref" href="#id55">Inserting Unicode characters</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id55" id="inserting-unicode-characters" name="inserting-unicode-characters">Inserting Unicode characters</a></h3>
<p>With GTK 2.10 and above, you can insert Unicode code points by hitting
Ctrl-Shift-u, then still holding Ctrl-Shift, type some hex digits representing
the code point for the character you want and hit Enter or Return (still
@@ -1477,7 +1477,7 @@
character is also entered. In the case of Enter/Return, it is a newline, as
you might expect.</p>
<p>In some earlier versions of Geany, you might need to first unbind Ctrl-Shift-u
-in the <a class="reference internal" href="#keybinding-preferences">keybinding preferences</a>, then select <em>Tools->Reload Configuration</em>
+in the <a class="reference" href="#keybinding-preferences">keybinding preferences</a>, then select <em>Tools->Reload Configuration</em>
or restart Geany. Note that it works slightly differently from other GTK
applications, in that you'll need to continue to hold down the Ctrl and Shift
keys while typing the code point hex digits (and the Enter or Return to finish the code point).</p>
@@ -1486,8 +1486,8 @@
keys conflict with other Geany keybindings.</p>
</div>
</div>
-<div class="section" id="search-replace-and-go-to">
-<h2><a class="toc-backref" href="#id56">Search, replace and go to</a></h2>
+<div class="section">
+<h2><a class="toc-backref" href="#id56" id="search-replace-and-go-to" name="search-replace-and-go-to">Search, replace and go to</a></h2>
<p>This section describes search-related commands from the Search menu
and the editor window's popup menu:</p>
<ul class="simple">
@@ -1500,31 +1500,31 @@
<li>Go to line</li>
</ul>
<p>* These items are available from the editor window's popup menu, or by
-using a keyboard shortcut (see <a class="reference internal" href="#search-keybindings">Search keybindings</a>).</p>
-<div class="section" id="toolbar-entries">
-<h3><a class="toc-backref" href="#id57">Toolbar entries</a></h3>
+using a keyboard shortcut (see <a class="reference" href="#search-keybindings">Search keybindings</a>).</p>
+<div class="section">
+<h3><a class="toc-backref" href="#id57" id="toolbar-entries" name="toolbar-entries">Toolbar entries</a></h3>
<p>There are also two toolbar entries:</p>
<ul class="simple">
<li>Search bar</li>
<li>Go to line entry</li>
</ul>
-<p>There are keybindings to focus each of these - see <a class="reference internal" href="#focus-keybindings">Focus
+<p>There are keybindings to focus each of these - see <a class="reference" href="#focus-keybindings">Focus
keybindings</a>. Pressing Escape will then focus the editor.</p>
-<div class="section" id="search-bar">
-<h4><a class="toc-backref" href="#id58">Search bar</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id58" id="search-bar" name="search-bar">Search bar</a></h4>
<p>The quickest way to find some text is to use the search bar entry in
the toolbar. This performs a case-insensitive search in the current
document whilst you type. Pressing Enter will search again.</p>
</div>
</div>
-<div class="section" id="find">
-<h3><a class="toc-backref" href="#id59">Find</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id59" id="find" name="find">Find</a></h3>
<p>The Find dialog is used for finding text in one or more open documents.</p>
<img alt="./images/find_dialog.png" src="./images/find_dialog.png" />
-<div class="section" id="matching-options">
-<h4><a class="toc-backref" href="#id60">Matching options</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id60" id="matching-options" name="matching-options">Matching options</a></h4>
<p>The syntax for the <em>Use regular expressions</em> option is shown in
-<a class="reference internal" href="#regular-expressions">Regular expressions</a>.</p>
+<a class="reference" href="#regular-expressions">Regular expressions</a>.</p>
<div class="note">
<p class="first admonition-title">Note</p>
<p class="last"><em>Use escape sequences</em> is implied for regular expressions.</p>
@@ -1534,8 +1534,8 @@
a tab character. Other recognized symbols are: \\, \n, \r, \uXXXX
(Unicode characters).</p>
</div>
-<div class="section" id="find-all">
-<h4><a class="toc-backref" href="#id61">Find all</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id61" id="find-all" name="find-all">Find all</a></h4>
<p>To find all matches, click on the Find All expander. This will reveal
several options:</p>
<ul class="simple">
@@ -1550,8 +1550,8 @@
colored box. These markers can be removed by selecting the
Remove Markers command from the Document menu.</p>
</div>
-<div class="section" id="change-font-in-search-dialog-text-fields">
-<h4><a class="toc-backref" href="#id62">Change font in search dialog text fields</a></h4>
+<div class="section">
+<h4><a class="toc-backref" href="#id62" id="change-font-in-search-dialog-text-fields" name="change-font-in-search-dialog-text-fields">Change font in search dialog text fields</a></h4>
<p>All search related dialogs use a Monospace for the text input fields to
increase the readability of input text. This is useful when you are
typing input such as regular expressions with spaces, periods and commas which
@@ -1572,8 +1572,8 @@
for the search dialogs.</p>
</div>
</div>
-<div class="section" id="find-usage">
-<h3><a class="toc-backref" href="#id63">Find usage</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id63" id="find-usage" name="find-usage">Find usage</a></h3>
<p>Find usage searches all open files. It is similar to the Find All In
Session option in the Find dialog.</p>
<p>If there is a selection, then it is used as the search text; otherwise
@@ -1582,42 +1582,51 @@
click position when the popup menu is used. The search results are
shown in the Messages tab of the Message Window.</p>
</div>
-<div class="section" id="find-in-files">
-<h3><a class="toc-backref" href="#id64">Find in files</a></h3>
+<div class="section">
+<h3><a class="toc-backref" href="#id64" id="find-in-files" name="find-in-files">Find in files</a></h3>
<p>Find in files is a more powerful version of Find usage that searches
all files in a certain directory using the Grep tool. The Grep tool
must be correctly set in Preferences to the path of the system's Grep
-utility. GNU Grep is recommended.</p>
+utility. GNU Grep is recommended (see note below).</p>
<img alt="./images/find_in_files_dialog.png" src="./images/find_in_files_dialog.png" />
-<p>The Encoding combo box can be used to define the encoding of the files
+<p>The <em>Files</em> field optionally searches only files matching the
+patterns listed. Patterns are basic and shell-like, separated by a
+space. To search all <tt class="docutils literal"><span class="pre">.c</span></tt> and <tt class="docutils literal"><span class="pre">.h</span></tt> files, use: <tt class="docutils literal"><span class="pre">*.c</span> <span class="pre">*.h</span></tt>.</p>
+<p>The <em>Encoding</em> field can be used to define the encoding of the files
to be searched. The entered search text is converted to the chosen encoding
-and the search results are converted back to UTF-8.
@@ Diff output truncated at 100000 characters. @@
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.