Fix title capitalization.
git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@5670 ea778897-0a13-0410-b9d1-a72fbfd435f5
This commit is contained in:
Nick Treleaven
parent
c3e5bd956c
commit
17f12625ac
@ -4,6 +4,8 @@
|
||||
Rename Preferences dialog Interface subtab More -> Notebook tabs.
|
||||
* src/toolbar.c, src/dialogs.c:
|
||||
Use mimetype icon in File Properties dialog.
|
||||
* doc/geany.txt, doc/geany.html:
|
||||
Fix title capitalization.
|
||||
|
||||
|
||||
2011-04-01 Colomban Wendling <colomban(at)geany(dot)org>
|
||||
|
||||
142
doc/geany.html
142
doc/geany.html
@ -166,8 +166,8 @@ of this program, and also in the chapter <a class="reference" href="#gnu-general
|
||||
<li><a class="reference" href="#source-compilation" id="id15" name="id15">Source compilation</a><ul>
|
||||
<li><a class="reference" href="#autotools-based-build-system" id="id16" name="id16">Autotools based build system</a></li>
|
||||
<li><a class="reference" href="#waf-based-build-system" id="id17" name="id17">Waf based build system</a><ul>
|
||||
<li><a class="reference" href="#waf-cache" id="id18" name="id18">Waf Cache</a><ul>
|
||||
<li><a class="reference" href="#cleaning-the-cache" id="id19" name="id19">Cleaning the Cache</a></li>
|
||||
<li><a class="reference" href="#waf-cache" id="id18" name="id18">Waf cache</a><ul>
|
||||
<li><a class="reference" href="#cleaning-the-cache" id="id19" name="id19">Cleaning the cache</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
@ -267,7 +267,7 @@ of this program, and also in the chapter <a class="reference" href="#gnu-general
|
||||
<li><a class="reference" href="#generating-a-global-tags-file" id="id82" name="id82">Generating a global tags file</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#c-ignore-tags" id="id83" name="id83">C Ignore tags</a></li>
|
||||
<li><a class="reference" href="#c-ignore-tags" id="id83" name="id83">C ignore.tags</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#preferences" id="id84" name="id84">Preferences</a><ul>
|
||||
@ -338,35 +338,35 @@ of this program, and also in the chapter <a class="reference" href="#gnu-general
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#project-management" id="id126" name="id126">Project Management</a><ul>
|
||||
<li><a class="reference" href="#new-project" id="id127" name="id127">New Project</a></li>
|
||||
<li><a class="reference" href="#project-properties" id="id128" name="id128">Project Properties</a></li>
|
||||
<li><a class="reference" href="#open-project" id="id129" name="id129">Open Project</a></li>
|
||||
<li><a class="reference" href="#close-project" id="id130" name="id130">Close Project</a></li>
|
||||
<li><a class="reference" href="#project-management" id="id126" name="id126">Project management</a><ul>
|
||||
<li><a class="reference" href="#new-project" id="id127" name="id127">New project</a></li>
|
||||
<li><a class="reference" href="#project-properties" id="id128" name="id128">Project properties</a></li>
|
||||
<li><a class="reference" href="#open-project" id="id129" name="id129">Open project</a></li>
|
||||
<li><a class="reference" href="#close-project" id="id130" name="id130">Close project</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#build-menu" id="id131" name="id131">Build Menu</a><ul>
|
||||
<li><a class="reference" href="#build-menu" id="id131" name="id131">Build menu</a><ul>
|
||||
<li><a class="reference" href="#indicators" id="id132" name="id132">Indicators</a></li>
|
||||
<li><a class="reference" href="#default-build-menu-items" id="id133" name="id133">Default Build Menu Items</a><ul>
|
||||
<li><a class="reference" href="#default-build-menu-items" id="id133" name="id133">Default build menu items</a><ul>
|
||||
<li><a class="reference" href="#compile" id="id134" name="id134">Compile</a></li>
|
||||
<li><a class="reference" href="#build" id="id135" name="id135">Build</a></li>
|
||||
<li><a class="reference" href="#make" id="id136" name="id136">Make</a></li>
|
||||
<li><a class="reference" href="#make-custom-target" id="id137" name="id137">Make custom target</a></li>
|
||||
<li><a class="reference" href="#make-object" id="id138" name="id138">Make object</a></li>
|
||||
<li><a class="reference" href="#next-error" id="id139" name="id139">Next Error</a></li>
|
||||
<li><a class="reference" href="#previous-error" id="id140" name="id140">Previous Error</a></li>
|
||||
<li><a class="reference" href="#next-error" id="id139" name="id139">Next error</a></li>
|
||||
<li><a class="reference" href="#previous-error" id="id140" name="id140">Previous error</a></li>
|
||||
<li><a class="reference" href="#execute" id="id141" name="id141">Execute</a></li>
|
||||
<li><a class="reference" href="#stopping-running-processes" id="id142" name="id142">Stopping running processes</a><ul>
|
||||
<li><a class="reference" href="#terminal-emulators" id="id143" name="id143">Terminal emulators</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#set-build-commands" id="id144" name="id144">Set Build Commands</a></li>
|
||||
<li><a class="reference" href="#set-build-commands" id="id144" name="id144">Set build commands</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#build-menu-configuration" id="id145" name="id145">Build Menu Configuration</a></li>
|
||||
<li><a class="reference" href="#build-menu-commands-dialog" id="id146" name="id146">Build Menu Commands Dialog</a><ul>
|
||||
<li><a class="reference" href="#substitutions-in-commands-and-working-directories" id="id147" name="id147">Substitutions in Commands and Working Directories</a></li>
|
||||
<li><a class="reference" href="#build-menu-keyboard-shortcuts" id="id148" name="id148">Build Menu Keyboard Shortcuts</a></li>
|
||||
<li><a class="reference" href="#build-menu-configuration" id="id145" name="id145">Build menu configuration</a></li>
|
||||
<li><a class="reference" href="#build-menu-commands-dialog" id="id146" name="id146">Build menu commands dialog</a><ul>
|
||||
<li><a class="reference" href="#substitutions-in-commands-and-working-directories" id="id147" name="id147">Substitutions in commands and working directories</a></li>
|
||||
<li><a class="reference" href="#build-menu-keyboard-shortcuts" id="id148" name="id148">Build menu keyboard shortcuts</a></li>
|
||||
<li><a class="reference" href="#old-settings" id="id149" name="id149">Old settings</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
@ -374,7 +374,7 @@ of this program, and also in the chapter <a class="reference" href="#gnu-general
|
||||
</li>
|
||||
<li><a class="reference" href="#printing-support" id="id150" name="id150">Printing support</a></li>
|
||||
<li><a class="reference" href="#plugins" id="id151" name="id151">Plugins</a><ul>
|
||||
<li><a class="reference" href="#plugin-manager" id="id152" name="id152">Plugin Manager</a></li>
|
||||
<li><a class="reference" href="#plugin-manager" id="id152" name="id152">Plugin manager</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#keybindings" id="id153" name="id153">Keybindings</a><ul>
|
||||
@ -418,33 +418,33 @@ of this program, and also in the chapter <a class="reference" href="#gnu-general
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#filetype-configuration" id="id183" name="id183">Filetype configuration</a><ul>
|
||||
<li><a class="reference" href="#styling-section" id="id184" name="id184">[styling] Section</a><ul>
|
||||
<li><a class="reference" href="#styling-section" id="id184" name="id184">[styling] section</a><ul>
|
||||
<li><a class="reference" href="#using-a-named-style" id="id185" name="id185">Using a named style</a></li>
|
||||
<li><a class="reference" href="#reading-styles-from-another-filetype" id="id186" name="id186">Reading styles from another filetype</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#keywords-section" id="id187" name="id187">[keywords] Section</a></li>
|
||||
<li><a class="reference" href="#lexer-properties-section" id="id188" name="id188">[lexer_properties] Section</a></li>
|
||||
<li><a class="reference" href="#settings-section" id="id189" name="id189">[settings] Section</a></li>
|
||||
<li><a class="reference" href="#build-settings-section" id="id190" name="id190">[build_settings] Section</a></li>
|
||||
<li><a class="reference" href="#keywords-section" id="id187" name="id187">[keywords] section</a></li>
|
||||
<li><a class="reference" href="#lexer-properties-section" id="id188" name="id188">[lexer_properties] section</a></li>
|
||||
<li><a class="reference" href="#settings-section" id="id189" name="id189">[settings] section</a></li>
|
||||
<li><a class="reference" href="#build-settings-section" id="id190" name="id190">[build_settings] section</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#special-file-filetypes-common" id="id191" name="id191">Special file filetypes.common</a><ul>
|
||||
<li><a class="reference" href="#named-styles-section" id="id192" name="id192">[named_styles] Section</a></li>
|
||||
<li><a class="reference" href="#id4" id="id193" name="id193">[styling] Section</a></li>
|
||||
<li><a class="reference" href="#id5" id="id194" name="id194">[settings] Section</a></li>
|
||||
<li><a class="reference" href="#named-styles-section" id="id192" name="id192">[named_styles] section</a></li>
|
||||
<li><a class="reference" href="#id4" id="id193" name="id193">[styling] section</a></li>
|
||||
<li><a class="reference" href="#id5" id="id194" name="id194">[settings] section</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#filetype-extensions" id="id195" name="id195">Filetype extensions</a></li>
|
||||
<li><a class="reference" href="#preferences-file-format" id="id196" name="id196">Preferences File Format</a><ul>
|
||||
<li><a class="reference" href="#preferences-file-format" id="id196" name="id196">Preferences file format</a><ul>
|
||||
<li><a class="reference" href="#hidden-preferences" id="id197" name="id197">Hidden preferences</a></li>
|
||||
<li><a class="reference" href="#build-menu-section" id="id198" name="id198">[build-menu] Section</a></li>
|
||||
<li><a class="reference" href="#build-menu-section" id="id198" name="id198">[build-menu] section</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#project-file-format" id="id199" name="id199">Project File Format</a><ul>
|
||||
<li><a class="reference" href="#build-menu-additions" id="id200" name="id200">[build-menu] Additions</a></li>
|
||||
<li><a class="reference" href="#project-file-format" id="id199" name="id199">Project file format</a><ul>
|
||||
<li><a class="reference" href="#build-menu-additions" id="id200" name="id200">[build-menu] additions</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#templates" id="id201" name="id201">Templates</a><ul>
|
||||
@ -619,7 +619,7 @@ $ ./waf build
|
||||
% ./waf install
|
||||
</pre>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id18" id="waf-cache" name="waf-cache">Waf Cache</a></h4>
|
||||
<h4><a class="toc-backref" href="#id18" 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.
|
||||
@ -639,7 +639,7 @@ export WAFCACHE=/home/username/.cache/waf
|
||||
<p>More information about the Waf cache feature are available at
|
||||
<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="#id19" id="cleaning-the-cache" name="cleaning-the-cache">Cleaning the Cache</a></h5>
|
||||
<h5><a class="toc-backref" href="#id19" 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
|
||||
@ -1223,7 +1223,7 @@ settings are set in <a class="reference" href="#editor-indentation-preferences">
|
||||
for more information).</p>
|
||||
<p>The default settings can be overridden per-document using the
|
||||
Document menu. They can also be overridden by projects - see
|
||||
<a class="reference" href="#project-management">Project Management</a>.</p>
|
||||
<a class="reference" href="#project-management">Project management</a>.</p>
|
||||
<p>The indent mode for the current document is shown on the status bar
|
||||
as follows:</p>
|
||||
<dl class="docutils">
|
||||
@ -2036,7 +2036,7 @@ upgrading Geany.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id83" id="c-ignore-tags" name="c-ignore-tags">C Ignore tags</a></h3>
|
||||
<h3><a class="toc-backref" href="#id83" id="c-ignore-tags" name="c-ignore-tags">C ignore.tags</a></h3>
|
||||
<p>You can ignore certain tags for C-based languages if they would lead
|
||||
to wrong parsing of the code. Use the <em>Tools->Configuration
|
||||
Files->ignore.tags</em> menu item to open the user <tt class="docutils literal"><span class="pre">ignore.tags</span></tt> file.
|
||||
@ -2753,8 +2753,8 @@ like a Python console (e.g. ipython). Use this with care.</dd>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id126" id="project-management" name="project-management">Project Management</a></h2>
|
||||
<p>Project Management is optional in Geany. Currently it can be used for:</p>
|
||||
<h2><a class="toc-backref" href="#id126" id="project-management" name="project-management">Project management</a></h2>
|
||||
<p>Project management is optional in Geany. Currently it can be used for:</p>
|
||||
<ul class="simple">
|
||||
<li>Storing and opening session files on a project basis.</li>
|
||||
<li>Overriding default settings with project equivalents.</li>
|
||||
@ -2771,7 +2771,7 @@ Geany is shutdown. When restarting Geany, the previously opened project
|
||||
file that was in use at the end of the last session will be reopened.</p>
|
||||
<p>The project menu items are detailed below.</p>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id127" id="new-project" name="new-project">New Project</a></h3>
|
||||
<h3><a class="toc-backref" href="#id127" id="new-project" name="new-project">New project</a></h3>
|
||||
<p>To create a new project, fill in the <em>Name</em> field. By default this
|
||||
will setup a new project file <tt class="docutils literal"><span class="pre">~/projects/name.geany</span></tt>. Usually it's
|
||||
best to store all your project files in the same directory (they are
|
||||
@ -2781,7 +2781,7 @@ can safely be set to any existing path -- it will not touch the file
|
||||
structure contained in it.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id128" id="project-properties" name="project-properties">Project Properties</a></h3>
|
||||
<h3><a class="toc-backref" href="#id128" id="project-properties" name="project-properties">Project properties</a></h3>
|
||||
<p>You can set an optional description for the project. Currently it's
|
||||
only used for a template wildcard - see <a class="reference" href="#template-wildcards">Template wildcards</a>.</p>
|
||||
<p>The <em>Base path</em> field is used as the directory to run the Build menu commands.
|
||||
@ -2791,7 +2791,7 @@ relative to the project's file name.</p>
|
||||
<a class="reference" href="#indentation">Indentation</a> settings.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id129" id="open-project" name="open-project">Open Project</a></h3>
|
||||
<h3><a class="toc-backref" href="#id129" id="open-project" name="open-project">Open project</a></h3>
|
||||
<p>The Open command displays a standard file chooser, starting in
|
||||
<tt class="docutils literal"><span class="pre">~/projects</span></tt>. Choose a project file named with the <tt class="docutils literal"><span class="pre">.geany</span></tt>
|
||||
extension.</p>
|
||||
@ -2799,14 +2799,14 @@ extension.</p>
|
||||
open files and open the session files associated with the project.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id130" id="close-project" name="close-project">Close Project</a></h3>
|
||||
<h3><a class="toc-backref" href="#id130" id="close-project" name="close-project">Close project</a></h3>
|
||||
<p>Project file settings are saved when the project is closed.</p>
|
||||
<p>When project session support is enabled, Geany will close the project
|
||||
session files and open any previously closed default session files.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id131" id="build-menu" name="build-menu">Build Menu</a></h2>
|
||||
<h2><a class="toc-backref" href="#id131" id="build-menu" name="build-menu">Build menu</a></h2>
|
||||
<p>After editing code with Geany, the next step is to compile, link, build,
|
||||
interpret, run etc. As Geany supports many languages each with a different
|
||||
approach to such operations, and as there are also many language independent
|
||||
@ -2842,7 +2842,7 @@ selecting <em>Remove Error Indicators</em> in the Document menu.</p>
|
||||
preferences</a>.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id133" id="default-build-menu-items" name="default-build-menu-items">Default Build Menu Items</a></h3>
|
||||
<h3><a class="toc-backref" href="#id133" id="default-build-menu-items" name="default-build-menu-items">Default build menu items</a></h3>
|
||||
<p>Depending on the current file's filetype, the default Build menu will contain
|
||||
the following items:</p>
|
||||
<ul class="simple">
|
||||
@ -2899,11 +2899,11 @@ the current file, using the filename for 'current_file'. It is useful
|
||||
for building just the current file without building the whole project.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id139" id="next-error" name="next-error">Next Error</a></h4>
|
||||
<h4><a class="toc-backref" href="#id139" id="next-error" name="next-error">Next error</a></h4>
|
||||
<p>The next error item will move to the next detected error in the file.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id140" id="previous-error" name="previous-error">Previous Error</a></h4>
|
||||
<h4><a class="toc-backref" href="#id140" id="previous-error" name="previous-error">Previous error</a></h4>
|
||||
<p>The previous error item will move to the previous detected error in the file.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
@ -2942,7 +2942,7 @@ tab in the terminal field.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id144" id="set-build-commands" name="set-build-commands">Set Build Commands</a></h4>
|
||||
<h4><a class="toc-backref" href="#id144" id="set-build-commands" name="set-build-commands">Set build commands</a></h4>
|
||||
<p>By default Compile, Build and Execute are fairly basic commands. You
|
||||
may wish to customise them using <em>Set Build Commands</em>.</p>
|
||||
<p>E.g. for C you can add any include paths and compile flags for the
|
||||
@ -2951,7 +2951,7 @@ arguments you want to use when running Execute.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id145" id="build-menu-configuration" name="build-menu-configuration">Build Menu Configuration</a></h3>
|
||||
<h3><a class="toc-backref" href="#id145" id="build-menu-configuration" name="build-menu-configuration">Build menu configuration</a></h3>
|
||||
<p>The build menu has considerable flexibility and configurability, allowing
|
||||
both menu labels the commands they execute and the directory they execute
|
||||
in to be configured.</p>
|
||||
@ -2978,7 +2978,7 @@ and is directed to the terminal selected in preferences.</li>
|
||||
</li>
|
||||
</ul>
|
||||
<p>The maximum numbers of items in each of the configurable groups can be
|
||||
configured when Geany starts using hidden settings (see <a class="reference" href="#preferences-file-format">Preferences File Format</a>).
|
||||
configured when Geany starts using hidden settings (see <a class="reference" href="#preferences-file-format">Preferences file format</a>).
|
||||
Even though the maximum number of items may have been increased, only
|
||||
those menu items that have values configured are shown in the menu.</p>
|
||||
<p>The groups of menu items obtain their configuration from four potential
|
||||
@ -3105,12 +3105,12 @@ filetype-independent commands in a filetype file, this provides the ability to
|
||||
define filetype dependent default menu items.</li>
|
||||
<li>(Execute, Project File) and (Execute, Preferences) - the project independent
|
||||
execute and preferences independent execute commands can only be set by hand
|
||||
editing the appropriate file, see <a class="reference" href="#preferences-file-format">Preferences File Format</a> and <a class="reference" href="#project-file-format">Project File
|
||||
Format</a>.</li>
|
||||
editing the appropriate file, see <a class="reference" href="#preferences-file-format">Preferences file format</a> and <a class="reference" href="#project-file-format">Project file
|
||||
format</a>.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id146" id="build-menu-commands-dialog" name="build-menu-commands-dialog">Build Menu Commands Dialog</a></h3>
|
||||
<h3><a class="toc-backref" href="#id146" id="build-menu-commands-dialog" name="build-menu-commands-dialog">Build menu commands dialog</a></h3>
|
||||
<p>Most of the configuration of the build menu is done through the Build Menu
|
||||
Commands Dialog. You edit the configuration sourced from preferences in the
|
||||
dialog opened from the Build->Build Menu Commands item and you edit the
|
||||
@ -3142,7 +3142,7 @@ When you do this the command from the next lower priority source will be shown.
|
||||
To hide lower priority menu items without having anything show in the menu
|
||||
configure with a nothing in the label but at least one character in the command.</p>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id147" id="substitutions-in-commands-and-working-directories" name="substitutions-in-commands-and-working-directories">Substitutions in Commands and Working Directories</a></h4>
|
||||
<h4><a class="toc-backref" href="#id147" id="substitutions-in-commands-and-working-directories" name="substitutions-in-commands-and-working-directories">Substitutions in commands and working directories</a></h4>
|
||||
<p>The first occurence of each of the following character sequences in each of the
|
||||
command and working directory fields is substituted by the items specified below
|
||||
before the command is run.</p>
|
||||
@ -3163,7 +3163,7 @@ build menu.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id148" id="build-menu-keyboard-shortcuts" name="build-menu-keyboard-shortcuts">Build Menu Keyboard Shortcuts</a></h4>
|
||||
<h4><a class="toc-backref" href="#id148" id="build-menu-keyboard-shortcuts" name="build-menu-keyboard-shortcuts">Build menu keyboard shortcuts</a></h4>
|
||||
<p>Keyboard shortcuts can be defined for the first two filetype menu items, the first three
|
||||
independent menu items, the first two execute menu items and the fixed menu items.
|
||||
In the keybindings configuration dialog (see <a class="reference" href="#keybinding-preferences">Keybinding preferences</a>)
|
||||
@ -3175,7 +3175,7 @@ these items are identified by the default labels shown in the <a class="referenc
|
||||
<h4><a class="toc-backref" href="#id149" id="old-settings" name="old-settings">Old settings</a></h4>
|
||||
<p>The configurable Build Menu capability was introduced in Geany 0.19 and
|
||||
required a new section to be added to the configuration files (See
|
||||
<a class="reference" href="#preferences-file-format">Preferences File Format</a>). Geany will still load older format project,
|
||||
<a class="reference" href="#preferences-file-format">Preferences file format</a>). Geany will still load older format project,
|
||||
preferences and filetype file settings and will attempt to map them into the new
|
||||
configuration format. There is not a simple clean mapping between the formats.
|
||||
The mapping used produces the most sensible results for the majority of cases.
|
||||
@ -3257,7 +3257,7 @@ the following directories:</p>
|
||||
<p>See also <a class="reference" href="#plugin-documentation">Plugin documentation</a> for information about single plugins
|
||||
which are included in Geany.</p>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id152" id="plugin-manager" name="plugin-manager">Plugin Manager</a></h3>
|
||||
<h3><a class="toc-backref" href="#id152" id="plugin-manager" name="plugin-manager">Plugin manager</a></h3>
|
||||
<p>The Plugin Manager dialog lets you choose which plugins
|
||||
should be loaded at startup. You can also load and unload plugins on the
|
||||
fly using this dialog. Once you click the checkbox for a specific plugin
|
||||
@ -4450,9 +4450,9 @@ list, or none.</p>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id183" id="filetype-configuration" name="filetype-configuration">Filetype configuration</a></h3>
|
||||
<p>As well as the sections listed below, each filetype file can contain
|
||||
a [build-menu] section as described in <a class="reference" href="#build-menu-section">[build-menu] Section</a>.</p>
|
||||
a [build-menu] section as described in <a class="reference" href="#build-menu-section">[build-menu] section</a>.</p>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id184" id="styling-section" name="styling-section">[styling] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id184" id="styling-section" name="styling-section">[styling] section</a></h4>
|
||||
<p>In this section the colors for syntax highlighting are defined. The
|
||||
manual format is:</p>
|
||||
<ul class="simple">
|
||||
@ -4505,7 +4505,7 @@ styling the same as the C styling, you would put the following in
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id187" id="keywords-section" name="keywords-section">[keywords] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id187" id="keywords-section" name="keywords-section">[keywords] section</a></h4>
|
||||
<p>This section contains keys for different keyword lists specific to
|
||||
the filetype. Some filetypes do not support keywords, so adding a
|
||||
new key will not work. You can only add or remove keywords to/from
|
||||
@ -4516,7 +4516,7 @@ an existing list.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id188" id="lexer-properties-section" name="lexer-properties-section">[lexer_properties] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id188" id="lexer-properties-section" name="lexer-properties-section">[lexer_properties] section</a></h4>
|
||||
<p>Here any special properties for the Scintilla lexer can be set in the
|
||||
format <tt class="docutils literal"><span class="pre">key.name.field=some.value</span></tt>.</p>
|
||||
<p>Properties Geany uses are listed in the system filetype files. To find
|
||||
@ -4526,7 +4526,7 @@ egrep -o 'GetProperty\w*\("([^"]+)"[^)]+\)' scintilla/Lex*.cxx
|
||||
</pre>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id189" id="settings-section" name="settings-section">[settings] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id189" id="settings-section" name="settings-section">[settings] section</a></h4>
|
||||
<dl class="docutils">
|
||||
<dt>extension</dt>
|
||||
<dd><p class="first">This is the default file extension used when saving files, not
|
||||
@ -4649,8 +4649,8 @@ this setting in their system configuration files.</dd>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id190" id="build-settings-section" name="build-settings-section">[build_settings] Section</a></h4>
|
||||
<p>As of Geany 0.19 this section is supplemented by the <a class="reference" href="#build-menu-section">[build-menu] Section</a>.
|
||||
<h4><a class="toc-backref" href="#id190" id="build-settings-section" name="build-settings-section">[build_settings] section</a></h4>
|
||||
<p>As of Geany 0.19 this section is supplemented by the <a class="reference" href="#build-menu-section">[build-menu] section</a>.
|
||||
Values that are set in the [build-menu] section will override those in this section.</p>
|
||||
<dl class="docutils">
|
||||
<dt>error_regex</dt>
|
||||
@ -4717,7 +4717,7 @@ the system file.</p>
|
||||
<p class="last">See the <a class="reference" href="#filetype-configuration">Filetype configuration</a> section for how to define styles.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id192" id="named-styles-section" name="named-styles-section">[named_styles] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id192" id="named-styles-section" name="named-styles-section">[named_styles] section</a></h4>
|
||||
<p>Named styles declared here can be used in the [styling] section of any
|
||||
filetypes.* file.</p>
|
||||
<p>For example:</p>
|
||||
@ -4744,7 +4744,7 @@ original style.</p>
|
||||
schemes menu</a>.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id193" id="id4" name="id4">[styling] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id193" id="id4" name="id4">[styling] section</a></h4>
|
||||
<dl class="docutils">
|
||||
<dt>default</dt>
|
||||
<dd><p class="first">This is the default style. It is used for styling files without a
|
||||
@ -4928,7 +4928,7 @@ arguments set whether to use the defined colors.</p>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h4><a class="toc-backref" href="#id194" id="id5" name="id5">[settings] Section</a></h4>
|
||||
<h4><a class="toc-backref" href="#id194" id="id5" name="id5">[settings] section</a></h4>
|
||||
<dl class="docutils">
|
||||
<dt>whitespace_chars</dt>
|
||||
<dd><p class="first">Characters to treat as whitespace. These characters are ignored
|
||||
@ -4962,7 +4962,7 @@ Make=Makefile*;*.mk;Buildfile;
|
||||
</pre>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id196" id="preferences-file-format" name="preferences-file-format">Preferences File Format</a></h2>
|
||||
<h2><a class="toc-backref" href="#id196" id="preferences-file-format" name="preferences-file-format">Preferences file format</a></h2>
|
||||
<p>The user preferences file <tt class="docutils literal"><span class="pre">geany.conf</span></tt> holds settings for all the items configured
|
||||
in the preferences dialog. This file should not be edited while Geany is running
|
||||
as the file will be overwritten when the preferences in Geany are changed or Geany
|
||||
@ -5181,7 +5181,7 @@ execute section of the Build menu.</td>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id198" id="build-menu-section" name="build-menu-section">[build-menu] Section</a></h3>
|
||||
<h3><a class="toc-backref" href="#id198" id="build-menu-section" name="build-menu-section">[build-menu] section</a></h3>
|
||||
<p>The [build-menu] section contains the configuration of the build menu.
|
||||
This section can occur in filetype, preferences and project files and
|
||||
always has the format described here. Different menu items are loaded
|
||||
@ -5213,19 +5213,19 @@ starting at 00</li>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id199" id="project-file-format" name="project-file-format">Project File Format</a></h2>
|
||||
<h2><a class="toc-backref" href="#id199" id="project-file-format" name="project-file-format">Project file format</a></h2>
|
||||
<p>The project file contains project related settings and possibly a
|
||||
record of the current session files.</p>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id200" id="build-menu-additions" name="build-menu-additions">[build-menu] Additions</a></h3>
|
||||
<h3><a class="toc-backref" href="#id200" id="build-menu-additions" name="build-menu-additions">[build-menu] additions</a></h3>
|
||||
<p>The project file also can have extra fields in the [build-menu] section
|
||||
in addition to those listed in <a class="reference" href="#build-menu-section">[build-menu] Section</a> above.</p>
|
||||
in addition to those listed in <a class="reference" href="#build-menu-section">[build-menu] section</a> above.</p>
|
||||
<p>When filetype menu items are configured for the project they are stored
|
||||
in the project file.</p>
|
||||
<p>The <tt class="docutils literal"><span class="pre">filetypes</span></tt> entry is a list of the filetypes which exist in the
|
||||
project file.</p>
|
||||
<p>For each filetype the entries for that filetype have the format defined in
|
||||
<a class="reference" href="#build-menu-section">[build-menu] Section</a> but the key is prefixed by the name of the filetype
|
||||
<a class="reference" href="#build-menu-section">[build-menu] section</a> but the key is prefixed by the name of the filetype
|
||||
as it appears in the <tt class="docutils literal"><span class="pre">filetypes</span></tt> entry, eg the entry for the label of
|
||||
filetype menu item 0 for the C filetype would be</p>
|
||||
<blockquote>
|
||||
@ -6553,7 +6553,7 @@ USE OR PERFORMANCE OF THIS SOFTWARE.</p>
|
||||
<div class="footer">
|
||||
<hr class="footer" />
|
||||
<a class="reference" href="geany.txt">View document source</a>.
|
||||
Generated on: 2011-03-29 13:57 UTC.
|
||||
Generated on: 2011-04-01 12:23 UTC.
|
||||
Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
|
||||
|
||||
</div>
|
||||
|
||||
@ -161,7 +161,7 @@ Then as root::
|
||||
|
||||
% ./waf install
|
||||
|
||||
Waf Cache
|
||||
Waf cache
|
||||
`````````
|
||||
|
||||
The Waf build system has a nice and interesting feature which can help to avoid
|
||||
@ -184,7 +184,7 @@ Remember to replace ``username`` with your actual username.
|
||||
More information about the Waf cache feature are available at
|
||||
http://code.google.com/p/waf/wiki/CacheObjectFiles.
|
||||
|
||||
Cleaning the Cache
|
||||
Cleaning the cache
|
||||
******************
|
||||
You should be careful about the size of the cache directory as it may
|
||||
grow rapidly over time.
|
||||
@ -771,7 +771,7 @@ for more information).
|
||||
|
||||
The default settings can be overridden per-document using the
|
||||
Document menu. They can also be overridden by projects - see
|
||||
`Project Management`_.
|
||||
`Project management`_.
|
||||
|
||||
The indent mode for the current document is shown on the status bar
|
||||
as follows:
|
||||
@ -1647,7 +1647,7 @@ copy of the generated tags file because it will get overwritten when
|
||||
upgrading Geany.
|
||||
|
||||
|
||||
C Ignore tags
|
||||
C ignore.tags
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
You can ignore certain tags for C-based languages if they would lead
|
||||
@ -2462,10 +2462,10 @@ Don't use run script
|
||||
like a Python console (e.g. ipython). Use this with care.
|
||||
|
||||
|
||||
Project Management
|
||||
Project management
|
||||
------------------
|
||||
|
||||
Project Management is optional in Geany. Currently it can be used for:
|
||||
Project management is optional in Geany. Currently it can be used for:
|
||||
|
||||
* Storing and opening session files on a project basis.
|
||||
* Overriding default settings with project equivalents.
|
||||
@ -2486,7 +2486,7 @@ file that was in use at the end of the last session will be reopened.
|
||||
The project menu items are detailed below.
|
||||
|
||||
|
||||
New Project
|
||||
New project
|
||||
^^^^^^^^^^^
|
||||
|
||||
To create a new project, fill in the *Name* field. By default this
|
||||
@ -2499,7 +2499,7 @@ can safely be set to any existing path -- it will not touch the file
|
||||
structure contained in it.
|
||||
|
||||
|
||||
Project Properties
|
||||
Project properties
|
||||
^^^^^^^^^^^^^^^^^^
|
||||
|
||||
You can set an optional description for the project. Currently it's
|
||||
@ -2513,7 +2513,7 @@ The *Indentation* tab allows you to override the default
|
||||
`Indentation`_ settings.
|
||||
|
||||
|
||||
Open Project
|
||||
Open project
|
||||
^^^^^^^^^^^^
|
||||
|
||||
The Open command displays a standard file chooser, starting in
|
||||
@ -2524,7 +2524,7 @@ When project session support is enabled, Geany will close the currently
|
||||
open files and open the session files associated with the project.
|
||||
|
||||
|
||||
Close Project
|
||||
Close project
|
||||
^^^^^^^^^^^^^
|
||||
|
||||
Project file settings are saved when the project is closed.
|
||||
@ -2533,7 +2533,7 @@ When project session support is enabled, Geany will close the project
|
||||
session files and open any previously closed default session files.
|
||||
|
||||
|
||||
Build Menu
|
||||
Build menu
|
||||
----------
|
||||
After editing code with Geany, the next step is to compile, link, build,
|
||||
interpret, run etc. As Geany supports many languages each with a different
|
||||
@ -2574,7 +2574,7 @@ If you do not like this feature, you can disable it - see `Editor Features
|
||||
preferences`_.
|
||||
|
||||
|
||||
Default Build Menu Items
|
||||
Default build menu items
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Depending on the current file's filetype, the default Build menu will contain
|
||||
the following items:
|
||||
@ -2642,12 +2642,12 @@ Make object will run "make current_file.o" in the same directory as
|
||||
the current file, using the filename for 'current_file'. It is useful
|
||||
for building just the current file without building the whole project.
|
||||
|
||||
Next Error
|
||||
Next error
|
||||
``````````
|
||||
|
||||
The next error item will move to the next detected error in the file.
|
||||
|
||||
Previous Error
|
||||
Previous error
|
||||
``````````````
|
||||
The previous error item will move to the previous detected error in the file.
|
||||
|
||||
@ -2693,7 +2693,7 @@ stopped. Just add this option in the preferences dialog on the Tools
|
||||
tab in the terminal field.
|
||||
|
||||
|
||||
Set Build Commands
|
||||
Set build commands
|
||||
``````````````````
|
||||
|
||||
By default Compile, Build and Execute are fairly basic commands. You
|
||||
@ -2703,7 +2703,7 @@ E.g. for C you can add any include paths and compile flags for the
|
||||
compiler, any library names and paths for the linker, and any
|
||||
arguments you want to use when running Execute.
|
||||
|
||||
Build Menu Configuration
|
||||
Build menu configuration
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The build menu has considerable flexibility and configurability, allowing
|
||||
@ -2734,7 +2734,7 @@ behaviors:
|
||||
* Show the build menu commands dialog.
|
||||
|
||||
The maximum numbers of items in each of the configurable groups can be
|
||||
configured when Geany starts using hidden settings (see `Preferences File Format`_).
|
||||
configured when Geany starts using hidden settings (see `Preferences file format`_).
|
||||
Even though the maximum number of items may have been increased, only
|
||||
those menu items that have values configured are shown in the menu.
|
||||
|
||||
@ -2803,10 +2803,10 @@ The following notes on the table reference cells by coordinate as (group,source)
|
||||
|
||||
* (Execute, Project File) and (Execute, Preferences) - the project independent
|
||||
execute and preferences independent execute commands can only be set by hand
|
||||
editing the appropriate file, see `Preferences File Format`_ and `Project File
|
||||
Format`_.
|
||||
editing the appropriate file, see `Preferences file format`_ and `Project file
|
||||
format`_.
|
||||
|
||||
Build Menu Commands Dialog
|
||||
Build menu commands dialog
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
Most of the configuration of the build menu is done through the Build Menu
|
||||
@ -2848,7 +2848,7 @@ When you do this the command from the next lower priority source will be shown.
|
||||
To hide lower priority menu items without having anything show in the menu
|
||||
configure with a nothing in the label but at least one character in the command.
|
||||
|
||||
Substitutions in Commands and Working Directories
|
||||
Substitutions in commands and working directories
|
||||
`````````````````````````````````````````````````
|
||||
|
||||
The first occurence of each of the following character sequences in each of the
|
||||
@ -2868,7 +2868,7 @@ before the command is run.
|
||||
and even checked into and out of version control without having to re-configure the
|
||||
build menu.
|
||||
|
||||
Build Menu Keyboard Shortcuts
|
||||
Build menu keyboard shortcuts
|
||||
`````````````````````````````
|
||||
|
||||
Keyboard shortcuts can be defined for the first two filetype menu items, the first three
|
||||
@ -2885,7 +2885,7 @@ Old settings
|
||||
|
||||
The configurable Build Menu capability was introduced in Geany 0.19 and
|
||||
required a new section to be added to the configuration files (See
|
||||
`Preferences File Format`_). Geany will still load older format project,
|
||||
`Preferences file format`_). Geany will still load older format project,
|
||||
preferences and filetype file settings and will attempt to map them into the new
|
||||
configuration format. There is not a simple clean mapping between the formats.
|
||||
The mapping used produces the most sensible results for the majority of cases.
|
||||
@ -2974,7 +2974,7 @@ Most plugins add menu items to the *Tools* menu when they are loaded.
|
||||
See also `Plugin documentation`_ for information about single plugins
|
||||
which are included in Geany.
|
||||
|
||||
Plugin Manager
|
||||
Plugin manager
|
||||
^^^^^^^^^^^^^^
|
||||
The Plugin Manager dialog lets you choose which plugins
|
||||
should be loaded at startup. You can also load and unload plugins on the
|
||||
@ -3711,9 +3711,9 @@ Filetype configuration
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
As well as the sections listed below, each filetype file can contain
|
||||
a [build-menu] section as described in `[build-menu] Section`_.
|
||||
a [build-menu] section as described in `[build-menu] section`_.
|
||||
|
||||
[styling] Section
|
||||
[styling] section
|
||||
`````````````````
|
||||
|
||||
In this section the colors for syntax highlighting are defined. The
|
||||
@ -3774,7 +3774,7 @@ styling the same as the C styling, you would put the following in
|
||||
[styling=C]
|
||||
|
||||
|
||||
[keywords] Section
|
||||
[keywords] section
|
||||
``````````````````
|
||||
|
||||
This section contains keys for different keyword lists specific to
|
||||
@ -3786,7 +3786,7 @@ an existing list.
|
||||
The keywords list must be in one line without line ending characters.
|
||||
|
||||
|
||||
[lexer_properties] Section
|
||||
[lexer_properties] section
|
||||
``````````````````````````
|
||||
Here any special properties for the Scintilla lexer can be set in the
|
||||
format ``key.name.field=some.value``.
|
||||
@ -3797,7 +3797,7 @@ other properties you need Geany's source code::
|
||||
egrep -o 'GetProperty\w*\("([^"]+)"[^)]+\)' scintilla/Lex*.cxx
|
||||
|
||||
|
||||
[settings] Section
|
||||
[settings] section
|
||||
``````````````````
|
||||
|
||||
extension
|
||||
@ -3923,10 +3923,10 @@ xml_indent_tags
|
||||
this setting in their system configuration files.
|
||||
|
||||
|
||||
[build_settings] Section
|
||||
[build_settings] section
|
||||
````````````````````````
|
||||
|
||||
As of Geany 0.19 this section is supplemented by the `[build-menu] Section`_.
|
||||
As of Geany 0.19 this section is supplemented by the `[build-menu] section`_.
|
||||
Values that are set in the [build-menu] section will override those in this section.
|
||||
|
||||
error_regex
|
||||
@ -3999,7 +3999,7 @@ the system file.
|
||||
See the `Filetype configuration`_ section for how to define styles.
|
||||
|
||||
|
||||
[named_styles] Section
|
||||
[named_styles] section
|
||||
``````````````````````
|
||||
Named styles declared here can be used in the [styling] section of any
|
||||
filetypes.* file.
|
||||
@ -4028,7 +4028,7 @@ different files.
|
||||
This section can be overridden with color scheme files - see the `Color
|
||||
schemes menu`_.
|
||||
|
||||
[styling] Section
|
||||
[styling] section
|
||||
`````````````````
|
||||
default
|
||||
This is the default style. It is used for styling files without a
|
||||
@ -4243,7 +4243,7 @@ calltips
|
||||
*Example:* ``calltips=0xc0c0c0;0xffffff;false;false``
|
||||
|
||||
|
||||
[settings] Section
|
||||
[settings] section
|
||||
``````````````````
|
||||
whitespace_chars
|
||||
Characters to treat as whitespace. These characters are ignored
|
||||
@ -4279,7 +4279,7 @@ should look like::
|
||||
[Extensions]
|
||||
Make=Makefile*;*.mk;Buildfile;
|
||||
|
||||
Preferences File Format
|
||||
Preferences file format
|
||||
-----------------------
|
||||
|
||||
The user preferences file ``geany.conf`` holds settings for all the items configured
|
||||
@ -4404,7 +4404,7 @@ number_exec_menu_items The maximum number of menu items in the 2
|
||||
execute section of the Build menu.
|
||||
================================ =========================================== ==================
|
||||
|
||||
[build-menu] Section
|
||||
[build-menu] section
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The [build-menu] section contains the configuration of the build menu.
|
||||
@ -4437,18 +4437,18 @@ where:
|
||||
- WD for working directory
|
||||
|
||||
|
||||
Project File Format
|
||||
Project file format
|
||||
-------------------
|
||||
|
||||
The project file contains project related settings and possibly a
|
||||
record of the current session files.
|
||||
|
||||
|
||||
[build-menu] Additions
|
||||
[build-menu] additions
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
The project file also can have extra fields in the [build-menu] section
|
||||
in addition to those listed in `[build-menu] Section`_ above.
|
||||
in addition to those listed in `[build-menu] section`_ above.
|
||||
|
||||
When filetype menu items are configured for the project they are stored
|
||||
in the project file.
|
||||
@ -4457,7 +4457,7 @@ The ``filetypes`` entry is a list of the filetypes which exist in the
|
||||
project file.
|
||||
|
||||
For each filetype the entries for that filetype have the format defined in
|
||||
`[build-menu] Section`_ but the key is prefixed by the name of the filetype
|
||||
`[build-menu] section`_ but the key is prefixed by the name of the filetype
|
||||
as it appears in the ``filetypes`` entry, eg the entry for the label of
|
||||
filetype menu item 0 for the C filetype would be
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user