doc/geany.html

   1 <?xml version="1.0" encoding="utf-8" ?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   4 <head>
   5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6 <meta name="generator" content="Docutils 0.8.1: http://docutils.sourceforge.net/" />
   7 <title>Geany</title>
   8 <meta name="authors" content="Enrico Tröger  Nick Treleaven  Frank Lanitz  Colomban Wendling" />
   9 <meta name="date" content="2011-10-01" />
  10 <style type="text/css">
  11
  12 /*
  13 :Author: Enrico Troeger
  14 :Contact: enrico(dot)troeger(at)uvena(dot)de
  15 :Copyright: This stylesheet has been placed in the public domain.
  16
  17 Stylesheet for Geany's documentation based on a version of John Gabriele.
  18 */
  19
  20 @media screen {
  21
  22         body {
  23                 background-color: #f2f2f2;
  24                 color: #404040;
  25                 margin-left: 0.4em;
  26                 max-width: 60em;
  27                 font-size: 90%;
  28         }
  29
  30         a {
  31                 color: #990000;
  32         }
  33
  34         a:visited {
  35                 color: #7E558E;
  36         }
  37
  38         a:hover {
  39                 text-decoration: none;
  40         }
  41
  42         h1 {
  43                 border-top: 1px dotted;
  44                 margin-top: 2em;
  45         }
  46
  47         h1, h2, h3 {
  48                 font-family: sans-serif;
  49                 color: #5D0606;
  50         }
  51
  52         h1.title {
  53           text-align: left }
  54
  55         h2 {
  56                 margin-top: 30px;
  57         }
  58
  59         h2.subtitle {
  60           text-align: left }
  61
  62         h3 {
  63                 padding-left: 3px;
  64         }
  65
  66         blockquote, pre {
  67                 border: 1px solid;
  68                 padding: 0.4em;
  69         }
  70
  71         blockquote {
  72                 font-family: sans-serif;
  73                 background-color: #DBEDD5;
  74                 border: 1px dotted;
  75                 border-left: 4px solid;
  76                 border-color: #9FD98C;
  77         }
  78
  79         pre {
  80                 background-color: #ECDFCE;
  81                 border: 1px dotted;
  82                 border-left: 4px solid;
  83                 border-color: #D9BE9A;
  84         }
  85
  86         tt, pre, code {
  87                 color: #6D4212;
  88         }
  89
  90         table {
  91                 border: 1px solid #D9BE9A;
  92         }
  93
  94         th {
  95                 background-color: #ECDFCE;
  96                 border: 1px dotted #D9BE9A;
  97         }
  98
  99         td {
 100                 border: 1px dotted #D9BE9A;
 101         }
 102
 103         .docinfo-name {
 104                 color: #5D0606;
 105         }
 106
 107         p.admonition-title {
 108                 color: #990000;
 109                 font-weight: bold;
 110         }
 111
 112         div.note {
 113                 margin: 1em 3em;
 114                 padding: 0em;
 115         }
 116
 117         dt {
 118                 font-style: italic;
 119         }
 120
 121 }
 122
 123 @media print {
 124
 125 }
 126
 127 </style>
 128 </head>
 129 <body>
 130 <div class="document" id="geany">
 131 <h1 class="title">Geany</h1>
 132 <h2 class="subtitle" id="a-fast-light-gtk-ide">A fast, light, GTK+ IDE</h2>
 133 <table class="docinfo" frame="void" rules="none">
 134 <col class="docinfo-name" />
 135 <col class="docinfo-content" />
 136 <tbody valign="top">
 137 <tr><th class="docinfo-name">Authors:</th>
 138 <td>Enrico Tröger
 139 <br />Nick Treleaven
 140 <br />Frank Lanitz
 141 <br />Colomban Wendling</td></tr>
 142 <tr><th class="docinfo-name">Date:</th>
 143 <td>2011-10-01</td></tr>
 144 <tr><th class="docinfo-name">Version:</th>
 145 <td>0.21</td></tr>
 146 </tbody>
 147 </table>
 148 <p>Copyright © 2005-2011</p>
 149 <p>This document is distributed under the terms of the GNU General Public
 150 License as published by the Free Software Foundation; either version 2
 151 of the License, or (at your option) any later version. A copy of this
 152 license can be found in the file COPYING included with the source code
 153 of this program, and also in the chapter <a class="reference internal" href="#gnu-general-public-license">GNU General Public License</a>.</p>
 154 <div class="contents topic" id="contents">
 155 <p class="topic-title first">Contents</p>
 156 <ul class="simple">
 157 <li><a class="reference internal" href="#introduction" id="id7">Introduction</a><ul>
 158 <li><a class="reference internal" href="#about-geany" id="id8">About Geany</a></li>
 159 <li><a class="reference internal" href="#where-to-get-it" id="id9">Where to get it</a></li>
 160 <li><a class="reference internal" href="#license" id="id10">License</a></li>
 161 <li><a class="reference internal" href="#about-this-document" id="id11">About this document</a></li>
 162 </ul>
 163 </li>
 164 <li><a class="reference internal" href="#installation" id="id12">Installation</a><ul>
 165 <li><a class="reference internal" href="#requirements" id="id13">Requirements</a></li>
 166 <li><a class="reference internal" href="#binary-packages" id="id14">Binary packages</a></li>
 167 <li><a class="reference internal" href="#source-compilation" id="id15">Source compilation</a><ul>
 168 <li><a class="reference internal" href="#autotools-based-build-system" id="id16">Autotools based build system</a></li>
 169 <li><a class="reference internal" href="#waf-based-build-system" id="id17">Waf based build system</a><ul>
 170 <li><a class="reference internal" href="#waf-cache" id="id18">Waf cache</a><ul>
 171 <li><a class="reference internal" href="#cleaning-the-cache" id="id19">Cleaning the cache</a></li>
 172 </ul>
 173 </li>
 174 </ul>
 175 </li>
 176 <li><a class="reference internal" href="#custom-installation" id="id20">Custom installation</a></li>
 177 <li><a class="reference internal" href="#dynamic-linking-loader-support-and-vte" id="id21">Dynamic linking loader support and VTE</a></li>
 178 <li><a class="reference internal" href="#build-problems" id="id22">Build problems</a></li>
 179 </ul>
 180 </li>
 181 <li><a class="reference internal" href="#installation-prefix" id="id23">Installation prefix</a></li>
 182 </ul>
 183 </li>
 184 <li><a class="reference internal" href="#usage" id="id24">Usage</a><ul>
 185 <li><a class="reference internal" href="#getting-started" id="id25">Getting started</a></li>
 186 <li><a class="reference internal" href="#the-geany-workspace" id="id26">The Geany workspace</a></li>
 187 <li><a class="reference internal" href="#command-line-options" id="id27">Command line options</a></li>
 188 <li><a class="reference internal" href="#general" id="id28">General</a><ul>
 189 <li><a class="reference internal" href="#startup" id="id29">Startup</a></li>
 190 <li><a class="reference internal" href="#opening-files-from-the-command-line-in-a-running-instance" id="id30">Opening files from the command-line in a running instance</a></li>
 191 <li><a class="reference internal" href="#virtual-terminal-emulator-widget-vte" id="id31">Virtual terminal emulator widget (VTE)</a></li>
 192 <li><a class="reference internal" href="#defining-own-widget-styles-using-gtkrc-2-0" id="id32">Defining own widget styles using .gtkrc-2.0</a></li>
 193 </ul>
 194 </li>
 195 <li><a class="reference internal" href="#documents" id="id33">Documents</a><ul>
 196 <li><a class="reference internal" href="#switching-between-documents" id="id34">Switching between documents</a></li>
 197 </ul>
 198 </li>
 199 <li><a class="reference internal" href="#character-sets-and-unicode-byte-order-mark-bom" id="id35">Character sets and Unicode Byte-Order-Mark (BOM)</a><ul>
 200 <li><a class="reference internal" href="#using-character-sets" id="id36">Using character sets</a></li>
 201 <li><a class="reference internal" href="#in-file-encoding-specification" id="id37">In-file encoding specification</a></li>
 202 <li><a class="reference internal" href="#special-encoding-none" id="id38">Special encoding &quot;None&quot;</a></li>
 203 <li><a class="reference internal" href="#unicode-byte-order-mark-bom" id="id39">Unicode Byte-Order-Mark (BOM)</a></li>
 204 </ul>
 205 </li>
 206 <li><a class="reference internal" href="#editing" id="id40">Editing</a><ul>
 207 <li><a class="reference internal" href="#folding" id="id41">Folding</a></li>
 208 <li><a class="reference internal" href="#column-mode-editing-rectangular-selections" id="id42">Column mode editing (rectangular selections)</a></li>
 209 <li><a class="reference internal" href="#drag-and-drop-of-text" id="id43">Drag and drop of text</a></li>
 210 <li><a class="reference internal" href="#indentation" id="id44">Indentation</a><ul>
 211 <li><a class="reference internal" href="#applying-new-indentation-settings" id="id45">Applying new indentation settings</a></li>
 212 <li><a class="reference internal" href="#detecting-indent-type" id="id46">Detecting indent type</a></li>
 213 </ul>
 214 </li>
 215 <li><a class="reference internal" href="#auto-indentation" id="id47">Auto-indentation</a></li>
 216 <li><a class="reference internal" href="#bookmarks" id="id48">Bookmarks</a></li>
 217 <li><a class="reference internal" href="#code-navigation-history" id="id49">Code navigation history</a></li>
 218 <li><a class="reference internal" href="#sending-text-through-custom-commands" id="id50">Sending text through custom commands</a></li>
 219 <li><a class="reference internal" href="#context-actions" id="id51">Context actions</a></li>
 220 <li><a class="reference internal" href="#autocompletion" id="id52">Autocompletion</a><ul>
 221 <li><a class="reference internal" href="#word-part-completion" id="id53">Word part completion</a></li>
 222 <li><a class="reference internal" href="#scope-autocompletion" id="id54">Scope autocompletion</a></li>
 223 </ul>
 224 </li>
 225 <li><a class="reference internal" href="#user-definable-snippets" id="id55">User-definable snippets</a><ul>
 226 <li><a class="reference internal" href="#snippet-keybindings" id="id56">Snippet keybindings</a></li>
 227 </ul>
 228 </li>
 229 <li><a class="reference internal" href="#inserting-unicode-characters" id="id57">Inserting Unicode characters</a></li>
 230 </ul>
 231 </li>
 232 <li><a class="reference internal" href="#search-replace-and-go-to" id="id58">Search, replace and go to</a><ul>
 233 <li><a class="reference internal" href="#toolbar-entries" id="id59">Toolbar entries</a><ul>
 234 <li><a class="reference internal" href="#search-bar" id="id60">Search bar</a></li>
 235 </ul>
 236 </li>
 237 <li><a class="reference internal" href="#find" id="id61">Find</a><ul>
 238 <li><a class="reference internal" href="#matching-options" id="id62">Matching options</a></li>
 239 <li><a class="reference internal" href="#find-all" id="id63">Find all</a></li>
 240 <li><a class="reference internal" href="#change-font-in-search-dialog-text-fields" id="id64">Change font in search dialog text fields</a></li>
 241 </ul>
 242 </li>
 243 <li><a class="reference internal" href="#find-selection" id="id65">Find selection</a></li>
 244 <li><a class="reference internal" href="#find-usage" id="id66">Find usage</a></li>
 245 <li><a class="reference internal" href="#find-in-files" id="id67">Find in files</a><ul>
 246 <li><a class="reference internal" href="#filtering-out-version-control-files" id="id68">Filtering out version control files</a></li>
 247 </ul>
 248 </li>
 249 <li><a class="reference internal" href="#replace" id="id69">Replace</a><ul>
 250 <li><a class="reference internal" href="#replace-all" id="id70">Replace all</a></li>
 251 </ul>
 252 </li>
 253 <li><a class="reference internal" href="#go-to-tag-definition" id="id71">Go to tag definition</a></li>
 254 <li><a class="reference internal" href="#go-to-tag-declaration" id="id72">Go to tag declaration</a></li>
 255 <li><a class="reference internal" href="#go-to-line" id="id73">Go to line</a></li>
 256 <li><a class="reference internal" href="#regular-expressions" id="id74">Regular expressions</a></li>
 257 </ul>
 258 </li>
 259 <li><a class="reference internal" href="#view-menu" id="id75">View menu</a><ul>
 260 <li><a class="reference internal" href="#color-schemes-menu" id="id76">Color schemes menu</a></li>
 261 </ul>
 262 </li>
 263 <li><a class="reference internal" href="#tags" id="id77">Tags</a><ul>
 264 <li><a class="reference internal" href="#workspace-tags" id="id78">Workspace tags</a></li>
 265 <li><a class="reference internal" href="#global-tags" id="id79">Global tags</a><ul>
 266 <li><a class="reference internal" href="#default-global-tags-files" id="id80">Default global tags files</a></li>
 267 <li><a class="reference internal" href="#global-tags-file-format" id="id81">Global tags file format</a></li>
 268 <li><a class="reference internal" href="#generating-a-global-tags-file" id="id82">Generating a global tags file</a></li>
 269 </ul>
 270 </li>
 271 <li><a class="reference internal" href="#c-ignore-tags" id="id83">C ignore.tags</a></li>
 272 </ul>
 273 </li>
 274 <li><a class="reference internal" href="#preferences" id="id84">Preferences</a><ul>
 275 <li><a class="reference internal" href="#general-startup-preferences" id="id85">General Startup preferences</a><ul>
 276 <li><a class="reference internal" href="#id1" id="id86">Startup</a></li>
 277 <li><a class="reference internal" href="#shutdown" id="id87">Shutdown</a></li>
 278 <li><a class="reference internal" href="#paths" id="id88">Paths</a></li>
 279 </ul>
 280 </li>
 281 <li><a class="reference internal" href="#general-miscellaneous-preferences" id="id89">General Miscellaneous preferences</a><ul>
 282 <li><a class="reference internal" href="#miscellaneous" id="id90">Miscellaneous</a></li>
 283 <li><a class="reference internal" href="#search" id="id91">Search</a></li>
 284 <li><a class="reference internal" href="#projects" id="id92">Projects</a></li>
 285 </ul>
 286 </li>
 287 <li><a class="reference internal" href="#interface-preferences" id="id93">Interface preferences</a><ul>
 288 <li><a class="reference internal" href="#sidebar" id="id94">Sidebar</a></li>
 289 <li><a class="reference internal" href="#fonts" id="id95">Fonts</a></li>
 290 <li><a class="reference internal" href="#id2" id="id96">Miscellaneous</a></li>
 291 </ul>
 292 </li>
 293 <li><a class="reference internal" href="#interface-notebook-tab-preferences" id="id97">Interface Notebook tab preferences</a><ul>
 294 <li><a class="reference internal" href="#editor-tabs" id="id98">Editor tabs</a></li>
 295 <li><a class="reference internal" href="#tab-positions" id="id99">Tab positions</a></li>
 296 </ul>
 297 </li>
 298 <li><a class="reference internal" href="#interface-toolbar-preferences" id="id100">Interface Toolbar preferences</a><ul>
 299 <li><a class="reference internal" href="#toolbar" id="id101">Toolbar</a></li>
 300 <li><a class="reference internal" href="#appearance" id="id102">Appearance</a></li>
 301 </ul>
 302 </li>
 303 <li><a class="reference internal" href="#editor-features-preferences" id="id103">Editor Features preferences</a><ul>
 304 <li><a class="reference internal" href="#features" id="id104">Features</a></li>
 305 </ul>
 306 </li>
 307 <li><a class="reference internal" href="#editor-indentation-preferences" id="id105">Editor Indentation preferences</a><ul>
 308 <li><a class="reference internal" href="#indentation-group" id="id106">Indentation group</a></li>
 309 </ul>
 310 </li>
 311 <li><a class="reference internal" href="#editor-completions-preferences" id="id107">Editor Completions preferences</a><ul>
 312 <li><a class="reference internal" href="#completions" id="id108">Completions</a></li>
 313 <li><a class="reference internal" href="#auto-close-quotes-and-brackets" id="id109">Auto-close quotes and brackets</a></li>
 314 </ul>
 315 </li>
 316 <li><a class="reference internal" href="#editor-display-preferences" id="id110">Editor Display preferences</a><ul>
 317 <li><a class="reference internal" href="#display" id="id111">Display</a></li>
 318 <li><a class="reference internal" href="#long-line-marker" id="id112">Long line marker</a></li>
 319 <li><a class="reference internal" href="#virtual-spaces" id="id113">Virtual spaces</a></li>
 320 </ul>
 321 </li>
 322 <li><a class="reference internal" href="#files-preferences" id="id114">Files preferences</a><ul>
 323 <li><a class="reference internal" href="#new-files" id="id115">New files</a></li>
 324 <li><a class="reference internal" href="#saving-files" id="id116">Saving files</a></li>
 325 <li><a class="reference internal" href="#id3" id="id117">Miscellaneous</a></li>
 326 </ul>
 327 </li>
 328 <li><a class="reference internal" href="#tools-preferences" id="id118">Tools preferences</a><ul>
 329 <li><a class="reference internal" href="#tool-paths" id="id119">Tool paths</a></li>
 330 <li><a class="reference internal" href="#commands" id="id120">Commands</a></li>
 331 </ul>
 332 </li>
 333 <li><a class="reference internal" href="#template-preferences" id="id121">Template preferences</a><ul>
 334 <li><a class="reference internal" href="#template-data" id="id122">Template data</a></li>
 335 </ul>
 336 </li>
 337 <li><a class="reference internal" href="#keybinding-preferences" id="id123">Keybinding preferences</a></li>
 338 <li><a class="reference internal" href="#printing-preferences" id="id124">Printing preferences</a></li>
 339 <li><a class="reference internal" href="#various-preferences" id="id125">Various preferences</a></li>
 340 <li><a class="reference internal" href="#terminal-vte-preferences" id="id126">Terminal (VTE) preferences</a><ul>
 341 <li><a class="reference internal" href="#terminal-widget" id="id127">Terminal widget</a></li>
 342 </ul>
 343 </li>
 344 </ul>
 345 </li>
 346 <li><a class="reference internal" href="#project-management" id="id128">Project management</a><ul>
 347 <li><a class="reference internal" href="#new-project" id="id129">New project</a></li>
 348 <li><a class="reference internal" href="#project-properties" id="id130">Project properties</a></li>
 349 <li><a class="reference internal" href="#open-project" id="id131">Open project</a></li>
 350 <li><a class="reference internal" href="#close-project" id="id132">Close project</a></li>
 351 </ul>
 352 </li>
 353 <li><a class="reference internal" href="#build-menu" id="id133">Build menu</a><ul>
 354 <li><a class="reference internal" href="#indicators" id="id134">Indicators</a></li>
 355 <li><a class="reference internal" href="#default-build-menu-items" id="id135">Default build menu items</a><ul>
 356 <li><a class="reference internal" href="#compile" id="id136">Compile</a></li>
 357 <li><a class="reference internal" href="#build" id="id137">Build</a></li>
 358 <li><a class="reference internal" href="#make" id="id138">Make</a></li>
 359 <li><a class="reference internal" href="#make-custom-target" id="id139">Make custom target</a></li>
 360 <li><a class="reference internal" href="#make-object" id="id140">Make object</a></li>
 361 <li><a class="reference internal" href="#next-error" id="id141">Next error</a></li>
 362 <li><a class="reference internal" href="#previous-error" id="id142">Previous error</a></li>
 363 <li><a class="reference internal" href="#execute" id="id143">Execute</a></li>
 364 <li><a class="reference internal" href="#stopping-running-processes" id="id144">Stopping running processes</a><ul>
 365 <li><a class="reference internal" href="#terminal-emulators" id="id145">Terminal emulators</a></li>
 366 </ul>
 367 </li>
 368 <li><a class="reference internal" href="#set-build-commands" id="id146">Set build commands</a></li>
 369 </ul>
 370 </li>
 371 <li><a class="reference internal" href="#build-menu-configuration" id="id147">Build menu configuration</a></li>
 372 <li><a class="reference internal" href="#build-menu-commands-dialog" id="id148">Build menu commands dialog</a><ul>
 373 <li><a class="reference internal" href="#substitutions-in-commands-and-working-directories" id="id149">Substitutions in commands and working directories</a></li>
 374 <li><a class="reference internal" href="#build-menu-keyboard-shortcuts" id="id150">Build menu keyboard shortcuts</a></li>
 375 <li><a class="reference internal" href="#old-settings" id="id151">Old settings</a></li>
 376 </ul>
 377 </li>
 378 </ul>
 379 </li>
 380 <li><a class="reference internal" href="#printing-support" id="id152">Printing support</a></li>
 381 <li><a class="reference internal" href="#plugins" id="id153">Plugins</a><ul>
 382 <li><a class="reference internal" href="#plugin-manager" id="id154">Plugin manager</a></li>
 383 </ul>
 384 </li>
 385 <li><a class="reference internal" href="#keybindings" id="id155">Keybindings</a><ul>
 386 <li><a class="reference internal" href="#switching-documents" id="id156">Switching documents</a></li>
 387 <li><a class="reference internal" href="#configurable-keybindings" id="id157">Configurable keybindings</a><ul>
 388 <li><a class="reference internal" href="#file-keybindings" id="id158">File keybindings</a></li>
 389 <li><a class="reference internal" href="#editor-keybindings" id="id159">Editor keybindings</a></li>
 390 <li><a class="reference internal" href="#clipboard-keybindings" id="id160">Clipboard keybindings</a></li>
 391 <li><a class="reference internal" href="#select-keybindings" id="id161">Select keybindings</a></li>
 392 <li><a class="reference internal" href="#insert-keybindings" id="id162">Insert keybindings</a></li>
 393 <li><a class="reference internal" href="#format-keybindings" id="id163">Format keybindings</a></li>
 394 <li><a class="reference internal" href="#settings-keybindings" id="id164">Settings keybindings</a></li>
 395 <li><a class="reference internal" href="#search-keybindings" id="id165">Search keybindings</a></li>
 396 <li><a class="reference internal" href="#go-to-keybindings" id="id166">Go to keybindings</a></li>
 397 <li><a class="reference internal" href="#view-keybindings" id="id167">View keybindings</a></li>
 398 <li><a class="reference internal" href="#focus-keybindings" id="id168">Focus keybindings</a></li>
 399 <li><a class="reference internal" href="#notebook-tab-keybindings" id="id169">Notebook tab keybindings</a></li>
 400 <li><a class="reference internal" href="#document-keybindings" id="id170">Document keybindings</a></li>
 401 <li><a class="reference internal" href="#build-keybindings" id="id171">Build keybindings</a></li>
 402 <li><a class="reference internal" href="#tools-keybindings" id="id172">Tools keybindings</a></li>
 403 <li><a class="reference internal" href="#help-keybindings" id="id173">Help keybindings</a></li>
 404 </ul>
 405 </li>
 406 </ul>
 407 </li>
 408 </ul>
 409 </li>
 410 <li><a class="reference internal" href="#configuration-files" id="id174">Configuration files</a><ul>
 411 <li><a class="reference internal" href="#configuration-file-paths" id="id175">Configuration file paths</a><ul>
 412 <li><a class="reference internal" href="#paths-on-unix-like-systems" id="id176">Paths on Unix-like systems</a></li>
 413 </ul>
 414 </li>
 415 <li><a class="reference internal" href="#tools-menu-items" id="id177">Tools menu items</a></li>
 416 <li><a class="reference internal" href="#global-configuration-file" id="id178">Global configuration file</a></li>
 417 <li><a class="reference internal" href="#filetype-definition-files" id="id179">Filetype definition files</a><ul>
 418 <li><a class="reference internal" href="#filenames" id="id180">Filenames</a></li>
 419 <li><a class="reference internal" href="#system-files" id="id181">System files</a></li>
 420 <li><a class="reference internal" href="#user-files" id="id182">User files</a></li>
 421 <li><a class="reference internal" href="#custom-filetypes" id="id183">Custom filetypes</a><ul>
 422 <li><a class="reference internal" href="#creating-a-custom-filetype-from-an-existing-filetype" id="id184">Creating a custom filetype from an existing filetype</a></li>
 423 </ul>
 424 </li>
 425 <li><a class="reference internal" href="#filetype-configuration" id="id185">Filetype configuration</a><ul>
 426 <li><a class="reference internal" href="#styling-section" id="id186">[styling] section</a><ul>
 427 <li><a class="reference internal" href="#using-a-named-style" id="id187">Using a named style</a></li>
 428 <li><a class="reference internal" href="#reading-styles-from-another-filetype" id="id188">Reading styles from another filetype</a></li>
 429 </ul>
 430 </li>
 431 <li><a class="reference internal" href="#keywords-section" id="id189">[keywords] section</a></li>
 432 <li><a class="reference internal" href="#lexer-properties-section" id="id190">[lexer_properties] section</a></li>
 433 <li><a class="reference internal" href="#settings-section" id="id191">[settings] section</a></li>
 434 <li><a class="reference internal" href="#indentation-section" id="id192">[indentation] section</a></li>
 435 <li><a class="reference internal" href="#build-settings-section" id="id193">[build_settings] section</a></li>
 436 </ul>
 437 </li>
 438 <li><a class="reference internal" href="#special-file-filetypes-common" id="id194">Special file filetypes.common</a><ul>
 439 <li><a class="reference internal" href="#named-styles-section" id="id195">[named_styles] section</a></li>
 440 <li><a class="reference internal" href="#id4" id="id196">[styling] section</a></li>
 441 <li><a class="reference internal" href="#id5" id="id197">[settings] section</a></li>
 442 </ul>
 443 </li>
 444 </ul>
 445 </li>
 446 <li><a class="reference internal" href="#filetype-extensions" id="id198">Filetype extensions</a></li>
 447 <li><a class="reference internal" href="#filetype-group-membership" id="id199">Filetype group membership</a></li>
 448 <li><a class="reference internal" href="#preferences-file-format" id="id200">Preferences file format</a><ul>
 449 <li><a class="reference internal" href="#build-menu-section" id="id201">[build-menu] section</a></li>
 450 </ul>
 451 </li>
 452 <li><a class="reference internal" href="#project-file-format" id="id202">Project file format</a><ul>
 453 <li><a class="reference internal" href="#build-menu-additions" id="id203">[build-menu] additions</a></li>
 454 </ul>
 455 </li>
 456 <li><a class="reference internal" href="#templates" id="id204">Templates</a><ul>
 457 <li><a class="reference internal" href="#template-meta-data" id="id205">Template meta data</a></li>
 458 <li><a class="reference internal" href="#file-templates" id="id206">File templates</a><ul>
 459 <li><a class="reference internal" href="#adding-file-templates" id="id207">Adding file templates</a></li>
 460 </ul>
 461 </li>
 462 <li><a class="reference internal" href="#customizing-templates" id="id208">Customizing templates</a><ul>
 463 <li><a class="reference internal" href="#template-wildcards" id="id209">Template wildcards</a><ul>
 464 <li><a class="reference internal" href="#special-command-wildcard" id="id210">Special {command:} wildcard</a></li>
 465 </ul>
 466 </li>
 467 </ul>
 468 </li>
 469 </ul>
 470 </li>
 471 <li><a class="reference internal" href="#customizing-the-toolbar" id="id211">Customizing the toolbar</a><ul>
 472 <li><a class="reference internal" href="#manually-editing-the-toolbar-layout" id="id212">Manually editing the toolbar layout</a></li>
 473 <li><a class="reference internal" href="#available-toolbar-elements" id="id213">Available toolbar elements</a></li>
 474 </ul>
 475 </li>
 476 </ul>
 477 </li>
 478 <li><a class="reference internal" href="#plugin-documentation" id="id214">Plugin documentation</a><ul>
 479 <li><a class="reference internal" href="#html-characters" id="id215">HTML Characters</a><ul>
 480 <li><a class="reference internal" href="#insert-entity-dialog" id="id216">Insert entity dialog</a></li>
 481 <li><a class="reference internal" href="#replace-special-chars-by-its-entity" id="id217">Replace special chars by its entity</a><ul>
 482 <li><a class="reference internal" href="#at-typing-time" id="id218">At typing time</a></li>
 483 <li><a class="reference internal" href="#bulk-replacement" id="id219">Bulk replacement</a></li>
 484 </ul>
 485 </li>
 486 </ul>
 487 </li>
 488 <li><a class="reference internal" href="#save-actions" id="id220">Save Actions</a><ul>
 489 <li><a class="reference internal" href="#instant-save" id="id221">Instant Save</a></li>
 490 <li><a class="reference internal" href="#backup-copy" id="id222">Backup Copy</a></li>
 491 </ul>
 492 </li>
 493 </ul>
 494 </li>
 495 <li><a class="reference internal" href="#contributing-to-this-document" id="id223">Contributing to this document</a></li>
 496 <li><a class="reference internal" href="#scintilla-keyboard-commands" id="id224">Scintilla keyboard commands</a><ul>
 497 <li><a class="reference internal" href="#keyboard-commands" id="id225">Keyboard commands</a></li>
 498 </ul>
 499 </li>
 500 <li><a class="reference internal" href="#tips-and-tricks" id="id226">Tips and tricks</a><ul>
 501 <li><a class="reference internal" href="#document-notebook" id="id227">Document notebook</a></li>
 502 <li><a class="reference internal" href="#editor" id="id228">Editor</a></li>
 503 <li><a class="reference internal" href="#interface" id="id229">Interface</a></li>
 504 <li><a class="reference internal" href="#gtk-related" id="id230">GTK-related</a></li>
 505 </ul>
 506 </li>
 507 <li><a class="reference internal" href="#compile-time-options" id="id231">Compile-time options</a><ul>
 508 <li><a class="reference internal" href="#src-geany-h" id="id232">src/geany.h</a></li>
 509 <li><a class="reference internal" href="#project-h" id="id233">project.h</a></li>
 510 <li><a class="reference internal" href="#editor-h" id="id234">editor.h</a></li>
 511 <li><a class="reference internal" href="#keyfile-c" id="id235">keyfile.c</a></li>
 512 <li><a class="reference internal" href="#build-c" id="id236">build.c</a></li>
 513 </ul>
 514 </li>
 515 <li><a class="reference internal" href="#gnu-general-public-license" id="id237">GNU General Public License</a></li>
 516 <li><a class="reference internal" href="#license-for-scintilla-and-scite" id="id238">License for Scintilla and SciTE</a></li>
 517 </ul>
 518 </div>
 519 <div class="section" id="introduction">
 520 <h1><a class="toc-backref" href="#id7">Introduction</a></h1>
 521 <div class="section" id="about-geany">
 522 <h2><a class="toc-backref" href="#id8">About Geany</a></h2>
 523 <p>Geany is a small and lightweight Integrated Development Environment. It
 524 was developed to provide a small and fast IDE, which has only a few
 525 dependencies on other packages. Another goal was to be as independent
 526 as possible from a particular Desktop Environment like KDE or GNOME -
 527 Geany only requires the GTK2 runtime libraries.</p>
 528 <p>Some basic features of Geany:</p>
 529 <ul class="simple">
 530 <li>Syntax highlighting</li>
 531 <li>Code folding</li>
 532 <li>Autocompletion of symbols/words</li>
 533 <li>Construct completion/snippets</li>
 534 <li>Auto-closing of XML and HTML tags</li>
 535 <li>Calltips</li>
 536 <li>Many supported filetypes including C, Java, PHP, HTML, Python, Perl,
 537 Pascal, and others</li>
 538 <li>Symbol lists</li>
 539 <li>Code navigation</li>
 540 <li>Build system to compile and execute your code</li>
 541 <li>Simple project management</li>
 542 <li>Plugin interface</li>
 543 </ul>
 544 </div>
 545 <div class="section" id="where-to-get-it">
 546 <h2><a class="toc-backref" href="#id9">Where to get it</a></h2>
 547 <p>You can obtain Geany from <a class="reference external" href="http://www.geany.org/">http://www.geany.org/</a> or perhaps also from
 548 your distribution. For a list of available packages, please see
 549 <a class="reference external" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
 550 </div>
 551 <div class="section" id="license">
 552 <h2><a class="toc-backref" href="#id10">License</a></h2>
 553 <p>Geany is distributed under the terms of the GNU General Public License
 554 as published by the Free Software Foundation; either version 2 of
 555 the License, or (at your option) any later version. A copy of this
 556 license can be found in the file COPYING included with the source
 557 code of this program and in the chapter, <a class="reference internal" href="#gnu-general-public-license">GNU General Public License</a>.</p>
 558 <p>The included Scintilla library (found in the subdirectory
 559 <tt class="docutils literal">scintilla/</tt>) has its own license, which can be found in the chapter,
 560 <a class="reference internal" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
 561 </div>
 562 <div class="section" id="about-this-document">
 563 <h2><a class="toc-backref" href="#id11">About this document</a></h2>
 564 <p>This documentation is available in HTML and text formats.
 565 The latest version can always be found at <a class="reference external" href="http://www.geany.org/">http://www.geany.org/</a>.</p>
 566 <p>If you want to contribute to it, see <a class="reference internal" href="#contributing-to-this-document">Contributing to this document</a>.</p>
 567 </div>
 568 </div>
 569 <div class="section" id="installation">
 570 <h1><a class="toc-backref" href="#id12">Installation</a></h1>
 571 <div class="section" id="requirements">
 572 <h2><a class="toc-backref" href="#id13">Requirements</a></h2>
 573 <p>You will need the GTK (&gt;= 2.12.0) libraries and their dependencies
 574 (Pango, GLib and ATK). Your distro should provide packages for these,
 575 usually installed by default. For Windows, you can download an installer
 576 from the website which bundles these libraries.</p>
 577 </div>
 578 <div class="section" id="binary-packages">
 579 <h2><a class="toc-backref" href="#id14">Binary packages</a></h2>
 580 <p>There are many binary packages available. For an up-to-date but maybe
 581 incomplete list see <a class="reference external" href="http://www.geany.org/Download/ThirdPartyPackages">http://www.geany.org/Download/ThirdPartyPackages</a>.</p>
 582 </div>
 583 <div class="section" id="source-compilation">
 584 <h2><a class="toc-backref" href="#id15">Source compilation</a></h2>
 585 <p>Compiling Geany is quite easy.
 586 To do so, you need the GTK (&gt;= 2.12.0) libraries and header files.
 587 You also need the Pango, GLib and ATK libraries and header files.
 588 All these files are available at <a class="reference external" href="http://www.gtk.org">http://www.gtk.org</a>, but very often
 589 your distro will provide development packages to save the trouble of
 590 building these yourself.</p>
 591 <p>Furthermore you need, of course, a C and C++ compiler. The GNU versions
 592 of these tools are recommended.</p>
 593 <div class="section" id="autotools-based-build-system">
 594 <h3><a class="toc-backref" href="#id16">Autotools based build system</a></h3>
 595 <p>The Autotools based build system is very mature and has been well tested.
 596 To use it, you just need the Make tool, preferably GNU Make.</p>
 597 <p>Then run the following commands:</p>
 598 <pre class="literal-block">
 599 $ ./configure
 600 $ make
 601 </pre>
 602 <p>Then as root:</p>
 603 <pre class="literal-block">
 604 % make install
 605 </pre>
 606 </div>
 607 <div class="section" id="waf-based-build-system">
 608 <h3><a class="toc-backref" href="#id17">Waf based build system</a></h3>
 609 <p>The Waf build system is still quite young and under heavy development but already in a
 610 usable state. In contrast to the Autotools system, Waf needs Python. So before using Waf, you need
 611 to install Python on your system.
 612 The advantage of the Waf build system over the Autotools based build system is that the whole
 613 build process might be a bit faster. Especially when you use the Waf
 614 cache feature for repetitive builds (e.g. when changing only a few source files
 615 to test something) will become much faster since Waf will cache and re-use the
 616 unchanged built files and only compile the changed code again. See <a class="reference internal" href="#waf-cache">Waf Cache</a> for details.
 617 To build Geany with Waf as run:</p>
 618 <pre class="literal-block">
 619 $ ./waf configure
 620 $ ./waf build
 621 </pre>
 622 <p>Then as root:</p>
 623 <pre class="literal-block">
 624 % ./waf install
 625 </pre>
 626 <div class="section" id="waf-cache">
 627 <h4><a class="toc-backref" href="#id18">Waf cache</a></h4>
 628 <p>The Waf build system has a nice and interesting feature which can help  to avoid
 629 a lot of unnecessary rebuilding of unchanged code. This often happens when developing new features
 630 or trying to debug something in Geany.
 631 Waf is able to store and retrieve the object files from a cache. This cache is declared
 632 using the environment variable <tt class="docutils literal">WAFCACHE</tt>.
 633 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
 634 this, you first need to create this directory:</p>
 635 <pre class="literal-block">
 636 $ mkdir -p ~/.cache/waf
 637 </pre>
 638 <p>then add the environment variable to your shell configuration (the following example is for
 639 Bash and should be adjusted to your used shell):</p>
 640 <pre class="literal-block">
 641 export WAFCACHE=/home/username/.cache/waf
 642 </pre>
 643 <p>Remember to replace <tt class="docutils literal">username</tt> with your actual username.</p>
 644 <p>More information about the Waf cache feature are available at
 645 <a class="reference external" href="http://code.google.com/p/waf/wiki/CacheObjectFiles">http://code.google.com/p/waf/wiki/CacheObjectFiles</a>.</p>
 646 <div class="section" id="cleaning-the-cache">
 647 <h5><a class="toc-backref" href="#id19">Cleaning the cache</a></h5>
 648 <p>You should be careful about the size of the cache directory as it may
 649 grow rapidly over time.
 650 Waf doesn't do any cleaning or other house-keeping of the cache yet, so you need to keep it
 651 clean by yourself.
 652 An easy way to keep it clean is to run the following command regularly to remove old
 653 cached files:</p>
 654 <pre class="literal-block">
 655 $ find /home/username/.cache/waf -mtime +14 -exec rm {} \;
 656 </pre>
 657 <p>This will delete all files in the cache directory which are older than 14 days.</p>
 658 <p>For details about the <tt class="docutils literal">find</tt> command and its options, check its manual page.</p>
 659 </div>
 660 </div>
 661 </div>
 662 <div class="section" id="custom-installation">
 663 <h3><a class="toc-backref" href="#id20">Custom installation</a></h3>
 664 <p>The configure script supports several common options, for a detailed
 665 list, type:</p>
 666 <pre class="literal-block">
 667 $ ./configure --help
 668 </pre>
 669 <dl class="docutils">
 670 <dt>or::</dt>
 671 <dd>$ ./waf --help</dd>
 672 </dl>
 673 <p>(depending on which build system you use).</p>
 674 <p>You may also want to read the INSTALL file for advanced installation
 675 options.</p>
 676 <ul class="simple">
 677 <li>See also <a class="reference internal" href="#compile-time-options">Compile-time options</a>.</li>
 678 </ul>
 679 </div>
 680 <div class="section" id="dynamic-linking-loader-support-and-vte">
 681 <h3><a class="toc-backref" href="#id21">Dynamic linking loader support and VTE</a></h3>
 682 <p>In the case that your system lacks dynamic linking loader support, you
 683 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>
 684 script. This prevents compiling Geany with dynamic linking loader
 685 support for automatically loading <tt class="docutils literal">libvte.so.4</tt> if available.</p>
 686 </div>
 687 <div class="section" id="build-problems">
 688 <h3><a class="toc-backref" href="#id22">Build problems</a></h3>
 689 <p>If there are any errors during compilation, check your build
 690 environment and try to find the error, otherwise contact the mailing
 691 list or one the authors. Sometimes you might need to ask for specific
 692 help from your distribution.</p>
 693 </div>
 694 </div>
 695 <div class="section" id="installation-prefix">
 696 <h2><a class="toc-backref" href="#id23">Installation prefix</a></h2>
 697 <p>If you want to find Geany's system files after installation you may
 698 want to know the installation prefix.</p>
 699 <p>Pass the <tt class="docutils literal"><span class="pre">--print-prefix</span></tt> option to Geany to check this - see
 700 <a class="reference internal" href="#command-line-options">Command line options</a>. The first path is the prefix.</p>
 701 <p>On Unix-like systems this is commonly <tt class="docutils literal">/usr</tt> if you installed from
 702 a binary package, or <tt class="docutils literal">/usr/local</tt> if you build from source.</p>
 703 <div class="note">
 704 <p class="first admonition-title">Note</p>
 705 <p class="last">Editing system files is not necessary as you can use the
 706 per-user configuration files instead, which don't need root
 707 permissions. See <a class="reference internal" href="#configuration-files">Configuration files</a>.</p>
 708 </div>
 709 </div>
 710 </div>
 711 <div class="section" id="usage">
 712 <h1><a class="toc-backref" href="#id24">Usage</a></h1>
 713 <div class="section" id="getting-started">
 714 <h2><a class="toc-backref" href="#id25">Getting started</a></h2>
 715 <p>You can start Geany in the following ways:</p>
 716 <ul>
 717 <li><p class="first">From the Desktop Environment menu:</p>
 718 <p>Choose in your application menu of your used Desktop Environment:
 719 Development --&gt; Geany.</p>
 720 </li>
 721 <li><p class="first">From the command line:</p>
 722 <p>To start Geany from a command line, type the following and press
 723 Return:</p>
 724 <pre class="literal-block">
 725 % geany
 726 </pre>
 727 </li>
 728 </ul>
 729 </div>
 730 <div class="section" id="the-geany-workspace">
 731 <h2><a class="toc-backref" href="#id26">The Geany workspace</a></h2>
 732 <p>The Geany window is shown in the following figure:</p>
 733 <img alt="./images/main_window.png" src="./images/main_window.png" />
 734 <p>The workspace has the following parts:</p>
 735 <ul class="simple">
 736 <li>The menu.</li>
 737 <li>An optional toolbar.</li>
 738 <li>An optional sidebar that can show the following tabs:<ul>
 739 <li>Documents - A document list, and</li>
 740 <li>Symbols - A list of symbols in your code.</li>
 741 </ul>
 742 </li>
 743 <li>The main editor window.</li>
 744 <li>An optional message window which can show the following tabs:<ul>
 745 <li>Status - A list of status messages.</li>
 746 <li>Compiler - The output of compiling or building programs.</li>
 747 <li>Messages - Results of 'Find Usage', 'Find Usage' 'Find in Files' and other actions</li>
 748 <li>Scribble - A text scratchpad for any use.</li>
 749 <li>Terminal - An optional terminal window.</li>
 750 </ul>
 751 </li>
 752 <li>A status bar</li>
 753 </ul>
 754 <p>Most of these can be configured in the <a class="reference internal" href="#interface-preferences">Interface preferences</a>, the
 755 <a class="reference internal" href="#view-menu">View menu</a>, or the popup menu for the relevant area.</p>
 756 <p>Additional tabs may be added to the sidebar and message window by plugins.</p>
 757 <p>The position of the tabs can be selected in the interface preferences.</p>
 758 <p>The sizes of the sidebar and message window can be adjusted by
 759 dragging the dividers.</p>
 760 </div>
 761 <div class="section" id="command-line-options">
 762 <h2><a class="toc-backref" href="#id27">Command line options</a></h2>
 763 <table border="1" class="docutils">
 764 <colgroup>
 765 <col width="9%" />
 766 <col width="18%" />
 767 <col width="72%" />
 768 </colgroup>
 769 <thead valign="bottom">
 770 <tr><th class="head">Short option</th>
 771 <th class="head">Long option</th>
 772 <th class="head">Function</th>
 773 </tr>
 774 </thead>
 775 <tbody valign="top">
 776 <tr><td><em>none</em></td>
 777 <td>+number</td>
 778 <td>Set initial line number for the first opened file
 779 (same as --line, do not put a space between the + sign
 780 and the number). E.g. &quot;geany +7 foo.bar&quot; will open the
 781 file foo.bar and place the cursor in line 7.</td>
 782 </tr>
 783 <tr><td><em>none</em></td>
 784 <td>--column</td>
 785 <td>Set initial column number for the first opened file.</td>
 786 </tr>
 787 <tr><td>-c dir_name</td>
 788 <td>--config=directory_name</td>
 789 <td>Use an alternate configuration directory. The default
 790 configuration directory is <tt class="docutils literal"><span class="pre">~/.config/geany/</span></tt> and that
 791 is where <tt class="docutils literal">geany.conf</tt> and other configuration files
 792 reside.</td>
 793 </tr>
 794 <tr><td><em>none</em></td>
 795 <td>--ft-names</td>
 796 <td>Print a list of Geany's internal filetype names (useful
 797 for snippets configuration).</td>
 798 </tr>
 799 <tr><td>-g</td>
 800 <td>--generate-tags</td>
 801 <td>Generate a global tags file (see
 802 <a class="reference internal" href="#generating-a-global-tags-file">Generating a global tags file</a>).</td>
 803 </tr>
 804 <tr><td>-P</td>
 805 <td>--no-preprocessing</td>
 806 <td>Don't preprocess C/C++ files when generating tags.</td>
 807 </tr>
 808 <tr><td>-i</td>
 809 <td>--new-instance</td>
 810 <td>Do not open files in a running instance, force opening
 811 a new instance. Only available if Geany was compiled
 812 with support for Sockets.</td>
 813 </tr>
 814 <tr><td>-l</td>
 815 <td>--line</td>
 816 <td>Set initial line number for the first opened file.</td>
 817 </tr>
 818 <tr><td><em>none</em></td>
 819 <td>--list-documents</td>
 820 <td>Return a list of open documents in a running Geany
 821 instance.
 822 This can be used to read the currently opened documents in
 823 Geany from an external script or tool. The returned list
 824 is separated by newlines (LF) and consists of the full,
 825 UTF-8 encoded filenames of the documents.
 826 Only available if Geany was compiled with support for
 827 Sockets.</td>
 828 </tr>
 829 <tr><td>-m</td>
 830 <td>--no-msgwin</td>
 831 <td>Do not show the message window. Use this option if you
 832 do not need compiler messages or VTE support.</td>
 833 </tr>
 834 <tr><td>-n</td>
 835 <td>--no-ctags</td>
 836 <td>Do not load symbol completion and call tip data. Use this
 837 option if you do not want to use them.</td>
 838 </tr>
 839 <tr><td>-p</td>
 840 <td>--no-plugins</td>
 841 <td>Do not load plugins or plugin support.</td>
 842 </tr>
 843 <tr><td><em>none</em></td>
 844 <td>--print-prefix</td>
 845 <td>Print installation prefix, the data directory, the lib
 846 directory and the locale directory (in that order) to
 847 stdout, one line each. This is mainly intended for plugin
 848 authors to detect installation paths.</td>
 849 </tr>
 850 <tr><td>-s</td>
 851 <td>--no-session</td>
 852 <td>Do not load the previous session's files.</td>
 853 </tr>
 854 <tr><td>-t</td>
 855 <td>--no-terminal</td>
 856 <td>Do not load terminal support. Use this option if you do
 857 not want to load the virtual terminal emulator widget
 858 at startup. If you do not have <tt class="docutils literal">libvte.so.4</tt> installed,
 859 then terminal-support is automatically disabled. Only
 860 available if Geany was compiled with support for VTE.</td>
 861 </tr>
 862 <tr><td><em>none</em></td>
 863 <td>--socket-file</td>
 864 <td><p class="first">Use this socket filename for communication with a
 865 running Geany instance. This can be used with the following
 866 command to execute Geany on the current workspace:</p>
 867 <pre class="last literal-block">
 868 geany --socket-file=/tmp/geany-sock-$(xprop -root _NET_CURRENT_DESKTOP | awk '{print $3}')
 869 </pre>
 870 </td>
 871 </tr>
 872 <tr><td><em>none</em></td>
 873 <td>--vte-lib</td>
 874 <td>Specify explicitly the path including filename or only
 875 the filename to the VTE library, e.g.
 876 <tt class="docutils literal">/usr/lib/libvte.so</tt> or <tt class="docutils literal">libvte.so</tt>. This option is
 877 only needed when the auto-detection does not work. Only
 878 available if Geany was compiled with support for VTE.</td>
 879 </tr>
 880 <tr><td>-v</td>
 881 <td>--verbose</td>
 882 <td>Be verbose (print useful status messages).</td>
 883 </tr>
 884 <tr><td>-V</td>
 885 <td>--version</td>
 886 <td>Show version information and exit.</td>
 887 </tr>
 888 <tr><td>-?</td>
 889 <td>--help</td>
 890 <td>Show help information and exit.</td>
 891 </tr>
 892 <tr><td><em>none</em></td>
 893 <td>[files ...]</td>
 894 <td><p class="first">Open all given files at startup. This option causes
 895 Geany to ignore loading stored files from the last
 896 session (if enabled).
 897 Geany also recognizes line and column information when
 898 appended to the filename with colons, e.g.
 899 &quot;geany foo.bar:10:5&quot; will open the file foo.bar and
 900 place the cursor in line 10 at column 5.</p>
 901 <p class="last">Projects can also be opened but a project file (*.geany)
 902 must be the first non-option argument. All additionally
 903 given files are ignored.</p>
 904 </td>
 905 </tr>
 906 </tbody>
 907 </table>
 908 <p>You can also pass line number and column number information, e.g.:</p>
 909 <pre class="literal-block">
 910 geany some_file.foo:55:4
 911 </pre>
 912 <p>Geany supports all generic GTK options, a list is available on the
 913 help screen.</p>
 914 </div>
 915 <div class="section" id="general">
 916 <h2><a class="toc-backref" href="#id28">General</a></h2>
 917 <div class="section" id="startup">
 918 <h3><a class="toc-backref" href="#id29">Startup</a></h3>
 919 <p>At startup, Geany loads all files from the last time Geany was
 920 launched. You can disable this feature in the preferences dialog
 921 (see <a class="reference internal" href="#general-startup-preferences">General Startup preferences</a>). If you specify some
 922 files on the command line, only these files will be opened, but you
 923 can find the files from the last session in the file menu under the
 924 &quot;Recent files&quot; item. By default this contains the last 10 recently
 925 opened files. You can change the number of recently opened files in
 926 the preferences dialog.</p>
 927 <p>You can start several instances of Geany, but only the first will
 928 load files from the last session. To run a second instance of Geany,
 929 do not specify any filenames on the command-line, or disable opening
 930 files in a running instance using the appropriate command line option.</p>
 931 </div>
 932 <div class="section" id="opening-files-from-the-command-line-in-a-running-instance">
 933 <h3><a class="toc-backref" href="#id30">Opening files from the command-line in a running instance</a></h3>
 934 <p>Geany detects if there is an an instance of itself already running and opens files
 935 from the command-line in that instance. So, Geany can
 936 be used to view and edit files by opening them from other programs
 937 such as a file manager.</p>
 938 <p>You can also pass line number and column number information, e.g.:</p>
 939 <pre class="literal-block">
 940 geany some_file.foo:55:4
 941 </pre>
 942 <p>This would open the file <tt class="docutils literal">some_file.foo</tt> with the cursor on line 55,
 943 column 4.</p>
 944 <p>If you do not like this for some reason, you can disable using the first
 945 instance by using the appropriate command line option -- see the section
 946 called <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
 947 </div>
 948 <div class="section" id="virtual-terminal-emulator-widget-vte">
 949 <h3><a class="toc-backref" href="#id31">Virtual terminal emulator widget (VTE)</a></h3>
 950 <p>If you have installed <tt class="docutils literal">libvte.so</tt> on your system, it is loaded
 951 automatically by Geany, and you will have a terminal widget in the
 952 notebook at the bottom.</p>
 953 <p>If Geany cannot find any <tt class="docutils literal">libvte.so</tt> at startup, the terminal widget
 954 will not be loaded. So there is no need to install the package containing
 955 this file in order to run Geany. Additionally, you can disable the use
 956 of the terminal widget by command line option, for more information
 957 see the section called <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
 958 <p>You can use this terminal (from now on called VTE) much as you would
 959 a terminal program like xterm. There is basic clipboard support. You
 960 can paste the contents of the clipboard by pressing the right mouse
 961 button to open the popup menu, and choosing Paste. To copy text from
 962 the VTE, just select the desired text and then press the right mouse
 963 button and choose Copy from the popup menu. On systems running the
 964 X Window System you can paste the last selected text by pressing the
 965 middle mouse button in the VTE (on 2-button mice, the middle button
 966 can often be simulated by pressing both mouse buttons together).</p>
 967 <p>In the preferences dialog you can specify a shell which should be
 968 started in the VTE. To make the specified shell a login shell just
 969 use the appropriate command line options for the shell. These options
 970 should be found in the manual page of the shell. For zsh and bash
 971 you can use the argument <tt class="docutils literal"><span class="pre">--login</span></tt>.</p>
 972 <div class="note">
 973 <p class="first admonition-title">Note</p>
 974 <p class="last">Geany tries to load <tt class="docutils literal">libvte.so</tt>. If this fails, it tries to load
 975 some other filenames. If this fails too, you should check whether you
 976 installed libvte correctly. Again note, Geany will run without this
 977 library.</p>
 978 </div>
 979 <p>It could be, that the library is called something else than
 980 <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
 981 please set a link to the correct file (as root):</p>
 982 <pre class="literal-block">
 983 # ln -s /usr/lib/libvte.so.X /usr/lib/libvte.so
 984 </pre>
 985 <p>Obviously, you have to adjust the paths and set X to the number of your
 986 <tt class="docutils literal">libvte.so</tt>.</p>
 987 <p>You can also specify the filename of the VTE library to use on the command
 988 line (see the section called <a class="reference internal" href="#command-line-options">Command line options</a>) or at compile time
 989 by specifying the command line option <tt class="docutils literal"><span class="pre">--with-vte-module-path</span></tt> to
 990 ./configure.</p>
 991 </div>
 992 <div class="section" id="defining-own-widget-styles-using-gtkrc-2-0">
 993 <h3><a class="toc-backref" href="#id32">Defining own widget styles using .gtkrc-2.0</a></h3>
 994 <p>You can define your widget style for many of Geany's GUI parts. To
 995 do this, just edit your <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt> (usually found in your home
 996 directory on UNIX-like systems and in the etc subdirectory of your
 997 Geany installation on Windows).</p>
 998 <p>To have a defined style used by Geany you must assign it to
 999 at least one of Geany's widgets. For example use the following line:</p>
1000 <pre class="literal-block">
1001 widget &quot;Geany*&quot; style &quot;geanyStyle&quot;
1002 </pre>
1003 <p>This would assign your style &quot;geany_style&quot; to all Geany
1004 widgets. You can also assign styles only to specific widgets. At the
1005 moment you can use the following widgets:</p>
1006 <ul class="simple">
1007 <li>GeanyMainWindow</li>
1008 <li>GeanyEditMenu</li>
1009 <li>GeanyToolbarMenu</li>
1010 <li>GeanyDialog</li>
1011 <li>GeanyDialogPrefs</li>
1012 <li>GeanyDialogProject</li>
1013 <li>GeanyDialogSearch</li>
1014 <li>GeanyMenubar</li>
1015 <li>GeanyToolbar</li>
1016 </ul>
1017 <p>An example of a simple <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt>:</p>
1018 <pre class="literal-block">
1019 style &quot;geanyStyle&quot;
1020 {
1021     font_name=&quot;Sans 12&quot;
1022 }
1023 widget &quot;GeanyMainWindow&quot; style &quot;geanyStyle&quot;
1024
1025 style &quot;geanyStyle&quot;
1026 {
1027     font_name=&quot;Sans 10&quot;
1028 }
1029 widget &quot;GeanyPrefsDialog&quot; style &quot;geanyStyle&quot;
1030 </pre>
1031 </div>
1032 </div>
1033 <div class="section" id="documents">
1034 <h2><a class="toc-backref" href="#id33">Documents</a></h2>
1035 <div class="section" id="switching-between-documents">
1036 <h3><a class="toc-backref" href="#id34">Switching between documents</a></h3>
1037 <p>The documents list and the editor tabs are two different ways
1038 to switch between documents using the mouse. When you hit the key
1039 combination to move between tabs, the order is determined by the tab
1040 order. It is not alphabetical as shown in the documents list
1041 (regardless of whether or not editor tabs are visible).</p>
1042 <p>See the <a class="reference internal" href="#notebook-tab-keybindings">Notebook tab keybindings</a> section for useful
1043 shortcuts including for Most-Recently-Used document switching.</p>
1044 </div>
1045 </div>
1046 <div class="section" id="character-sets-and-unicode-byte-order-mark-bom">
1047 <h2><a class="toc-backref" href="#id35">Character sets and Unicode Byte-Order-Mark (BOM)</a></h2>
1048 <div class="section" id="using-character-sets">
1049 <h3><a class="toc-backref" href="#id36">Using character sets</a></h3>
1050 <p>Geany provides support for detecting and converting character sets. So
1051 you can open and save files in different character sets, and even
1052 convert a file from one character set to another. To do this,
1053 Geany uses the character conversion capabilities of the GLib library.</p>
1054 <p>Only text files are supported, i.e. opening files which contain
1055 NULL-bytes may fail. Geany will try to open the file anyway but it is
1056 likely that the file will be truncated because it can only be read up
1057 to the first occurrence of a NULL-byte. All characters after this
1058 position are lost and are not written when you save the file.</p>
1059 <p>Geany tries to detect the encoding of a file while opening it, but
1060 auto-detecting the encoding of a file is not easy and sometimes an
1061 encoding might not be detected correctly. In this case you have to
1062 set the encoding of the file manually in order to display it
1063 correctly. You can this in the file open dialog by selecting an
1064 encoding in the drop down box or by reloading the file with the
1065 file menu item &quot;Reload as&quot;. The auto-detection works well for most
1066 encodings but there are also some encodings where it is known that
1067 auto-detection has problems.</p>
1068 <p>There are different ways to set different encodings in Geany:</p>
1069 <ul>
1070 <li><p class="first">Using the file open dialog</p>
1071 <p>This opens the file with the encoding specified in the encoding drop
1072 down box. If the encoding is set to &quot;Detect from file&quot; auto-detection
1073 will be used. If the encoding is set to &quot;Without encoding (None)&quot; the
1074 file will be opened without any character conversion and Geany will
1075 not try to auto-detect the encoding (see below for more information).</p>
1076 </li>
1077 <li><p class="first">Using the &quot;Reload as&quot; menu item</p>
1078 <p>This item reloads the current file with the specified encoding. It can
1079 help if you opened a file and found out that the wrong encoding was used.</p>
1080 </li>
1081 <li><p class="first">Using the &quot;Set encoding&quot; menu item</p>
1082 <p>Contrary to the above two options, this will not change or reload
1083 the current file unless you save it. It is useful when you want to
1084 change the encoding of the file.</p>
1085 </li>
1086 <li><p class="first">Specifying the encoding in the file itself</p>
1087 <p>As mentioned above, auto-detecting the encoding of a file may fail on
1088 some encodings. If you know that Geany doesn't open a certain file,
1089 you can add the specification line, described in the next section,
1090 to the beginning of the file to force Geany to use a specific
1091 encoding when opening the file.</p>
1092 </li>
1093 </ul>
1094 </div>
1095 <div class="section" id="in-file-encoding-specification">
1096 <h3><a class="toc-backref" href="#id37">In-file encoding specification</a></h3>
1097 <p>Geany detects meta tags of HTML files which contain charset information
1098 like:</p>
1099 <pre class="literal-block">
1100 &lt;meta http-equiv=&quot;content-type&quot; content=&quot;text/html; charset=ISO-8859-15&quot; /&gt;
1101 </pre>
1102 <p>and the specified charset is used when opening the file. This is useful if the
1103 encoding of the file cannot be detected properly.
1104 For non-HTML files you can also define a line like:</p>
1105 <pre class="literal-block">
1106 /* geany_encoding=ISO-8859-15 */
1107 </pre>
1108 <p>or:</p>
1109 <pre class="literal-block">
1110 # geany_encoding=ISO-8859-15 #
1111 </pre>
1112 <p>to force an encoding to be used. The #, /* and */ are examples
1113 of filetype-specific comment characters. It doesn't matter which
1114 characters are around the string &quot; geany_encoding=ISO-8859-15 &quot; as long
1115 as there is at least one whitespace character before and after this
1116 string. Whitespace characters are in this case a space or tab character.
1117 An example to use this could be you have a file with ISO-8859-15
1118 encoding but Geany constantly detects the file encoding as ISO-8859-1.
1119 Then you simply add such a line to the file and Geany will open it
1120 correctly the next time.</p>
1121 <p>Since Geany 0.15 you can also use lines which match the
1122 regular expression used to find the encoding string:
1123 <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>
1124 <div class="note">
1125 <p class="first admonition-title">Note</p>
1126 <p class="last">These specifications must be in the first 512 bytes of the file.
1127 Anything after the first 512 bytes will not be recognized.</p>
1128 </div>
1129 <p>Some examples are:</p>
1130 <pre class="literal-block">
1131 # encoding = ISO-8859-15
1132 </pre>
1133 <p>or:</p>
1134 <pre class="literal-block">
1135 # coding: ISO-8859-15
1136 </pre>
1137 </div>
1138 <div class="section" id="special-encoding-none">
1139 <h3><a class="toc-backref" href="#id38">Special encoding &quot;None&quot;</a></h3>
1140 <p>There is a special encoding &quot;None&quot; which uses no
1141 encoding. It is useful when you know that Geany cannot auto-detect
1142 the encoding of a file and it is not displayed correctly. Especially
1143 when the file contains NULL-bytes this can be useful to skip auto
1144 detection and open the file properly at least until the occurrence
1145 of the first NULL-byte. Using this encoding opens the file as it is
1146 without any character conversion.</p>
1147 </div>
1148 <div class="section" id="unicode-byte-order-mark-bom">
1149 <h3><a class="toc-backref" href="#id39">Unicode Byte-Order-Mark (BOM)</a></h3>
1150 <p>Furthermore, Geany detects a Unicode Byte Order Mark (see
1151 <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,
1152 this feature is only available if the opened file is in a Unicode
1153 encoding. The Byte Order Mark helps to detect the encoding of a file,
1154 e.g. whether it is UTF-16LE or UTF-16BE and so on. On Unix-like systems
1155 using a Byte Order Mark could cause some problems for programs not
1156 expecting it, e.g. the compiler gcc stops
1157 with stray errors, PHP does not parse a script containing a BOM and
1158 script files starting with a she-bang maybe cannot be started. In the
1159 status bar you can easily see whether the file starts with a BOM or
1160 not.</p>
1161 <p>If you want to set a BOM for a file or if you want to remove it
1162 from a file, just use the document menu and toggle the checkbox.</p>
1163 <div class="note">
1164 <p class="first admonition-title">Note</p>
1165 <p class="last">If you are unsure what a BOM is or if you do not understand where
1166 to use it, then it is probably not important for you and you can
1167 safely ignore it.</p>
1168 </div>
1169 </div>
1170 </div>
1171 <div class="section" id="editing">
1172 <h2><a class="toc-backref" href="#id40">Editing</a></h2>
1173 <div class="section" id="folding">
1174 <h3><a class="toc-backref" href="#id41">Folding</a></h3>
1175 <p>Geany provides basic code folding support. Folding means the ability to
1176 show and hide parts of the text in the current file. You can hide
1177 unimportant code sections and concentrate on the parts you are working on
1178 and later you can show hidden sections again. In the editor window there is
1179 a small grey margin on the left side with [+] and [-] symbols which
1180 show hidden parts and hide parts of the file respectively. By
1181 clicking on these icons you can simply show and hide sections which are
1182 marked by vertical lines within this margin. For many filetypes nested
1183 folding is supported, so there may be several fold points within other
1184 fold points.</p>
1185 <div class="note">
1186 <p class="first admonition-title">Note</p>
1187 <p class="last">You can customize the folding icon and line styles - see the
1188 filetypes.common <a class="reference internal" href="#folding-settings">Folding Settings</a>.</p>
1189 </div>
1190 <p>If you don't like it or don't need it at all, you can simply disable
1191 folding support completely in the preferences dialog.</p>
1192 <p>The folding behaviour can be changed with the &quot;Fold/Unfold all children of
1193 a fold point&quot; option in the preference dialog. If activated, Geany will
1194 unfold all nested fold points below the current one if they are already
1195 folded (when clicking on a [+] symbol).
1196 When clicking on a [-] symbol, Geany will fold all nested fold points
1197 below the current one if they are unfolded.</p>
1198 <p>This option can be inverted by pressing the Shift
1199 key while clicking on a fold symbol. That means, if the &quot;Fold/Unfold all
1200 children of a fold point&quot; option is enabled, pressing Shift will disable
1201 it for this click and vice versa.</p>
1202 </div>
1203 <div class="section" id="column-mode-editing-rectangular-selections">
1204 <h3><a class="toc-backref" href="#id42">Column mode editing (rectangular selections)</a></h3>
1205 <p>There is basic support for column mode editing. To use it, create a
1206 rectangular selection by holding down the Control and Shift keys
1207 (or Control and Alt if it doesn't work) while
1208 selecting some text. It is also possible to create a zero-column selection.
1209 Once a rectangular selection exists you can start editing the text within
1210 this selection and the modifications will be done for every line in the
1211 selection.</p>
1212 </div>
1213 <div class="section" id="drag-and-drop-of-text">
1214 <h3><a class="toc-backref" href="#id43">Drag and drop of text</a></h3>
1215 <p>If you drag selected text in the editor widget of Geany the text is
1216 moved to the position where the mouse pointer is when releasing the
1217 mouse button. Holding Control when releasing the mouse button will
1218 copy the text instead. This behaviour was changed in Geany 0.11 -
1219 before the selected text was copied to the new position.</p>
1220 </div>
1221 <div class="section" id="indentation">
1222 <h3><a class="toc-backref" href="#id44">Indentation</a></h3>
1223 <p>Geany allows each document to indent either with a tab character,
1224 multiple spaces or a combination of both. The default indent
1225 settings are set in <a class="reference internal" href="#editor-indentation-preferences">Editor Indentation preferences</a> (see the link
1226 for more information).</p>
1227 <p>The default settings can be overridden per-document using the
1228 Document menu. They can also be overridden by projects - see
1229 <a class="reference internal" href="#project-management">Project management</a>.</p>
1230 <p>The indent mode for the current document is shown on the status bar
1231 as follows:</p>
1232 <dl class="docutils">
1233 <dt>TAB</dt>
1234 <dd>Indent with Tab characters.</dd>
1235 <dt>SP</dt>
1236 <dd>Indent with spaces.</dd>
1237 <dt>T/S</dt>
1238 <dd>Indent with tabs and spaces, depending on how much indentation is
1239 on a line.</dd>
1240 </dl>
1241 <div class="section" id="applying-new-indentation-settings">
1242 <h4><a class="toc-backref" href="#id45">Applying new indentation settings</a></h4>
1243 <p>After changing the default settings you may wish to apply the new
1244 settings to every document in the current session. To do this use the
1245 <em>Project-&gt;Apply Default Indentation</em> menu item.</p>
1246 </div>
1247 <div class="section" id="detecting-indent-type">
1248 <h4><a class="toc-backref" href="#id46">Detecting indent type</a></h4>
1249 <p>The <em>Detect from file</em> indentation preference can be used to
1250 scan each file as it's opened and set the indent type based on
1251 how many lines start with a tab vs. 2 or more spaces.</p>
1252 </div>
1253 </div>
1254 <div class="section" id="auto-indentation">
1255 <h3><a class="toc-backref" href="#id47">Auto-indentation</a></h3>
1256 <p>When enabled, auto-indentation happens when pressing <em>Enter</em> in the
1257 Editor. It adds a certain amount of indentation to the new line so the
1258 user doesn't always have to indent each line manually.</p>
1259 <p>Geany has four types of auto-indentation:</p>
1260 <dl class="docutils">
1261 <dt>None</dt>
1262 <dd>Disables auto-indentation completely.</dd>
1263 <dt>Basic</dt>
1264 <dd>Adds the same amount of whitespace on a new line as on the last line.</dd>
1265 <dt>Current chars</dt>
1266 <dd>Does the same as <em>Basic</em> but also indents a new line after an opening
1267 brace '{', and de-indents when typing a closing brace '}'. For Python,
1268 a new line will be indented after typing ':' at the end of the
1269 previous line.</dd>
1270 <dt>Match braces</dt>
1271 <dd>Similar to <em>Current chars</em> but the closing brace will be aligned to
1272 match the indentation of the line with the opening brace.</dd>
1273 </dl>
1274 <p>There is also XML-tag auto-indentation. This is enabled when the
1275 mode is more than just Basic, and is also controlled by a filetype
1276 setting - see <a class="reference internal" href="#xml-indent-tags">xml_indent_tags</a>.</p>
1277 </div>
1278 <div class="section" id="bookmarks">
1279 <h3><a class="toc-backref" href="#id48">Bookmarks</a></h3>
1280 <p>Geany provides a handy bookmarking feature that lets you mark one
1281 or more lines in a document, and return the cursor to them using a
1282 key combination.</p>
1283 <p>To place a mark on a line, either left-mouse-click in the left margin
1284 of the editor window, or else use Ctrl-m. This will
1285 produce a small green plus symbol in the margin. You can have as many
1286 marks in a document as you like. Click again (or use Ctrl-m again)
1287 to remove the bookmark. To remove all the marks in a given document,
1288 use &quot;Remove Markers&quot; in the Document menu.</p>
1289 <p>To navigate down your document, jumping from one mark to the next,
1290 use Ctrl-. (control period). To go in the opposite direction on
1291 the page, use Ctrl-, (control comma). Using the bookmarking feature
1292 together with the commands to switch from one editor tab to another
1293 (Ctrl-PgUp/PgDn and Ctrl-Tab) provides a particularly fast way to
1294 navigate around multiple files.</p>
1295 </div>
1296 <div class="section" id="code-navigation-history">
1297 <h3><a class="toc-backref" href="#id49">Code navigation history</a></h3>
1298 <p>To ease navigation in source files and especially between
1299 different files, Geany lets you jump between different navigation
1300 points. Currently, this works for the following:</p>
1301 <ul class="simple">
1302 <li><a class="reference internal" href="#go-to-tag-declaration">Go to tag declaration</a></li>
1303 <li><a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a></li>
1304 <li>Symbol list items</li>
1305 <li>Build errors</li>
1306 <li>Message items</li>
1307 </ul>
1308 <p>When using one of these actions, Geany remembers your current position
1309 and jumps to the new one. If you decide to go back to your previous
1310 position in the file, just use &quot;Navigate back a location&quot;. To
1311 get back to the new position again, just use &quot;Navigate forward a
1312 location&quot;. This makes it easier to navigate in e.g.  foreign code
1313 and between different files.</p>
1314 </div>
1315 <div class="section" id="sending-text-through-custom-commands">
1316 <h3><a class="toc-backref" href="#id50">Sending text through custom commands</a></h3>
1317 <p>You can define several custom commands in Geany and send the current
1318 selection to one of these commands using the <em>Edit-&gt;Format-&gt;Send
1319 Selection to</em> menu or keybindings. The output of the command will be
1320 used to replace the current selection. This makes it possible to use
1321 text formatting tools with Geany in a general way.</p>
1322 <p>The selected text will be sent to the standard input of the executed
1323 command, so the command should be able to read from it and it should
1324 print all results to its standard output which will be read by
1325 Geany. To help finding errors in executing the command, the output
1326 of the program's standard error will be printed on Geany's standard
1327 output.</p>
1328 <p>If there is no selection, the whole current line is used instead.</p>
1329 <p>To add a custom command, use the <em>Send Selection to-&gt;Set Custom
1330 Commands</em> menu item. Click on <em>Add</em> to get a new item and type the
1331 command. You can also specify some command line options. Empty
1332 commands are not saved.</p>
1333 <p>Normal shell quoting is supported, so you can do things like:</p>
1334 <ul class="simple">
1335 <li><tt class="docutils literal">sed <span class="pre">'s/\./(dot)/g'</span></tt></li>
1336 </ul>
1337 <p>The above example would normally be done with the <a class="reference internal" href="#replace-all">Replace all</a>
1338 function, but it can be handy to have common commands already set up.</p>
1339 </div>
1340 <div class="section" id="context-actions">
1341 <h3><a class="toc-backref" href="#id51">Context actions</a></h3>
1342 <p>You can execute the context action command on the current word at the
1343 cursor position or the available selection.  This word or selection
1344 can be used as an argument to the command.
1345 The context action is invoked by a menu entry in the popup menu of the
1346 editor and also a keyboard shortcut (see the section called
1347 <a class="reference internal" href="#keybindings">Keybindings</a>).</p>
1348 <p>The command can be specified in the preferences dialog and also for
1349 each filetype (see &quot;context_action_cmd&quot; in the section called
1350 <a class="reference internal" href="#filetype-configuration">Filetype configuration</a>). When the context action is invoked, the filetype
1351 specific command is used if available, otherwise the command
1352 specified in the preferences dialog is executed.</p>
1353 <p>The current word or selection can be referred with the wildcard &quot;%s&quot;
1354 in the command, it will be replaced by the current word or
1355 selection before the command is executed.</p>
1356 <p>For example a context action can be used to open API documentation
1357 in a browser window, the command to open the PHP API documentation
1358 would be:</p>
1359 <pre class="literal-block">
1360 firefox &quot;http://www.php.net/%s&quot;
1361 </pre>
1362 <p>when executing the command, the %s is substituted by the word near
1363 the cursor position or by the current selection. If the cursor is at
1364 the word &quot;echo&quot;, a browser window will open(assumed your browser is
1365 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>
1366 </div>
1367 <div class="section" id="autocompletion">
1368 <h3><a class="toc-backref" href="#id52">Autocompletion</a></h3>
1369 <p>Geany can offer a list of possible completions for symbols defined in the
1370 tags and for all words in a document.</p>
1371 <p>The autocompletion list for symbols is presented when the first few
1372 characters of the symbol are typed (configurable, see <a class="reference internal" href="#editor-completions-preferences">Editor Completions
1373 preferences</a>, default 4) or when the <em>Complete word</em>
1374 keybinding is pressed (configurable, see <a class="reference internal" href="#editor-keybindings">Editor keybindings</a>,
1375 default Ctrl-Space).</p>
1376 <p>When the defined keybinding is typed and the <em>Autocomplete all words in
1377 document</em> preference (in <a class="reference internal" href="#editor-completions-preferences">Editor Completions preferences</a>)
1378 is selected then the autocompletion list will show all matching words
1379 in the document, if there are no matching symbols.</p>
1380 <p>If you don't want to use autocompletion it can be dismissed until
1381 the next symbol by pressing Escape. The autocompletion list is updated
1382 as more characters are typed so that it only shows completions that start
1383 with the characters typed so far. If no symbols begin with the sequence,
1384 the autocompletion window is closed.</p>
1385 <p>The up and down arrows will move the selected item. The highlighted
1386 item on the autocompletion list can be chosen from the list by pressing
1387 Enter/Return. You can also double-click to select an item. The sequence
1388 will be completed to match the chosen item, and if the <em>Drop rest of
1389 word on completion</em> preference is set (in <a class="reference internal" href="#editor-completions-preferences">Editor Completions
1390 preferences</a>) then any characters after the cursor that match
1391 a symbol or word are deleted.</p>
1392 <div class="section" id="word-part-completion">
1393 <h4><a class="toc-backref" href="#id53">Word part completion</a></h4>
1394 <p>By default, pressing Tab will complete the selected item by word part;
1395 useful e.g. for adding the prefix <tt class="docutils literal">gtk_combo_box_entry_</tt> without typing it
1396 manually:</p>
1397 <ul class="simple">
1398 <li>gtk_com&lt;TAB&gt;</li>
1399 <li>gtk_combo_&lt;TAB&gt;</li>
1400 <li>gtk_combo_box_&lt;e&gt;&lt;TAB&gt;</li>
1401 <li>gtk_combo_box_entry_&lt;s&gt;&lt;ENTER&gt;</li>
1402 <li>gtk_combo_box_entry_set_text_column</li>
1403 </ul>
1404 <p>The key combination can be changed from Tab - See <a class="reference internal" href="#editor-keybindings">Editor keybindings</a>.
1405 If you clear/change the key combination for word part completion, Tab
1406 will complete the whole word instead, like Enter.</p>
1407 </div>
1408 <div class="section" id="scope-autocompletion">
1409 <h4><a class="toc-backref" href="#id54">Scope autocompletion</a></h4>
1410 <p>E.g.:</p>
1411 <pre class="literal-block">
1412 struct
1413 {
1414     int i;
1415     char c;
1416 } foo;
1417 </pre>
1418 <p>When you type <tt class="docutils literal">foo.</tt> it will show an autocompletion list with 'i' and
1419 'c' symbols.</p>
1420 <p>It only works for languages that set parent scope names for e.g. struct
1421 members. Currently this means C-like languages. The C tag parser only
1422 parses global scopes, so this won't work for structs or objects declared
1423 in local scope.</p>
1424 </div>
1425 </div>
1426 <div class="section" id="user-definable-snippets">
1427 <h3><a class="toc-backref" href="#id55">User-definable snippets</a></h3>
1428 <p>Snippets are small strings or code constructs which can be replaced or
1429 completed to a more complex string. So you can save a lot of time when
1430 typing common strings and letting Geany do the work for you.
1431 To know what to complete or replace Geany reads a configuration file
1432 called <tt class="docutils literal">snippets.conf</tt> at startup.</p>
1433 <p>Maybe you need to often type your name, so define a snippet like this:</p>
1434 <pre class="literal-block">
1435 [Default]
1436 myname=Enrico Tröger
1437 </pre>
1438 <p>Every time you write <tt class="docutils literal">myname</tt> &lt;TAB&gt; in Geany, it will replace &quot;myname&quot;
1439 with &quot;Enrico Tröger&quot;. The key to start autocompletion can be changed
1440 in the preferences dialog, by default it is TAB. The corresponding keybinding
1441 is called <cite>Complete snippet</cite>.</p>
1442 <p><strong>Paths</strong></p>
1443 <p>You can override the default snippets using the user
1444 <tt class="docutils literal">snippets.conf</tt> file. Use the <em>Tools-&gt;Configuration
1445 Files-&gt;snippets.conf</em> menu item. See also <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>.</p>
1446 <p>This adds the default settings to the user file if the file doesn't
1447 exist. Alternatively the file can be created manually, adding only
1448 the settings you want to change. All missing settings will be read
1449 from the system snippets file.</p>
1450 <p><strong>Snippet groups</strong></p>
1451 <p>The file <tt class="docutils literal">snippets.conf</tt> contains sections defining snippets that
1452 are available for particular filetypes and in general.</p>
1453 <p>The two sections &quot;Default&quot; and &quot;Special&quot; apply to all filetypes.
1454 &quot;Default&quot; contains all snippets which are available for every
1455 filetype and &quot;Special&quot; contains snippets which can only be used in
1456 other snippets. So you can define often used parts of snippets and
1457 just use the special snippet as a placeholder (see the
1458 <tt class="docutils literal">snippets.conf</tt> for details).</p>
1459 <p>You can define sections with the name of a filetype eg &quot;C++&quot;.  The
1460 snippets in that section are only available for use in files with that
1461 filetype.  Snippets in filetype sections will hide snippets with the
1462 same name in the &quot;Default&quot; section when used in a file of that
1463 filetype.</p>
1464 <p><strong>Substitution sequences for snippets</strong></p>
1465 <p>To define snippets you can use several special character sequences which
1466 will be replaced when using the snippet:</p>
1467 <table border="1" class="docutils">
1468 <colgroup>
1469 <col width="22%" />
1470 <col width="78%" />
1471 </colgroup>
1472 <tbody valign="top">
1473 <tr><td>\n or %newline%</td>
1474 <td>Insert a new line (it will be replaced by the used EOL
1475 char(s): LF, CR/LF, or CR).</td>
1476 </tr>
1477 <tr><td>\t or %ws%</td>
1478 <td>Insert an indentation step, it will be replaced according
1479 to the current document's indent mode.</td>
1480 </tr>
1481 <tr><td>\s</td>
1482 <td>\s to force whitespace at beginning or end of a value
1483 ('key= value' won't work, use 'key=\svalue')</td>
1484 </tr>
1485 <tr><td>%cursor%</td>
1486 <td>Place the cursor at this position after completion has
1487 been done. You can define multiple %cursor% wildcards
1488 and use the keybinding <cite>Move cursor in snippet</cite> to jump
1489 to the next defined cursor position in the completed
1490 snippet.</td>
1491 </tr>
1492 <tr><td>%...%</td>
1493 <td>&quot;...&quot; means the name of a key in the &quot;Special&quot; section.
1494 If you have defined a key &quot;brace_open&quot; in the &quot;Special&quot;
1495 section you can use %brace_open% in any other snippet.</td>
1496 </tr>
1497 </tbody>
1498 </table>
1499 <p>Snippet names must not contain spaces otherwise they won't
1500 work correctly. But beside that you can define almost any
1501 string as a snippet and use it later in Geany. It is not limited
1502 to existing contructs of certain programming languages(like <tt class="docutils literal">if</tt>,
1503 <tt class="docutils literal">for</tt>, <tt class="docutils literal">switch</tt>). Define whatever you need.</p>
1504 <p><strong>Template wildcards</strong></p>
1505 <p>Since Geany 0.15 you can also use most of the available templates wildcards
1506 listed in <a class="reference internal" href="#template-wildcards">Template wildcards</a>. All wildcards which are listed as
1507 <cite>available in snippets</cite> can be used. For instance to improve the above example:</p>
1508 <pre class="literal-block">
1509 [Default]
1510 myname=My name is {developer}
1511 mysystem=My system: {command:uname -a}
1512 </pre>
1513 <p>this will replace <tt class="docutils literal">myname</tt> with &quot;My name is &quot; and the value of the template
1514 preference <tt class="docutils literal">developer</tt>.</p>
1515 <p><strong>Word characters</strong></p>
1516 <p>You can change the way Geany recognizes the word to complete,
1517 that is how the start and end of a word is recognised when the
1518 snippet completion is requested. The section &quot;Special&quot; may
1519 contain a key &quot;wordchars&quot; which lists all characters a string may contain
1520 to be recognized as a word for completion. Leave it commented to use
1521 default characters or define it to add or remove characters to fit your
1522 needs.</p>
1523 <div class="section" id="snippet-keybindings">
1524 <h4><a class="toc-backref" href="#id56">Snippet keybindings</a></h4>
1525 <p>Normally you would type the snippet name and press Tab. However, you
1526 can define keybindings for snippets under the <em>Keybindings</em> group in
1527 <tt class="docutils literal">snippets.conf</tt>:</p>
1528 <pre class="literal-block">
1529 [Keybindings]
1530 for=&lt;Ctrl&gt;7
1531 block_cursor=&lt;Ctrl&gt;8
1532 </pre>
1533 <div class="note">
1534 <p class="first admonition-title">Note</p>
1535 <p class="last">Snippet keybindings may be overridden by Geany's configurable
1536 keybindings.</p>
1537 </div>
1538 </div>
1539 </div>
1540 <div class="section" id="inserting-unicode-characters">
1541 <h3><a class="toc-backref" href="#id57">Inserting Unicode characters</a></h3>
1542 <p>You can insert Unicode code points by hitting Ctrl-Shift-u, then still holding
1543 Ctrl-Shift, type some hex digits representing the code point for the character
1544 you want and hit Enter or Return (still holding Ctrl-Shift). If you release
1545 Ctrl-Shift before hitting Enter or Return (or any other character), the code
1546 insertion is completed, but the typed character is also entered.  In the case
1547 of Enter/Return, it is a newline, as you might expect.</p>
1548 <p>In some earlier versions of Geany, you might need to first unbind Ctrl-Shift-u
1549 in the <a class="reference internal" href="#keybinding-preferences">keybinding preferences</a>, then select <em>Tools-&gt;Reload Configuration</em>
1550 or restart Geany. Note that it works slightly differently from other GTK
1551 applications, in that you'll need to continue to hold down the Ctrl and Shift
1552 keys while typing the code point hex digits (and the Enter or Return to finish the code point).</p>
1553 </div>
1554 </div>
1555 <div class="section" id="search-replace-and-go-to">
1556 <h2><a class="toc-backref" href="#id58">Search, replace and go to</a></h2>
1557 <p>This section describes search-related commands from the Search menu
1558 and the editor window's popup menu:</p>
1559 <ul class="simple">
1560 <li>Find</li>
1561 <li>Find selection</li>
1562 <li>Find usage</li>
1563 <li>Find in files</li>
1564 <li>Replace</li>
1565 <li>Go to tag definition</li>
1566 <li>Go to tag declaration</li>
1567 <li>Go to line</li>
1568 </ul>
1569 <div class="section" id="toolbar-entries">
1570 <h3><a class="toc-backref" href="#id59">Toolbar entries</a></h3>
1571 <p>There are also two toolbar entries:</p>
1572 <ul class="simple">
1573 <li>Search bar</li>
1574 <li>Go to line entry</li>
1575 </ul>
1576 <p>There are keybindings to focus each of these - see <a class="reference internal" href="#focus-keybindings">Focus
1577 keybindings</a>. Pressing Escape will then focus the editor.</p>
1578 <div class="section" id="search-bar">
1579 <h4><a class="toc-backref" href="#id60">Search bar</a></h4>
1580 <p>The quickest way to find some text is to use the search bar entry in
1581 the toolbar. This performs a case-insensitive search in the current
1582 document whilst you type. Pressing Enter will search again, and pressing
1583 Shift-Enter will search backwards.</p>
1584 </div>
1585 </div>
1586 <div class="section" id="find">
1587 <h3><a class="toc-backref" href="#id61">Find</a></h3>
1588 <p>The Find dialog is used for finding text in one or more open documents.</p>
1589 <img alt="./images/find_dialog.png" src="./images/find_dialog.png" />
1590 <div class="section" id="matching-options">
1591 <h4><a class="toc-backref" href="#id62">Matching options</a></h4>
1592 <p>The syntax for the <em>Use regular expressions</em> option is shown in
1593 <a class="reference internal" href="#regular-expressions">Regular expressions</a>.</p>
1594 <div class="note">
1595 <p class="first admonition-title">Note</p>
1596 <p class="last"><em>Use escape sequences</em> is implied for regular expressions.</p>
1597 </div>
1598 <p>The <em>Use escape sequences</em> option will transform any escaped characters
1599 into their UTF-8 equivalent. For example, \t will be transformed into
1600 a tab character. Other recognized symbols are: \\, \n, \r, \uXXXX
1601 (Unicode characters).</p>
1602 </div>
1603 <div class="section" id="find-all">
1604 <h4><a class="toc-backref" href="#id63">Find all</a></h4>
1605 <p>To find all matches, click on the Find All expander. This will reveal
1606 several options:</p>
1607 <ul class="simple">
1608 <li>In Document</li>
1609 <li>In Session</li>
1610 <li>Mark</li>
1611 </ul>
1612 <p>Find All In Document will show a list of matching lines in the
1613 current document in the Messages tab of the Message Window. <em>Find All
1614 In Session</em> does the same for all open documents.</p>
1615 <p>Mark will highlight all matches in the current document with a
1616 colored box. These markers can be removed by selecting the
1617 Remove Markers command from the Document menu.</p>
1618 </div>
1619 <div class="section" id="change-font-in-search-dialog-text-fields">
1620 <h4><a class="toc-backref" href="#id64">Change font in search dialog text fields</a></h4>
1621 <p>All search related dialogs use a Monospace for the text input fields to
1622 increase the readability of input text. This is useful when you are
1623 typing input such as regular expressions with spaces, periods and commas which
1624 might it hard to read with a proportional font.</p>
1625 <p>If you want to change the font, you can do this easily
1626 by inserting the following style into your <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt>
1627 (usually found in your home directory on UNIX-like systems and in the
1628 etc subdirectory of your Geany installation on Windows):</p>
1629 <pre class="literal-block">
1630 style &quot;search_style&quot;
1631 {
1632     font_name=&quot;Monospace 8&quot;
1633 }
1634 widget &quot;GeanyDialogSearch.*.GtkEntry&quot; style:highest &quot;search_style&quot;
1635 </pre>
1636 <p>Please note the addition of &quot;:highest&quot; in the last line which sets the priority
1637 of this style to the highest available. Otherwise, the style is ignored
1638 for the search dialogs.</p>
1639 </div>
1640 </div>
1641 <div class="section" id="find-selection">
1642 <h3><a class="toc-backref" href="#id65">Find selection</a></h3>
1643 <p>The <em>Find Next/Previous Selection</em> commands perform a search for the
1644 current selected text. If nothing is selected, by default the current
1645 word is used instead. This can be customized by the
1646 <em>find_selection_type</em> preference - see <a class="reference internal" href="#various-preferences">Various preferences</a>.</p>
1647 <table border="1" class="docutils">
1648 <colgroup>
1649 <col width="10%" />
1650 <col width="90%" />
1651 </colgroup>
1652 <thead valign="bottom">
1653 <tr><th class="head">Value</th>
1654 <th class="head"><em>find_selection_type</em> behaviour</th>
1655 </tr>
1656 </thead>
1657 <tbody valign="top">
1658 <tr><td>0</td>
1659 <td>Use the current word (default).</td>
1660 </tr>
1661 <tr><td>1</td>
1662 <td>Try the X selection first, then current word.</td>
1663 </tr>
1664 <tr><td>2</td>
1665 <td>Repeat last search.</td>
1666 </tr>
1667 </tbody>
1668 </table>
1669 </div>
1670 <div class="section" id="find-usage">
1671 <h3><a class="toc-backref" href="#id66">Find usage</a></h3>
1672 <p>Find usage searches all open files. It is similar to the Find All In
1673 Session option in the Find dialog.</p>
1674 <p>If there is a selection, then it is used as the search text; otherwise
1675 the current word is used. The current word is either taken from the
1676 word nearest the edit cursor, or the word underneath the popup menu
1677 click position when the popup menu is used. The search results are
1678 shown in the Messages tab of the Message Window.</p>
1679 </div>
1680 <div class="section" id="find-in-files">
1681 <h3><a class="toc-backref" href="#id67">Find in files</a></h3>
1682 <p>Find in files is a more powerful version of Find usage that searches
1683 all files in a certain directory using the Grep tool. The Grep tool
1684 must be correctly set in Preferences to the path of the system's Grep
1685 utility. GNU Grep is recommended (see note below).</p>
1686 <img alt="./images/find_in_files_dialog.png" src="./images/find_in_files_dialog.png" />
1687 <p>The <em>Files</em> setting allows to choose which files are included in the
1688 search, depending on the mode:</p>
1689 <dl class="docutils">
1690 <dt>All</dt>
1691 <dd>Search in all files;</dd>
1692 <dt>Project</dt>
1693 <dd>Use the current project's patterns, see <a class="reference internal" href="#project-properties">Project properties</a>;</dd>
1694 <dt>Custom</dt>
1695 <dd>Use custom patterns.</dd>
1696 </dl>
1697 <p>Both project and custom patterns use a glob-style syntax, each
1698 pattern separated by a space. To search all <tt class="docutils literal">.c</tt> and <tt class="docutils literal">.h</tt> files,
1699 use: <tt class="docutils literal">*.c *.h</tt>.
1700 Note that an empty pattern list searches in all files rather
1701 than none.</p>
1702 <p>The <em>Encoding</em> field can be used to define the encoding of the files
1703 to be searched. The entered search text is converted to the chosen encoding
1704 and the search results are converted back to UTF-8.</p>
1705 <p>The <em>Extra options</em> field is used to pass any additional arguments to
1706 the grep tool.</p>
1707 <div class="note">
1708 <p class="first admonition-title">Note</p>
1709 <p class="last">The <em>Files</em> setting uses <tt class="docutils literal"><span class="pre">--include=</span></tt> when searching recursively,
1710 <em>Recurse in subfolders</em> uses <tt class="docutils literal"><span class="pre">-r</span></tt>; both are GNU Grep options and may
1711 not work with other Grep implementations.</p>
1712 </div>
1713 <div class="section" id="filtering-out-version-control-files">
1714 <h4><a class="toc-backref" href="#id68">Filtering out version control files</a></h4>
1715 <p>When using the <em>Recurse in subfolders</em> option with a directory that's
1716 under version control, you can set the <em>Extra options</em> field to filter
1717 out version control files.</p>
1718 <p>If you have GNU Grep &gt;= 2.5.2 you can use the <tt class="docutils literal"><span class="pre">--exclude-dir</span></tt>
1719 argument to filter out CVS and hidden directories like <tt class="docutils literal">.svn</tt>.</p>
1720 <p>Example: <tt class="docutils literal"><span class="pre">--exclude-dir=.svn</span> <span class="pre">--exclude-dir=CVS</span></tt></p>
1721 <p>If you have an older Grep, you can try using the <tt class="docutils literal"><span class="pre">--exclude</span></tt> flag
1722 to filter out filenames.</p>
1723 <p>SVN Example: <tt class="docutils literal"><span class="pre">--exclude=*.svn-base</span></tt></p>
1724 <p>The --exclude argument only matches the file name part, not the path.</p>
1725 </div>
1726 </div>
1727 <div class="section" id="replace">
1728 <h3><a class="toc-backref" href="#id69">Replace</a></h3>
1729 <p>The Replace dialog is used for replacing text in one or more open
1730 documents.</p>
1731 <img alt="./images/replace_dialog.png" src="./images/replace_dialog.png" />
1732 <p>The Replace dialog has the same options for matching text as the Find
1733 dialog. See the section <a class="reference internal" href="#matching-options">Matching options</a>.</p>
1734 <p>The <em>Use regular expressions</em> option allows regular expressions to
1735 be used in the search string and back references in the replacement
1736 text -- see the entry for '\n' in <a class="reference internal" href="#regular-expressions">Regular expressions</a>.</p>
1737 <div class="section" id="replace-all">
1738 <h4><a class="toc-backref" href="#id70">Replace all</a></h4>
1739 <p>To replace several matches, click on the <em>Replace All</em> expander. This
1740 will reveal several options:</p>
1741 <ul class="simple">
1742 <li>In Document</li>
1743 <li>In Session</li>
1744 <li>In Selection</li>
1745 </ul>
1746 <p><em>Replace All In Document</em> will replace all matching text in the
1747 current document. <em>Replace All In Session</em> does the same for all open
1748 documents. <em>Replace All In Selection</em> will replace all matching text
1749 in the current selection of the current document.</p>
1750 </div>
1751 </div>
1752 <div class="section" id="go-to-tag-definition">
1753 <h3><a class="toc-backref" href="#id71">Go to tag definition</a></h3>
1754 <p>If the current word is the name of a tag definition (like a function
1755 body) and the file containing the tag definition is open, this command
1756 will switch to that file and go to the corresponding line number. The
1757 current word is either the word nearest the edit cursor,
1758 or the word underneath the popup menu click position when the popup
1759 menu is used.</p>
1760 <div class="note">
1761 <p class="first admonition-title">Note</p>
1762 <p class="last">If the current word's tag is on the current line, Geany will try
1763 to look for a tag declaration instead, as this is more useful.
1764 Likewise 'Go to tag declaration' will search for a tag definition
1765 in this case also.</p>
1766 </div>
1767 </div>
1768 <div class="section" id="go-to-tag-declaration">
1769 <h3><a class="toc-backref" href="#id72">Go to tag declaration</a></h3>
1770 <p>Like Go to tag definition, but for a forward declaration such as a
1771 C function prototype or <tt class="docutils literal">extern</tt> declaration instead of a function
1772 body.</p>
1773 </div>
1774 <div class="section" id="go-to-line">
1775 <h3><a class="toc-backref" href="#id73">Go to line</a></h3>
1776 <p>Go to a particular line number in the current file.</p>
1777 </div>
1778 <div class="section" id="regular-expressions">
1779 <h3><a class="toc-backref" href="#id74">Regular expressions</a></h3>
1780 <p>You can use regular expressions in the Find and Replace dialogs
1781 by selecting the <em>Use regular expressions</em> check box (see <a class="reference internal" href="#matching-options">Matching
1782 options</a>). The syntax is POSIX compatible, as described in the table
1783 below.</p>
1784 <div class="note">
1785 <p class="first admonition-title">Note</p>
1786 <ol class="last arabic simple">
1787 <li>The <em>Use escape sequences</em> dialog option always applies for regular
1788 expressions.</li>
1789 <li>Searching backwards with regular expressions is not supported.</li>
1790 <li>\b, \d, \s, \w are GNU extensions and may not be available
1791 on non-GNU POSIX systems unless you built Geany with the
1792 <tt class="docutils literal"><span class="pre">--enable-gnu-regex</span></tt> option (this is always used on Windows).</li>
1793 </ol>
1794 </div>
1795 <p><strong>In a regular expression, the following characters are interpreted:</strong></p>
1796 <table border="1" class="docutils">
1797 <colgroup>
1798 <col width="10%" />
1799 <col width="90%" />
1800 </colgroup>
1801 <tbody valign="top">
1802 <tr><td>.</td>
1803 <td>Matches any character.</td>
1804 </tr>
1805 <tr><td>(</td>
1806 <td>This marks the start of a region for tagging a match.</td>
1807 </tr>
1808 <tr><td>)</td>
1809 <td>This marks the end of a tagged region.</td>
1810 </tr>
1811 <tr><td>\n</td>
1812 <td><p class="first">Where n is 1 through 9 refers to the first through ninth tagged
1813 region when searching or replacing.</p>
1814 <p>Searching for (Wiki)\1 matches WikiWiki.</p>
1815 <p class="last">If the search string was Fred([1-9])XXX and the
1816 replace string was Sam\1YYY, when applied to Fred2XXX this
1817 would generate Sam2YYY.</p>
1818 </td>
1819 </tr>
1820 <tr><td>\0</td>
1821 <td>When replacing, the whole matching text.</td>
1822 </tr>
1823 <tr><td>\b</td>
1824 <td>This matches a word boundary.</td>
1825 </tr>
1826 <tr><td>\c</td>
1827 <td><p class="first">A backslash followed by d, D, s, S, w or W, becomes a
1828 character class (both inside and outside sets []).</p>
1829 <ul class="last simple">
1830 <li>d: decimal digits</li>
1831 <li>D: any char except decimal digits</li>
1832 <li>s: whitespace (space, \t \n \r \f \v)</li>
1833 <li>S: any char except whitespace (see above)</li>
1834 <li>w: alphanumeric &amp; underscore</li>
1835 <li>W: any char except alphanumeric &amp; underscore</li>
1836 </ul>
1837 </td>
1838 </tr>
1839 <tr><td>\x</td>
1840 <td>This allows you to use a character x that would otherwise have
1841 a special meaning. For example, \[ would be interpreted as [
1842 and not as the start of a character set. Use \\ for a literal
1843 backslash.</td>
1844 </tr>
1845 <tr><td>[...]</td>
1846 <td><p class="first">Matches one of the characters in the set. If the first
1847 character in the set is ^, it matches the characters NOT in
1848 the set, i.e. complements the set. A shorthand S-E (start
1849 dash end) is used to specify a set of characters S up to E,
1850 inclusive.</p>
1851 <p>The special characters ] and - have no special
1852 meaning if they appear first in the set. - can also be last
1853 in the set. To include both, put ] first: []A-Z-].</p>
1854 <p>Examples:</p>
1855 <pre class="last literal-block">
1856 []|-]    matches these 3 chars
1857 []-|]    matches from ] to | chars
1858 [a-z]    any lowercase alpha
1859 [^]-]    any char except - and ]
1860 [^A-Z]   any char except uppercase alpha
1861 [a-zA-Z] any alpha
1862 </pre>
1863 </td>
1864 </tr>
1865 <tr><td>^</td>
1866 <td>This matches the start of a line (unless used inside a set, see
1867 above).</td>
1868 </tr>
1869 <tr><td>$</td>
1870 <td>This matches the end of a line.</td>
1871 </tr>
1872 <tr><td>*</td>
1873 <td>This matches 0 or more times. For example, Sa*m matches Sm, Sam,
1874 Saam, Saaam and so on.</td>
1875 </tr>
1876 <tr><td>+</td>
1877 <td>This matches 1 or more times. For example, Sa+m matches Sam,
1878 Saam, Saaam and so on.</td>
1879 </tr>
1880 <tr><td>?</td>
1881 <td>This matches 0 or 1 time(s). For example, Joh?n matches John, Jon.</td>
1882 </tr>
1883 </tbody>
1884 </table>
1885 <div class="note">
1886 <p class="first admonition-title">Note</p>
1887 <p class="last">This table is adapted from Scintilla and SciTE documentation,
1888 distributed under the <a class="reference internal" href="#license-for-scintilla-and-scite">License for Scintilla and SciTE</a>.</p>
1889 </div>
1890 </div>
1891 </div>
1892 <div class="section" id="view-menu">
1893 <h2><a class="toc-backref" href="#id75">View menu</a></h2>
1894 <p>The View menu allows various elements of the main window to be shown
1895 or hidden, and also provides various display-related editor options.</p>
1896 <div class="section" id="color-schemes-menu">
1897 <h3><a class="toc-backref" href="#id76">Color schemes menu</a></h3>
1898 <p>The Color schemes menu is available under the <em>View-&gt;Editor</em> submenu.
1899 It lists various color schemes for editor highlighting styles,
1900 including the default scheme first. Other items are available based
1901 on what color scheme files Geany found at startup.</p>
1902 <p>Color scheme files are read from the <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a> under
1903 the <tt class="docutils literal">colorschemes</tt> subdirectory. They should have the extension
1904 <tt class="docutils literal">.conf</tt>. The default color scheme
1905 is read from <tt class="docutils literal">filetypes.common</tt>.</p>
1906 <p>The <a class="reference internal" href="#named-styles-section">[named_styles] section</a> is the same as for <tt class="docutils literal">filetypes.common</tt>.</p>
1907 <div class="note">
1908 <p class="first admonition-title">Note</p>
1909 <p class="last">Some filetypes do not yet support named styles so will ignore
1910 any chosen color scheme.</p>
1911 </div>
1912 <p>The <tt class="docutils literal">[theme_info]</tt> section can contain information about the
1913 theme. The <tt class="docutils literal">name</tt> and <tt class="docutils literal">description</tt> keys are read to set the
1914 menu item text and tooltip, respectively. These keys can have
1915 translations, e.g.:</p>
1916 <pre class="literal-block">
1917 key=Hello
1918 key[de]=Hallo
1919 key[fr_FR]=Bonjour
1920 </pre>
1921 </div>
1922 </div>
1923 <div class="section" id="tags">
1924 <h2><a class="toc-backref" href="#id77">Tags</a></h2>
1925 <p>Tags are information that relates symbols in a program with the
1926 source file location of the declaration and definition.</p>
1927 <p>Geany has built-in functionality for generating tag information (aka
1928 &quot;workspace tags&quot;) for supported filetypes when you open a file.  You
1929 can also have Geany automatically load external tag files (aka &quot;global
1930 tags files&quot;) upon startup, or manually using <em>Tools --&gt; Load Tags</em>.</p>
1931 <p>Geany uses its own tag file format, similar to what <tt class="docutils literal">ctags</tt> uses
1932 (but is incompatible with ctags). You use Geany to generate global
1933 tags files, as described below.</p>
1934 <div class="section" id="workspace-tags">
1935 <h3><a class="toc-backref" href="#id78">Workspace tags</a></h3>
1936 <p>Tags for each document are parsed whenever a file is loaded, saved or
1937 modified (see <em>Symbol list update frequency</em> preference in the <a class="reference internal" href="#editor-completions-preferences">Editor
1938 Completions preferences</a>). These are shown in the Symbol list in the
1939 Sidebar. These tags are also used for autocompletion of symbols and calltips
1940 for all documents open in the current session that have the same filetype.</p>
1941 <p>The <em>Go to Tag</em> commands can be used with all workspace tags. See
1942 <a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a>.</p>
1943 </div>
1944 <div class="section" id="global-tags">
1945 <h3><a class="toc-backref" href="#id79">Global tags</a></h3>
1946 <p>Global tags are used to provide autocompletion of symbols and calltips
1947 without having to open the corresponding source files. This is intended
1948 for library APIs, as the tags file only has to be updated when you upgrade
1949 the library.</p>
1950 <p>You can load a custom global tags file in two ways:</p>
1951 <ul class="simple">
1952 <li>Using the <em>Load Tags</em> command in the Tools menu.</li>
1953 <li>By moving or symlinking tags files to the <tt class="docutils literal">tags</tt> subdirectory of
1954 one of the <a class="reference internal" href="#configuration-file-paths">configuration file paths</a> before starting Geany.</li>
1955 </ul>
1956 <p>You can either download these files or generate your own. They have
1957 the format:</p>
1958 <pre class="literal-block">
1959 name.lang_ext.tags
1960 </pre>
1961 <p><em>lang_ext</em> is one of the extensions set for the filetype associated
1962 with the tags. See the section called <a class="reference internal" href="#filetype-extensions">Filetype extensions</a> for
1963 more information.</p>
1964 <div class="section" id="default-global-tags-files">
1965 <h4><a class="toc-backref" href="#id80">Default global tags files</a></h4>
1966 <p>For some languages, a list of global tags is loaded when the
1967 corresponding filetype is first used. Currently these are for:</p>
1968 <ul class="simple">
1969 <li>C -- GTK+ and GLib</li>
1970 <li>Pascal</li>
1971 <li>PHP</li>
1972 <li>HTML -- &amp;symbol; completion, e.g. for ampersand, copyright, etc.</li>
1973 <li>LaTeX</li>
1974 <li>Python</li>
1975 </ul>
1976 </div>
1977 <div class="section" id="global-tags-file-format">
1978 <h4><a class="toc-backref" href="#id81">Global tags file format</a></h4>
1979 <p>Global tags files can have two different formats:</p>
1980 <ul class="simple">
1981 <li>Tagmanager format</li>
1982 <li>Pipe-separated format</li>
1983 </ul>
1984 <p>The first line of global tags files should be a comment, introduced
1985 by <tt class="docutils literal">#</tt> followed by a space and a string like <tt class="docutils literal">format=pipe</tt>
1986 or <tt class="docutils literal">format=tagmanager</tt> respectively, these are case-sensitive.
1987 This helps Geany to read the file properly. If this line
1988 is missing, Geany tries to auto-detect the used format but this
1989 might fail.</p>
1990 <p>The Tagmanager format is a bit more complex and is used for files
1991 created by the <tt class="docutils literal">geany <span class="pre">-g</span></tt> command. There is one tag per line.
1992 Different tag attributes like the return value or the argument list
1993 are separated with different characters indicating the type of the
1994 following argument.</p>
1995 <p>The Pipe-separated format is easier to read and write.
1996 There is one tag per line and different tag attributes are separated
1997 by the pipe character (<tt class="docutils literal">|</tt>). A line looks like:</p>
1998 <pre class="literal-block">
1999 basename|string|(string path [, string suffix])|
2000 </pre>
2001 <div class="line-block">
2002 <div class="line">The first field is the tag name (usually a function name).</div>
2003 <div class="line">The second field is the type of the return value.</div>
2004 <div class="line">The third field is the argument list for this tag.</div>
2005 <div class="line">The fourth field is the description for this tag but
2006 currently unused and should be left empty.</div>
2007 </div>
2008 <p>Except for the first field (tag name), all other field can be left
2009 empty but the pipe separator must appear for them.</p>
2010 <p>You can easily write your own global tag files using this format.
2011 Just save them in your tags directory, as described earlier in the
2012 section <a class="reference internal" href="#global-tags">Global tags</a>.</p>
2013 </div>
2014 <div class="section" id="generating-a-global-tags-file">
2015 <h4><a class="toc-backref" href="#id82">Generating a global tags file</a></h4>
2016 <p>You can generate your own global tags files by parsing a list of
2017 source files. The command is:</p>
2018 <pre class="literal-block">
2019 geany -g [-P] &lt;Tag File&gt; &lt;File list&gt;
2020 </pre>
2021 <ul class="simple">
2022 <li>Tag File filename should be in the format described earlier --
2023 see the section called <a class="reference internal" href="#global-tags">Global tags</a>.</li>
2024 <li>File list is a list of filenames, each with a full path (unless
2025 you are generating C/C++ tags and have set the CFLAGS environment
2026 variable appropriately).</li>
2027 <li><tt class="docutils literal"><span class="pre">-P</span></tt> or <tt class="docutils literal"><span class="pre">--no-preprocessing</span></tt> disables using the C pre-processor
2028 to process <tt class="docutils literal">#include</tt> directives for C/C++ source files. Use this
2029 option if you want to specify each source file on the command-line
2030 instead of using a 'master' header file. Also can be useful if you
2031 don't want to specify the CFLAGS environment variable.</li>
2032 </ul>
2033 <p>Example for the wxD library for the D programming language:</p>
2034 <pre class="literal-block">
2035 geany -g wxd.d.tags /home/username/wxd/wx/*.d
2036 </pre>
2037 <p><em>Generating C/C++ tag files:</em></p>
2038 <p>For C/C++ tag files, gcc and grep are required, so that header files
2039 can be preprocessed to include any other headers they depend upon.</p>
2040 <p>For C/C++ files, the environment variable CFLAGS should be set with
2041 appropriate <tt class="docutils literal"><span class="pre">-I/path</span></tt> include paths. The following example works with
2042 the bash shell, generating tags for the GnomeUI library:</p>
2043 <pre class="literal-block">
2044 CFLAGS=`pkg-config --cflags libgnomeui-2.0` geany -g gnomeui.c.tags \
2045 /usr/include/libgnomeui-2.0/gnome.h
2046 </pre>
2047 <p>You can adapt this command to use CFLAGS and header files appropriate
2048 for whichever libraries you want.</p>
2049 <p><em>Replacing the default C/C++ tags file:</em></p>
2050 <p>Geany currently uses a default global tags file c99.tags for
2051 C and C++, commonly installed in /usr/share/geany. This file can
2052 be replaced with one containing tags parsed from a different set
2053 of header files. When Geany is next started, your custom tags file
2054 will be loaded instead of the default c99.tags. You should keep a
2055 copy of the generated tags file because it will get overwritten when
2056 upgrading Geany.</p>
2057 </div>
2058 </div>
2059 <div class="section" id="c-ignore-tags">
2060 <h3><a class="toc-backref" href="#id83">C ignore.tags</a></h3>
2061 <p>You can ignore certain tags for C-based languages if they would lead
2062 to wrong parsing of the code. Use the <em>Tools-&gt;Configuration
2063 Files-&gt;ignore.tags</em> menu item to open the user <tt class="docutils literal">ignore.tags</tt> file.
2064 See also <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>.</p>
2065 <p>List all tag names you want to ignore in this file, separated by spaces
2066 and/or newlines.</p>
2067 <p>Example:</p>
2068 <pre class="literal-block">
2069 G_GNUC_NULL_TERMINATED
2070 G_GNUC_PRINTF
2071 G_GNUC_WARN_UNUSED_RESULT
2072 </pre>
2073 <p>This will parse code like:</p>
2074 <p><tt class="docutils literal">gchar **utils_strv_new(const gchar *first, <span class="pre">...)</span>
2075 G_GNUC_NULL_TERMINATED;</tt></p>
2076 <p>More detailed information about ignore tags usage from the Exuberant Ctags
2077 manual page:</p>
2078 <blockquote>
2079 Specifies a list of identifiers which are to be specially handled
2080 while  parsing C and C++ source files. This option is specifically
2081 provided to handle special cases arising through the use of
2082 pre-processor macros. When the identifiers listed are simple identifiers,
2083 these identifiers will be ignored during parsing of the source files.
2084 If an identifier is suffixed with a '+' character, ctags will also
2085 ignore any parenthesis-enclosed argument list which may immediately
2086 follow the identifier in the source files.
2087 If two identifiers are separated with the '=' character, the first
2088 identifiers is replaced by the second identifiers for parsing purposes.</blockquote>
2089 <p>For even more detailed information please read the manual page of
2090 Exuberant Ctags.</p>
2091 </div>
2092 </div>
2093 <div class="section" id="preferences">
2094 <h2><a class="toc-backref" href="#id84">Preferences</a></h2>
2095 <p>You may adjust Geany's settings using the Edit --&gt; Preferences
2096 dialog. Any changes you make there can be applied by hitting either
2097 the Apply or the OK button. These settings will persist between Geany
2098 sessions. Note that most settings here have descriptive popup bubble
2099 help -- just hover the mouse over the item in question to get help
2100 on it.</p>
2101 <p>You may also adjust some View settings (under the View menu) that
2102 persist between Geany sessions. The settings under the Document menu,
2103 however, are only for the current document and revert to defaults
2104 when restarting Geany.</p>
2105 <div class="note">
2106 <p class="first admonition-title">Note</p>
2107 <p class="last">In the paragraphs that follow, the text describing a dialog tab
2108 comes after the screenshot of that tab.</p>
2109 </div>
2110 <div class="section" id="general-startup-preferences">
2111 <h3><a class="toc-backref" href="#id85">General Startup preferences</a></h3>
2112 <img alt="./images/pref_dialog_gen_startup.png" src="./images/pref_dialog_gen_startup.png" />
2113 <div class="section" id="id1">
2114 <h4><a class="toc-backref" href="#id86">Startup</a></h4>
2115 <dl class="docutils">
2116 <dt>Load files from the last session</dt>
2117 <dd>On startup, load the same files you had open the last time you
2118 used Geany.</dd>
2119 <dt>Load virtual terminal support</dt>
2120 <dd>Load the library for running a terminal in the message window area.</dd>
2121 <dt>Enable plugin support</dt>
2122 <dd>Allow plugins to be used in Geany.</dd>
2123 </dl>
2124 </div>
2125 <div class="section" id="shutdown">
2126 <h4><a class="toc-backref" href="#id87">Shutdown</a></h4>
2127 <dl class="docutils">
2128 <dt>Save window position and geometry</dt>
2129 <dd>Save the current position and size of the main window so next time
2130 you open Geany it's in the same location.</dd>
2131 <dt>Confirm Exit</dt>
2132 <dd>Have a dialog pop up to confirm that you really want to quit Geany.</dd>
2133 </dl>
2134 </div>
2135 <div class="section" id="paths">
2136 <h4><a class="toc-backref" href="#id88">Paths</a></h4>
2137 <dl class="docutils">
2138 <dt>Startup path</dt>
2139 <dd>Path to start in when opening or saving files.
2140 It must be an absolute path.
2141 Leave it blank to use the current working directory.</dd>
2142 <dt>Project files</dt>
2143 <dd>Path to start in when opening project files.</dd>
2144 <dt>Extra plugin path</dt>
2145 <dd>By default Geany looks in the global installation path and in the
2146 configuration directory. In addition the path entered here will be searched
2147 for plugins. Usually you do not need to set an additional path to search for
2148 plugins. It might be useful when Geany is installed on a multi-user machine
2149 and additional plugins are available in a common location for all users.
2150 Leave blank to not set an additional lookup path.</dd>
2151 </dl>
2152 </div>
2153 </div>
2154 <div class="section" id="general-miscellaneous-preferences">
2155 <h3><a class="toc-backref" href="#id89">General Miscellaneous preferences</a></h3>
2156 <img alt="./images/pref_dialog_gen_misc.png" src="./images/pref_dialog_gen_misc.png" />
2157 <div class="section" id="miscellaneous">
2158 <h4><a class="toc-backref" href="#id90">Miscellaneous</a></h4>
2159 <dl class="docutils">
2160 <dt>Beep on errors when compilation has finished</dt>
2161 <dd>Have the computer make a beeping sound when compilation of your program
2162 has completed or any errors occurred.</dd>
2163 <dt>Switch status message list at new message</dt>
2164 <dd>Switch to the status message tab (in the notebook window at the bottom)
2165 once a new status message arrives.</dd>
2166 <dt>Suppress status messages in the status bar</dt>
2167 <dd><p class="first">Remove all messages from the status bar. The messages are still displayed
2168 in the status messages window.</p>
2169 <div class="tip last">
2170 <p class="first admonition-title">Tip</p>
2171 <p class="last">Another option is to use the <em>Switch to Editor</em> keybinding - it
2172 reshows the document statistics on the status bar. See <a class="reference internal" href="#focus-keybindings">Focus
2173 keybindings</a>.</p>
2174 </div>
2175 </dd>
2176 <dt>Use Windows File Open/Save dialogs</dt>
2177 <dd>Defines whether to use the native Windows File Open/Save dialogs or
2178 whether to use the GTK default dialogs.</dd>
2179 <dt>Auto-focus widgets (focus follows mouse)</dt>
2180 <dd>Give the focus automatically to widgets below the mouse cursor.
2181 This works for the main editor widget, the scribble, the toolbar search field
2182 goto line fields and the VTE.</dd>
2183 </dl>
2184 </div>
2185 <div class="section" id="search">
2186 <h4><a class="toc-backref" href="#id91">Search</a></h4>
2187 <dl class="docutils">
2188 <dt>Always wrap search and hide the Find dialog</dt>
2189 <dd>Always wrap search around the document and hide the Find dialog after clicking
2190 Find Next/Previous.</dd>
2191 <dt>Use the current word under the cursor for Find dialogs</dt>
2192 <dd>Use current word under the cursor when opening the Find, Find in Files or Replace dialog and
2193 there is no selection. When this option is disabled, the search term last used in the
2194 appropriate Find dialog is used.</dd>
2195 <dt>Use the current file's directory for Find in Files</dt>
2196 <dd>When opening the Find in Files dialog, set the directory to search to the directory of the current
2197 active file. When this option is disabled, the directory of the last use of the Find in Files
2198 dialog is used.</dd>
2199 </dl>
2200 </div>
2201 <div class="section" id="projects">
2202 <h4><a class="toc-backref" href="#id92">Projects</a></h4>
2203 <dl class="docutils">
2204 <dt>Use project-based session files</dt>
2205 <dd>Save your current session when closing projects. You will be able to
2206 resume different project sessions, automatically opening the files
2207 you had open previously.</dd>
2208 <dt>Store project file inside the project base directory</dt>
2209 <dd>When creating new projects, the default path for the project file contains
2210 the project base path. Without this option enabled, the default project file
2211 path is one level above the project base path.
2212 In either case, you can easily set the final project file path in the
2213 <em>New Project</em> dialog. This option provides the more common
2214 defaults automatically for convenience.</dd>
2215 </dl>
2216 </div>
2217 </div>
2218 <div class="section" id="interface-preferences">
2219 <h3><a class="toc-backref" href="#id93">Interface preferences</a></h3>
2220 <img alt="./images/pref_dialog_interface_interface.png" src="./images/pref_dialog_interface_interface.png" />
2221 <div class="section" id="sidebar">
2222 <h4><a class="toc-backref" href="#id94">Sidebar</a></h4>
2223 <dl class="docutils">
2224 <dt>Show sidebar</dt>
2225 <dd>Whether to show the sidebar at all.</dd>
2226 <dt>Show symbol list</dt>
2227 <dd>Show the list of functions, variables, and other information in the
2228 current document you are editing.</dd>
2229 <dt>Show documents list</dt>
2230 <dd>Show all the documents you have open currently. This can be used to
2231 change between documents (see <a class="reference internal" href="#switching-between-documents">Switching between documents</a>) and
2232 to perform some common operations such as saving, closing and reloading.</dd>
2233 <dt>Position</dt>
2234 <dd>Whether to place the sidebar on the left or right of the editor window.</dd>
2235 </dl>
2236 </div>
2237 <div class="section" id="fonts">
2238 <h4><a class="toc-backref" href="#id95">Fonts</a></h4>
2239 <dl class="docutils">
2240 <dt>Editor</dt>
2241 <dd>Change the font used to display documents.</dd>
2242 <dt>Symbol list</dt>
2243 <dd>Change the font used for the Symbols sidebar tab.</dd>
2244 <dt>Message window</dt>
2245 <dd>Change the font used for the message window area.</dd>
2246 </dl>
2247 </div>
2248 <div class="section" id="id2">
2249 <h4><a class="toc-backref" href="#id96">Miscellaneous</a></h4>
2250 <dl class="docutils">
2251 <dt>Show status bar</dt>
2252 <dd>Show the status bar at the bottom of the main window. It gives information about
2253 the file you are editing like the line and column you are on, whether any
2254 modifications were done, the file encoding, the filetype and other information.</dd>
2255 </dl>
2256 </div>
2257 </div>
2258 <div class="section" id="interface-notebook-tab-preferences">
2259 <h3><a class="toc-backref" href="#id97">Interface Notebook tab preferences</a></h3>
2260 <img alt="./images/pref_dialog_interface_notebook.png" src="./images/pref_dialog_interface_notebook.png" />
2261 <div class="section" id="editor-tabs">
2262 <h4><a class="toc-backref" href="#id98">Editor tabs</a></h4>
2263 <dl class="docutils">
2264 <dt>Show editor tabs</dt>
2265 <dd>Show a notebook tab for all documents so you can switch between them
2266 using the mouse (instead of using the Documents window).</dd>
2267 <dt>Show close buttons</dt>
2268 <dd>Make each tab show a close button so you can easily close open
2269 documents.</dd>
2270 <dt>Placement of new file tabs</dt>
2271 <dd>Whether to create a document with its notebook tab to the left or
2272 right of all existing tabs.</dd>
2273 <dt>Next to current</dt>
2274 <dd>Whether to place file tabs next to the current tab
2275 rather than at the edges of the notebook.</dd>
2276 <dt>Double-clicking hides all additional widgets</dt>
2277 <dd>Whether to call the View-&gt;Toggle All Additional Widgets command
2278 when double-clicking on a notebook tab.</dd>
2279 </dl>
2280 </div>
2281 <div class="section" id="tab-positions">
2282 <h4><a class="toc-backref" href="#id99">Tab positions</a></h4>
2283 <dl class="docutils">
2284 <dt>Editor</dt>
2285 <dd>Set the positioning of the editor's notebook tabs to the right,
2286 left, top, or bottom of the editing window.</dd>
2287 <dt>Sidebar</dt>
2288 <dd>Set the positioning of the sidebar's notebook tabs to the right,
2289 left, top, or bottom of the sidebar window.</dd>
2290 <dt>Message window</dt>
2291 <dd>Set the positioning of the message window's notebook tabs to the
2292 right, left, top, or bottom of the message window.</dd>
2293 </dl>
2294 </div>
2295 </div>
2296 <div class="section" id="interface-toolbar-preferences">
2297 <h3><a class="toc-backref" href="#id100">Interface Toolbar preferences</a></h3>
2298 <p>Affects the main toolbar underneath the menu bar.</p>
2299 <img alt="./images/pref_dialog_interface_toolbar.png" src="./images/pref_dialog_interface_toolbar.png" />
2300 <div class="section" id="toolbar">
2301 <h4><a class="toc-backref" href="#id101">Toolbar</a></h4>
2302 <dl class="docutils">
2303 <dt>Show Toolbar</dt>
2304 <dd>Whether to show the toolbar.</dd>
2305 <dt>Append Toolbar to the Menu</dt>
2306 <dd>Allows to append the toolbar to the main menu bar instead of placing it below.
2307 This is useful to save vertical space.</dd>
2308 <dt>Customize Toolbar</dt>
2309 <dd>See <a class="reference internal" href="#customizing-the-toolbar">Customizing the toolbar</a>.</dd>
2310 </dl>
2311 </div>
2312 <div class="section" id="appearance">
2313 <h4><a class="toc-backref" href="#id102">Appearance</a></h4>
2314 <dl class="docutils">
2315 <dt>Icon Style</dt>
2316 <dd>Select the toolbar icon style to use - either icons and text, just
2317 icons or just text.
2318 The choice System default uses whatever icon style is set by GTK.</dd>
2319 <dt>Icon size</dt>
2320 <dd>Select the size of the icons you see (large, small or very small).
2321 The choice System default uses whatever icon size is set by GTK.</dd>
2322 </dl>
2323 </div>
2324 </div>
2325 <div class="section" id="editor-features-preferences">
2326 <h3><a class="toc-backref" href="#id103">Editor Features preferences</a></h3>
2327 <img alt="./images/pref_dialog_edit_features.png" src="./images/pref_dialog_edit_features.png" />
2328 <div class="section" id="features">
2329 <h4><a class="toc-backref" href="#id104">Features</a></h4>
2330 <dl class="docutils">
2331 <dt>Line wrapping</dt>
2332 <dd>Show long lines wrapped around to new display lines.</dd>
2333 <dt>&quot;Smart&quot; home key</dt>
2334 <dd>Whether to move the cursor to the first non-whitespace character
2335 on the line when you hit the home key on your keyboard. Pressing it
2336 again will go to the very start of the line.</dd>
2337 <dt>Disable Drag and Drop</dt>
2338 <dd>Do not allow the dragging and dropping of selected text in documents.</dd>
2339 <dt>Code folding</dt>
2340 <dd>Allow groups of lines in a document to be collapsed for easier
2341 navigation/editing.</dd>
2342 <dt>Fold/Unfold all children of a fold point</dt>
2343 <dd>Whether to fold/unfold all child fold points when a parent line
2344 is folded.</dd>
2345 <dt>Use indicators to show compile errors</dt>
2346 <dd>Underline lines with compile errors using red squiggles to indicate
2347 them in the editor area.</dd>
2348 <dt>Newline strip trailing spaces</dt>
2349 <dd>Remove any white space at the end of the line when you hit the
2350 Enter/Return key.</dd>
2351 <dt>Line breaking column</dt>
2352 <dd>The editor column number to insert a newline at when Line Breaking
2353 is enabled for the current document.</dd>
2354 <dt>Comment toggle marker</dt>
2355 <dd>A string which is added when toggling a line comment in a source file.
2356 It is used to mark the comment as toggled.</dd>
2357 </dl>
2358 </div>
2359 </div>
2360 <div class="section" id="editor-indentation-preferences">
2361 <h3><a class="toc-backref" href="#id105">Editor Indentation preferences</a></h3>
2362 <img alt="./images/pref_dialog_edit_indentation.png" src="./images/pref_dialog_edit_indentation.png" />
2363 <div class="section" id="indentation-group">
2364 <h4><a class="toc-backref" href="#id106">Indentation group</a></h4>
2365 <p>See <a class="reference internal" href="#indentation">Indentation</a> for more information.</p>
2366 <dl class="docutils">
2367 <dt>Width</dt>
2368 <dd>The width of a single indent size in spaces. By default the indent
2369 size is equivalent to 4 spaces.</dd>
2370 <dt>Detect width from file</dt>
2371 <dd>Try to detect and set the indent width based on file content, when
2372 a file is opened.</dd>
2373 <dt>Type</dt>
2374 <dd><p class="first">When Geany inserts indentation, whether to use:</p>
2375 <ul class="simple">
2376 <li>Just Tabs</li>
2377 <li>Just Spaces</li>
2378 <li>Tabs and Spaces, depending on how much indentation is on a line</li>
2379 </ul>
2380 <p class="last">The <em>Tabs and Spaces</em> indent type is also known as <em>Soft tab
2381 support</em> in some other editors.</p>
2382 </dd>
2383 <dt>Detect type from file</dt>
2384 <dd>Try to detect and set the indent type based on file content, when
2385 a file is opened.</dd>
2386 <dt>Auto-indent mode</dt>
2387 <dd><p class="first">The type of auto-indentation you wish to use after pressing Enter,
2388 if any.</p>
2389 <dl class="last docutils">
2390 <dt>Basic</dt>
2391 <dd>Just add the indentation of the previous line.</dd>
2392 <dt>Current chars</dt>
2393 <dd>Add indentation based on the current filetype and any characters at
2394 the end of the line such as <tt class="docutils literal">{</tt>, <tt class="docutils literal">}</tt> for C, <tt class="docutils literal">:</tt> for Python.</dd>
2395 <dt>Match braces</dt>
2396 <dd>Like <em>Current chars</em> but for C-like languages, make a closing
2397 <tt class="docutils literal">}</tt> brace line up with the matching opening brace.</dd>
2398 </dl>
2399 </dd>
2400 <dt>Tab key indents</dt>
2401 <dd><p class="first">If set, pressing tab will indent the current line or selection, and
2402 unindent when pressing Shift-tab. Otherwise, the tab key will
2403 insert a tab character into the document (which can be different
2404 from indentation, depending on the indent type).</p>
2405 <div class="note last">
2406 <p class="first admonition-title">Note</p>
2407 <p class="last">There are also separate configurable keybindings for indent &amp;
2408 unindent, but this preference allows the tab key to have different
2409 meanings in different contexts - e.g. for snippet completion.</p>
2410 </div>
2411 </dd>
2412 </dl>
2413 </div>
2414 </div>
2415 <div class="section" id="editor-completions-preferences">
2416 <h3><a class="toc-backref" href="#id107">Editor Completions preferences</a></h3>
2417 <img alt="./images/pref_dialog_edit_completions.png" src="./images/pref_dialog_edit_completions.png" />
2418 <div class="section" id="completions">
2419 <h4><a class="toc-backref" href="#id108">Completions</a></h4>
2420 <dl class="docutils">
2421 <dt>Snippet Completion</dt>
2422 <dd>Whether to replace special keywords after typing Tab into a
2423 pre-defined text snippet.
2424 See <a class="reference internal" href="#user-definable-snippets">User-definable snippets</a>.</dd>
2425 <dt>XML/HTML tag auto-closing</dt>
2426 <dd>When you open an XML/HTML tag automatically generate its
2427 completion tag.</dd>
2428 <dt>Automatic continuation multi-line comments</dt>
2429 <dd><p class="first">Continue automatically multi-line comments in languages like C, C++
2430 and Java when a new line is entered inside such a comment.
2431 With this option enabled, Geany will insert a <tt class="docutils literal">*</tt> on every new line
2432 inside a multi-line comment, for example when you press return in the
2433 following C code:</p>
2434 <pre class="literal-block">
2435 /*
2436  * This is a C multi-line comment, press &lt;Return&gt;
2437 </pre>
2438 <p>then Geany would insert:</p>
2439 <pre class="literal-block">
2440 *
2441 </pre>
2442 <p class="last">on the next line with the correct indentation based on the previous line,
2443 as long as the multi-line is not closed by <tt class="docutils literal">*/</tt>.</p>
2444 </dd>
2445 <dt>Autocomplete symbols</dt>
2446 <dd>When you start to type a symbol name, look for the full string to
2447 allow it to be completed for you.</dd>
2448 <dt>Autocomplete all words in document</dt>
2449 <dd>When you start to type a word, Geany will search the whole document for
2450 words starting with the typed part to complete it, assuming there
2451 are no tag names to show.</dd>
2452 <dt>Drop rest of word on completion</dt>
2453 <dd>Remove any word part to the right of the cursor when choosing a
2454 completion list item.</dd>
2455 <dt>Characters to type for autocompletion</dt>
2456 <dd>Number of characters of a word to type before autocompletion is
2457 displayed.</dd>
2458 <dt>Completion list height</dt>
2459 <dd>The number of rows to display for the autocompletion window.</dd>
2460 <dt>Max. symbol name suggestions</dt>
2461 <dd>The maximum number of items in the autocompletion list.</dd>
2462 <dt>Symbol list update frequency</dt>
2463 <dd><p class="first">The minimum delay (in milliseconds) between two symbol list updates.</p>
2464 <p>This option determines how frequently the tag list is updated for the
2465 current document. The smaller the delay, the more up-to-date the symbol
2466 list (and then the completions); but rebuilding the symbol list has a
2467 cost in performance, especially with large files.</p>
2468 <p>The default value is 250ms, which means the symbol list will be updated
2469 at most four times per second, even if the document changes continuously.</p>
2470 <p class="last">A value of 0 disables automatic updates, so the symbol list will only be
2471 updated upon document saving.</p>
2472 </dd>
2473 </dl>
2474 </div>
2475 <div class="section" id="auto-close-quotes-and-brackets">
2476 <h4><a class="toc-backref" href="#id109">Auto-close quotes and brackets</a></h4>
2477 <p>Geany can automatically insert a closing bracket and quote characters when
2478 you open them. For instance, you type a <tt class="docutils literal">(</tt> and Geany will automatically
2479 insert <tt class="docutils literal">)</tt>. With the following options, you can define for which
2480 characters this should work.</p>
2481 <dl class="docutils">
2482 <dt>Parenthesis ( )</dt>
2483 <dd>Auto-close parenthesis when typing an opening one</dd>
2484 <dt>Curly brackets { }</dt>
2485 <dd>Auto-close curly brackets (braces) when typing an opening one</dd>
2486 <dt>Square brackets [ ]</dt>
2487 <dd>Auto-close square brackets when typing an opening one</dd>
2488 <dt>Single quotes ' '</dt>
2489 <dd>Auto-close single quotes when typing an opening one</dd>
2490 <dt>Double quotes &quot; &quot;</dt>
2491 <dd>Auto-close double quotes when typing an opening one</dd>
2492 </dl>
2493 </div>
2494 </div>
2495 <div class="section" id="editor-display-preferences">
2496 <h3><a class="toc-backref" href="#id110">Editor Display preferences</a></h3>
2497 <p>This is for visual elements displayed in the editor window.</p>
2498 <img alt="./images/pref_dialog_edit_display.png" src="./images/pref_dialog_edit_display.png" />
2499 <div class="section" id="display">
2500 <h4><a class="toc-backref" href="#id111">Display</a></h4>
2501 <dl class="docutils">
2502 <dt>Invert syntax highlighting colors</dt>
2503 <dd>Invert all colors, by default this makes white text on a black
2504 background.</dd>
2505 <dt>Show indendation guides</dt>
2506 <dd>Show vertical lines to help show how much leading indentation there
2507 is on each line.</dd>
2508 <dt>Show whitespaces</dt>
2509 <dd>Mark all tabs with an arrow &quot;--&gt;&quot; symbol and spaces with dots to
2510 show which kinds of whitespace are used.</dd>
2511 <dt>Show line endings</dt>
2512 <dd>Display a symbol everywhere that a carriage return or line feed
2513 is present.</dd>
2514 <dt>Show line numbers</dt>
2515 <dd>Show or hide the Line Number margin.</dd>
2516 <dt>Show markers margin</dt>
2517 <dd>Show or hide the small margin right of the line numbers, which is used
2518 to mark lines.</dd>
2519 <dt>Stop scrolling at last line</dt>
2520 <dd>When enabled Geany stops scrolling when at the last line of the document.
2521 Otherwise you can scroll one more page even if there are no real lines.</dd>
2522 </dl>
2523 </div>
2524 <div class="section" id="long-line-marker">
2525 <h4><a class="toc-backref" href="#id112">Long line marker</a></h4>
2526 <p>The long line marker helps to indicate overly-long lines, or as a hint
2527 to the user for when to break the line.</p>
2528 <dl class="docutils">
2529 <dt>Type</dt>
2530 <dd><dl class="first last docutils">
2531 <dt>Line</dt>
2532 <dd>Show a thin vertical line in the editor window at the given column
2533 position.</dd>
2534 <dt>Background</dt>
2535 <dd>Change the background color of characters after the given column
2536 position to the color set below. (This is recommended over the
2537 <em>Line</em> setting if you use proportional fonts).</dd>
2538 <dt>Disabled</dt>
2539 <dd>Don't mark long lines at all.</dd>
2540 </dl>
2541 </dd>
2542 <dt>Long line marker</dt>
2543 <dd>Set this value to a value greater than zero to specify the column
2544 where it should appear.</dd>
2545 <dt>Long line marker color</dt>
2546 <dd>Set the color of the long line marker.</dd>
2547 </dl>
2548 </div>
2549 <div class="section" id="virtual-spaces">
2550 <h4><a class="toc-backref" href="#id113">Virtual spaces</a></h4>
2551 <p>Virtual space is space beyond the end of each line.
2552 The cursor may be moved into virtual space but no real space will be
2553 added to the document until there is some text typed or some other
2554 text insertion command is used.</p>
2555 <dl class="docutils">
2556 <dt>Disabled</dt>
2557 <dd>Do not show virtual spaces</dd>
2558 <dt>Only for rectangular selections</dt>
2559 <dd>Only show virtual spaces beyond the end of lines when drawing a rectangular selection</dd>
2560 <dt>Always</dt>
2561 <dd>Always show virtual spaces beyond the end of lines</dd>
2562 </dl>
2563 </div>
2564 </div>
2565 <div class="section" id="files-preferences">
2566 <h3><a class="toc-backref" href="#id114">Files preferences</a></h3>
2567 <img alt="./images/pref_dialog_files.png" src="./images/pref_dialog_files.png" />
2568 <div class="section" id="new-files">
2569 <h4><a class="toc-backref" href="#id115">New files</a></h4>
2570 <dl class="docutils">
2571 <dt>Open new documents from the command-line</dt>
2572 <dd>Whether to create new documents when passing filenames that don't
2573 exist from the command-line.</dd>
2574 <dt>Default encoding (new files)</dt>
2575 <dd>The type of file encoding you wish to use when creating files.</dd>
2576 <dt>Used fixed encoding when opening files</dt>
2577 <dd>Assume all files you are opening are using the type of encoding specified below.</dd>
2578 <dt>Default encoding (existing files)</dt>
2579 <dd>Opens all files with the specified encoding instead of auto-detecting it.
2580 Use this option when it's not possible for Geany to detect the exact encoding.</dd>
2581 <dt>Default end of line characters</dt>
2582 <dd>The end of line characters to which should be used for new files.
2583 On Windows systems, you generally want to use CR/LF which are the common
2584 characters to mark line breaks.
2585 On Unix-like systems, LF is default and CR is used on MAC systems.</dd>
2586 </dl>
2587 </div>
2588 <div class="section" id="saving-files">
2589 <h4><a class="toc-backref" href="#id116">Saving files</a></h4>
2590 <p>Perform formatting operations when a document is saved. These
2591 can each be undone with the Undo command.</p>
2592 <dl class="docutils">
2593 <dt>Ensure newline at file end</dt>
2594 <dd>Add a newline at the end of the document if one is missing.</dd>
2595 <dt>Ensure consistent line endings</dt>
2596 <dd>Ensures that newline characters always get converted before
2597 saving, avoiding mixed line endings in the same file.</dd>
2598 <dt>Strip trailing spaces</dt>
2599 <dd>Remove the trailing spaces on each line of the document.</dd>
2600 <dt>Replace tabs by space</dt>
2601 <dd><p class="first">Replace all tabs in the document with the equivalent number of spaces.</p>
2602 <div class="note last">
2603 <p class="first admonition-title">Note</p>
2604 <p class="last">It is better to use spaces to indent than use this preference - see
2605 <a class="reference internal" href="#indentation">Indentation</a>.</p>
2606 </div>
2607 </dd>
2608 </dl>
2609 </div>
2610 <div class="section" id="id3">
2611 <h4><a class="toc-backref" href="#id117">Miscellaneous</a></h4>
2612 <dl class="docutils">
2613 <dt>Recent files list length</dt>
2614 <dd>The number of files to remember in the recently used files list.</dd>
2615 <dt>Disk check timeout</dt>
2616 <dd><p class="first">The number of seconds to periodically check the current document's
2617 file on disk in case it has changed. Setting it to 0 will disable
2618 this feature.</p>
2619 <div class="note last">
2620 <p class="first admonition-title">Note</p>
2621 <p class="last">These checks are only performed on local files. Remote files are
2622 not checked for changes due to performance issues
2623 (remote files are files in <tt class="docutils literal"><span class="pre">~/.gvfs/</span></tt>).</p>
2624 </div>
2625 </dd>
2626 </dl>
2627 </div>
2628 </div>
2629 <div class="section" id="tools-preferences">
2630 <h3><a class="toc-backref" href="#id118">Tools preferences</a></h3>
2631 <img alt="./images/pref_dialog_tools.png" src="./images/pref_dialog_tools.png" />
2632 <div class="section" id="tool-paths">
2633 <h4><a class="toc-backref" href="#id119">Tool paths</a></h4>
2634 <dl class="docutils">
2635 <dt>Terminal</dt>
2636 <dd>The location of your terminal executable.</dd>
2637 <dt>Browser</dt>
2638 <dd>The location of your web browser executable.</dd>
2639 <dt>Grep</dt>
2640 <dd>The location of the grep executable.</dd>
2641 </dl>
2642 <div class="note">
2643 <p class="first admonition-title">Note</p>
2644 <p class="last">For Windows users: at the time of writing it is recommended to use
2645 the grep.exe from the UnxUtils project
2646 (<a class="reference external" href="http://sourceforge.net/projects/unxutils">http://sourceforge.net/projects/unxutils</a>). The grep.exe from the
2647 Mingw project for instance might not work with Geany at the moment.</p>
2648 </div>
2649 </div>
2650 <div class="section" id="commands">
2651 <h4><a class="toc-backref" href="#id120">Commands</a></h4>
2652 <dl class="docutils">
2653 <dt>Context action</dt>
2654 <dd>Set this to a command to execute on the current word.
2655 You can use the &quot;%s&quot; wildcard to pass the current word below the cursor
2656 to the specified command.</dd>
2657 </dl>
2658 </div>
2659 </div>
2660 <div class="section" id="template-preferences">
2661 <h3><a class="toc-backref" href="#id121">Template preferences</a></h3>
2662 <p>This data is used as meta data for various template text to insert into
2663 a document, such as the file header. You only need to set fields that
2664 you want to use in your template files.</p>
2665 <img alt="./images/pref_dialog_templ.png" src="./images/pref_dialog_templ.png" />
2666 <div class="section" id="template-data">
2667 <h4><a class="toc-backref" href="#id122">Template data</a></h4>
2668 <dl class="docutils">
2669 <dt>Developer</dt>
2670 <dd>The name of the developer who will be creating files.</dd>
2671 <dt>Initials</dt>
2672 <dd>The initials of the developer.</dd>
2673 <dt>Mail address</dt>
2674 <dd><p class="first">The email address of the developer.</p>
2675 <div class="note last">
2676 <p class="first admonition-title">Note</p>
2677 <p class="last">You may wish to add anti-spam markup, e.g. <tt class="docutils literal">name&lt;at&gt;site&lt;dot&gt;ext</tt>.</p>
2678 </div>
2679 </dd>
2680 <dt>Company</dt>
2681 <dd>The company the developer is working for.</dd>
2682 <dt>Initial version</dt>
2683 <dd>The initial version of files you will be creating.</dd>
2684 <dt>Year</dt>
2685 <dd>Specify a format for the the {year} wildcard. You can use any conversion specifiers
2686 which can be used with the ANSI C strftime function.  For details please see
2687 <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
2688 <dt>Date</dt>
2689 <dd>Specify a format for the the {date} wildcard. You can use any conversion specifiers
2690 which can be used with the ANSI C strftime function.  For details please see
2691 <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
2692 <dt>Date &amp; Time</dt>
2693 <dd>Specify a format for the the {datetime} wildcard. You can use any conversion specifiers
2694 which can be used with the ANSI C strftime function.  For details please see
2695 <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
2696 </dl>
2697 </div>
2698 </div>
2699 <div class="section" id="keybinding-preferences">
2700 <h3><a class="toc-backref" href="#id123">Keybinding preferences</a></h3>
2701 <img alt="./images/pref_dialog_keys.png" src="./images/pref_dialog_keys.png" />
2702 <p>There are some commands listed in the keybinding dialog that are not, by default,
2703 bound to a key combination, and may not be available as a menu item.</p>
2704 <div class="note">
2705 <p class="first admonition-title">Note</p>
2706 <p class="last">For more information see the section <a class="reference internal" href="#keybindings">Keybindings</a>.</p>
2707 </div>
2708 </div>
2709 <div class="section" id="printing-preferences">
2710 <h3><a class="toc-backref" href="#id124">Printing preferences</a></h3>
2711 <img alt="./images/pref_dialog_printing.png" src="./images/pref_dialog_printing.png" />
2712 <dl class="docutils">
2713 <dt>Use external command for printing</dt>
2714 <dd>Use a system command to print your file out.</dd>
2715 <dt>Use native GTK printing</dt>
2716 <dd>Let the GTK GUI toolkit handle your print request.</dd>
2717 <dt>Print line numbers</dt>
2718 <dd>Print the line numbers on the left of your paper.</dd>
2719 <dt>Print page number</dt>
2720 <dd>Print the page number on the bottom right of your paper.</dd>
2721 <dt>Print page header</dt>
2722 <dd>Print a header on every page that is sent to the printer.</dd>
2723 <dt>Use base name of the printed file</dt>
2724 <dd>Don't use the entire path for the header, only the filename.</dd>
2725 <dt>Date format</dt>
2726 <dd>How the date should be printed. You can use the same format
2727 specifiers as in the ANSI C function strftime(). For details please
2728 see <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</dd>
2729 </dl>
2730 </div>
2731 <div class="section" id="various-preferences">
2732 <h3><a class="toc-backref" href="#id125">Various preferences</a></h3>
2733 <img alt="./images/pref_dialog_various.png" src="./images/pref_dialog_various.png" />
2734 <p>Rarely used preferences, explained in the table below. A few of them require
2735 restart to take effect, and a few other will only affect newly opened or created
2736 documents before restart.</p>
2737 <table border="1" class="docutils">
2738 <colgroup>
2739 <col width="34%" />
2740 <col width="44%" />
2741 <col width="11%" />
2742 <col width="12%" />
2743 </colgroup>
2744 <thead valign="bottom">
2745 <tr><th class="head">Key</th>
2746 <th class="head">Description</th>
2747 <th class="head">Default</th>
2748 <th class="head">Applies</th>
2749 </tr>
2750 </thead>
2751 <tbody valign="top">
2752 <tr><td><strong>Editor related</strong></td>
2753 <td>&nbsp;</td>
2754 <td>&nbsp;</td>
2755 <td>&nbsp;</td>
2756 </tr>
2757 <tr><td>use_gtk_word_boundaries</td>
2758 <td>Whether to look for the end of a word
2759 when using word-boundary related
2760 Scintilla commands (see <a class="reference internal" href="#scintilla-keyboard-commands">Scintilla
2761 keyboard commands</a>).</td>
2762 <td>true</td>
2763 <td>to new
2764 documents</td>
2765 </tr>
2766 <tr><td>brace_match_ltgt</td>
2767 <td>Whether to highlight &lt;, &gt; angle brackets.</td>
2768 <td>false</td>
2769 <td>immediately</td>
2770 </tr>
2771 <tr><td>complete_snippets_whilst_editing</td>
2772 <td>Whether to allow completion of snippets
2773 when editing an existing line (i.e. there
2774 is some text after the current cursor
2775 position on the line). Only used when the
2776 keybinding <cite>Complete snippet</cite> is set to
2777 <tt class="docutils literal">Space</tt>.</td>
2778 <td>false</td>
2779 <td>immediately</td>
2780 </tr>
2781 <tr><td>show_editor_scrollbars</td>
2782 <td>Whether to display scrollbars. If set to
2783 false, the horizontal and vertical
2784 scrollbars are hidden completely.</td>
2785 <td>true</td>
2786 <td>immediately</td>
2787 </tr>
2788 <tr><td>indent_hard_tab_width</td>
2789 <td>The size of a tab character. Don't change
2790 it unless you really need to; use the
2791 indentation settings instead.</td>
2792 <td>8</td>
2793 <td>immediately</td>
2794 </tr>
2795 <tr><td><strong>Interface related</strong></td>
2796 <td>&nbsp;</td>
2797 <td>&nbsp;</td>
2798 <td>&nbsp;</td>
2799 </tr>
2800 <tr><td>show_symbol_list_expanders</td>
2801 <td>Whether to show or hide the small
2802 expander icons on the symbol list</td>
2803 <td>true</td>
2804 <td>to new
2805 documents</td>
2806 </tr>
2807 <tr><td>allow_always_save</td>
2808 <td>treeview. Whether files can be saved
2809 always, even if they don't have any
2810 changes. By default, the Save button and
2811 menu item are disabled when a file is
2812 unchanged. When setting this option to
2813 true, the Save button and menu item are
2814 always active and files can be saved.</td>
2815 <td>false</td>
2816 <td>immediately</td>
2817 </tr>
2818 <tr><td>compiler_tab_autoscroll</td>
2819 <td>Whether to automatically scroll to the
2820 last line of the output in the Compiler
2821 tab.</td>
2822 <td>true</td>
2823 <td>immediately</td>
2824 </tr>
2825 <tr><td>statusbar_template</td>
2826 <td>The status bar statistics line format.
2827 (Search in src/ui_utils.c for details).</td>
2828 <td>See below.</td>
2829 <td>immediately</td>
2830 </tr>
2831 <tr><td>new_document_after_close</td>
2832 <td>Whether to open a new document after all
2833 documents have been closed.</td>
2834 <td>false</td>
2835 <td>immediately</td>
2836 </tr>
2837 <tr><td>msgwin_status_visible</td>
2838 <td>Whether to show the Status tab in the
2839 Messages Window</td>
2840 <td>true</td>
2841 <td>immediately</td>
2842 </tr>
2843 <tr><td>msgwin_compiler_visible</td>
2844 <td>Whether to show the Compiler tab in the
2845 Messages Window</td>
2846 <td>true</td>
2847 <td>immediately</td>
2848 </tr>
2849 <tr><td>msgwin_messages_visible</td>
2850 <td>Whether to show the Messages tab in the
2851 Messages Window</td>
2852 <td>true</td>
2853 <td>immediately</td>
2854 </tr>
2855 <tr><td>msgwin_scribble_visible</td>
2856 <td>Whether to show the Scribble tab in the
2857 Messages Window</td>
2858 <td>true</td>
2859 <td>immediately</td>
2860 </tr>
2861 </tbody>
2862 </table>
2863 <p>By default, statusbar_template is empty. This tells Geany to use its
2864 internal default, which is currently:</p>
2865 <p><tt class="docutils literal">line: %l / %L\t col: %c\t sel: %s\t %w&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; %t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; %mmode: %M&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; encoding: %e&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; filetype: %f&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scope: %S</tt></p>
2866 <p>Note that <tt class="docutils literal">\t</tt> = tab.</p>
2867 <table border="1" class="docutils">
2868 <colgroup>
2869 <col width="34%" />
2870 <col width="46%" />
2871 <col width="9%" />
2872 <col width="12%" />
2873 </colgroup>
2874 <thead valign="bottom">
2875 <tr><th class="head">Key</th>
2876 <th class="head">Description</th>
2877 <th class="head">Default</th>
2878 <th class="head">Applies</th>
2879 </tr>
2880 </thead>
2881 <tbody valign="top">
2882 <tr><td><strong>VTE related</strong></td>
2883 <td>&nbsp;</td>
2884 <td>&nbsp;</td>
2885 <td>&nbsp;</td>
2886 </tr>
2887 <tr><td>emulation</td>
2888 <td>Terminal emulation mode. Only change this
2889 if you have VTE termcap files other than
2890 <tt class="docutils literal">vte/termcap/xterm</tt>.</td>
2891 <td>xterm</td>
2892 <td>immediately</td>
2893 </tr>
2894 <tr><td>send_selection_unsafe</td>
2895 <td>By default, Geany strips any trailing
2896 newline characters from the current
2897 selection before sending it to the terminal
2898 to not execute arbitrary code. This is
2899 mainly a security feature.
2900 If, for whatever reasons, you really want
2901 it to be executed directly, set this option
2902 to true.</td>
2903 <td>false</td>
2904 <td>immediately</td>
2905 </tr>
2906 <tr><td><strong>File related</strong></td>
2907 <td>&nbsp;</td>
2908 <td>&nbsp;</td>
2909 <td>&nbsp;</td>
2910 </tr>
2911 <tr><td>use_atomic_file_saving</td>
2912 <td>Defines the mode how Geany saves files to
2913 disk. If disabled, Geany directly writes
2914 the content of the document to disk. This
2915 might cause loss of data when there is
2916 no more free space on disk to save the
2917 file. When set to true, Geany first saves
2918 the contents into a temporary file and if
2919 this succeeded, the temporary file is
2920 moved to the real file to save.
2921 This gives better error checking in case of
2922 no more free disk space. But it also
2923 destroys hard links of the original file
2924 and its permissions (e.g. executable flags
2925 are reset). Use this with care as it can
2926 break things seriously.
2927 The better approach would be to ensure your
2928 disk won't run out of free space.</td>
2929 <td>false</td>
2930 <td>immediately</td>
2931 </tr>
2932 <tr><td>use_gio_unsafe_file_saving</td>
2933 <td>Whether to use GIO as the unsafe file
2934 saving backend. It is better on most
2935 situations but is known not to work
2936 correctly on some complex setups.</td>
2937 <td>true</td>
2938 <td>immediately</td>
2939 </tr>
2940 <tr><td>gio_unsafe_save_backup</td>
2941 <td>Make a backup when using GIO unsafe file
2942 saving. Backup is named <cite>filename~</cite>.</td>
2943 <td>false</td>
2944 <td>immediately</td>
2945 </tr>
2946 <tr><td><strong>Search related</strong></td>
2947 <td>&nbsp;</td>
2948 <td>&nbsp;</td>
2949 <td>&nbsp;</td>
2950 </tr>
2951 <tr><td>find_selection_type</td>
2952 <td>See <a class="reference internal" href="#find-selection">Find selection</a>.</td>
2953 <td>0</td>
2954 <td>immediately</td>
2955 </tr>
2956 <tr><td><strong>Build Menu related</strong></td>
2957 <td>&nbsp;</td>
2958 <td>&nbsp;</td>
2959 <td>&nbsp;</td>
2960 </tr>
2961 <tr><td>number_ft_menu_items</td>
2962 <td>The maximum number of menu items in the
2963 filetype section of the Build menu.</td>
2964 <td>2</td>
2965 <td>on restart</td>
2966 </tr>
2967 <tr><td>number_non_ft_menu_items</td>
2968 <td>The maximum number of menu items in the
2969 independent section of the Build menu.</td>
2970 <td>3</td>
2971 <td>on restart</td>
2972 </tr>
2973 <tr><td>number_exec_menu_items</td>
2974 <td>The maximum number of menu items in the
2975 execute section of the Build menu.</td>
2976 <td>2</td>
2977 <td>on restart</td>
2978 </tr>
2979 </tbody>
2980 </table>
2981 </div>
2982 <div class="section" id="terminal-vte-preferences">
2983 <h3><a class="toc-backref" href="#id126">Terminal (VTE) preferences</a></h3>
2984 <p>See also: <a class="reference internal" href="#virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a>.</p>
2985 <img alt="./images/pref_dialog_vte.png" src="./images/pref_dialog_vte.png" />
2986 <div class="section" id="terminal-widget">
2987 <h4><a class="toc-backref" href="#id127">Terminal widget</a></h4>
2988 <dl class="docutils">
2989 <dt>Terminal font</dt>
2990 <dd>Select the font that will be used in the terminal emulation control.</dd>
2991 <dt>Foreground color</dt>
2992 <dd>Select the font color.</dd>
2993 <dt>Background color</dt>
2994 <dd>Select the background color of the terminal.</dd>
2995 <dt>Scrollback lines</dt>
2996 <dd>The number of lines buffered so that you can scroll though the history.</dd>
2997 <dt>Shell</dt>
2998 <dd>The location of the shell on your system.</dd>
2999 <dt>Scroll on keystroke</dt>
3000 <dd>Scroll the terminal to the prompt line when pressing a key.</dd>
3001 <dt>Scroll on output</dt>
3002 <dd>Scroll the output down.</dd>
3003 <dt>Cursor blinks</dt>
3004 <dd>Let the terminal cursor blink.</dd>
3005 <dt>Override Geany keybindings</dt>
3006 <dd>Allow the VTE to receive keyboard shortcuts (apart from focus commands).</dd>
3007 <dt>Disable menu shortcut key (F10 by default)</dt>
3008 <dd>Disable the menu shortcut when you are in the virtual terminal.</dd>
3009 <dt>Follow path of the current file</dt>
3010 <dd>Make the path of the terminal change according to the path of the
3011 current file.</dd>
3012 <dt>Execute programs in VTE</dt>
3013 <dd>Execute programs in the virtual terminal instead of using the external
3014 terminal tool.  Note that if you run multiple execute commands at once
3015 the output may become mixed together in the VTE.</dd>
3016 <dt>Don't use run script</dt>
3017 <dd>Don't use the simple run script which is usually used to display
3018 the exit status of the executed program.
3019 This can be useful if you already have a program running in the VTE
3020 like a Python console (e.g. ipython). Use this with care.</dd>
3021 </dl>
3022 </div>
3023 </div>
3024 </div>
3025 <div class="section" id="project-management">
3026 <h2><a class="toc-backref" href="#id128">Project management</a></h2>
3027 <p>Project management is optional in Geany. Currently it can be used for:</p>
3028 <ul class="simple">
3029 <li>Storing and opening session files on a project basis.</li>
3030 <li>Overriding default settings with project equivalents.</li>
3031 <li>Configuring the Build menu on a project basis.</li>
3032 </ul>
3033 <p>A list of session files can be stored and opened with the project
3034 when the <em>Use project-based session files</em> preference is enabled,
3035 in the <em>Project</em> group of the <a class="reference internal" href="#preferences">Preferences</a> dialog.</p>
3036 <p>As long as a project is open, the Build menu will use
3037 the items defined in project's settings, instead of the defaults.
3038 See <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a> for information on configuring the menu.</p>
3039 <p>The current project's settings are saved when it is closed, or when
3040 Geany is shutdown. When restarting Geany, the previously opened project
3041 file that was in use at the end of the last session will be reopened.</p>
3042 <p>The project menu items are detailed below.</p>
3043 <div class="section" id="new-project">
3044 <h3><a class="toc-backref" href="#id129">New project</a></h3>
3045 <p>To create a new project, fill in the <em>Name</em> field. By default this
3046 will setup a new project file <tt class="docutils literal">~/projects/name.geany</tt>. Usually it's
3047 best to store all your project files in the same directory (they are
3048 independent of any source directory trees).</p>
3049 <p>The Base path text field is setup to use <tt class="docutils literal">~/projects/name</tt>. This
3050 can safely be set to any existing path -- it will not touch the file
3051 structure contained in it.</p>
3052 </div>
3053 <div class="section" id="project-properties">
3054 <h3><a class="toc-backref" href="#id130">Project properties</a></h3>
3055 <p>You can set an optional description for the project. Currently it's
3056 only used for a template wildcard - see <a class="reference internal" href="#template-wildcards">Template wildcards</a>.</p>
3057 <p>The <em>Base path</em> field is used as the directory to run the Build menu commands.
3058 The specified path can be an absolute path or it is considered to be
3059 relative to the project's file name.</p>
3060 <p>The <em>File patterns</em> field allows to specify a list of file patterns for the
3061 project, which can be used in the <a class="reference internal" href="#find-in-files">Find in files</a> dialog.</p>
3062 <p>The <em>Indentation</em> tab allows you to override the default
3063 <a class="reference internal" href="#indentation">Indentation</a> settings.</p>
3064 </div>
3065 <div class="section" id="open-project">
3066 <h3><a class="toc-backref" href="#id131">Open project</a></h3>
3067 <p>The Open command displays a standard file chooser, starting in
3068 <tt class="docutils literal">~/projects</tt>. Choose a project file named with the <tt class="docutils literal">.geany</tt>
3069 extension.</p>
3070 <p>When project session support is enabled, Geany will close the currently
3071 open files and open the session files associated with the project.</p>
3072 </div>
3073 <div class="section" id="close-project">
3074 <h3><a class="toc-backref" href="#id132">Close project</a></h3>
3075 <p>Project file settings are saved when the project is closed.</p>
3076 <p>When project session support is enabled, Geany will close the project
3077 session files and open any previously closed default session files.</p>
3078 </div>
3079 </div>
3080 <div class="section" id="build-menu">
3081 <h2><a class="toc-backref" href="#id133">Build menu</a></h2>
3082 <p>After editing code with Geany, the next step is to compile, link, build,
3083 interpret, run etc.  As Geany supports many languages each with a different
3084 approach to such operations, and as there are also many language independent
3085 software building systems, Geany does not have a built-in build system, nor
3086 does it limit which system you can use.  Instead the build menu provides
3087 a configurable and flexible means of running any external commands to
3088 execute your preferred build system.</p>
3089 <p>This section provides a description of the default configuration of the
3090 build menu and then covers how to configure it, and where the defaults fit in.</p>
3091 <p>Running the commands from within Geany has two benefits:</p>
3092 <ul class="simple">
3093 <li>The current file is automatically saved before the command is run.</li>
3094 <li>The output is captured in the Compiler notebook tab and parsed for
3095 warnings or errors.</li>
3096 </ul>
3097 <p>Warnings and errors that can be parsed for line numbers will be shown in
3098 red in the Compiler tab and you can click on them to switch to the relevant
3099 source file (or open it) and mark the line number.  Also lines with
3100 warnings or errors are marked in the source, see <a class="reference internal" href="#indicators">Indicators</a> below.</p>
3101 <div class="tip">
3102 <p class="first admonition-title">Tip</p>
3103 <p class="last">If Geany's default error message parsing does not parse errors for
3104 the tool you're using, you can set a custom regex in the Build Commands
3105 Dialog, see <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a>.</p>
3106 </div>
3107 <div class="section" id="indicators">
3108 <h3><a class="toc-backref" href="#id134">Indicators</a></h3>
3109 <p>Indicators are red squiggly underlines which are used to highlight
3110 errors which occurred while compiling the current file. So you can
3111 easily see where your code failed to compile. You can remove them by
3112 selecting <em>Remove Error Indicators</em> in the Document menu.</p>
3113 <p>If you do not like this feature, you can disable it - see <a class="reference internal" href="#editor-features-preferences">Editor Features
3114 preferences</a>.</p>
3115 </div>
3116 <div class="section" id="default-build-menu-items">
3117 <h3><a class="toc-backref" href="#id135">Default build menu items</a></h3>
3118 <p>Depending on the current file's filetype, the default Build menu will contain
3119 the following items:</p>
3120 <ul class="simple">
3121 <li>Compile</li>
3122 <li>Build</li>
3123 <li>Make All</li>
3124 <li>Make Custom Target</li>
3125 <li>Make Object</li>
3126 <li>Next Error</li>
3127 <li>Previous Error</li>
3128 <li>Execute</li>
3129 <li>Set Build Menu Commands</li>
3130 </ul>
3131 <div class="section" id="compile">
3132 <h4><a class="toc-backref" href="#id136">Compile</a></h4>
3133 <p>The Compile command has different uses for different kinds of files.</p>
3134 <p>For compilable languages such as C and C++, the Compile command is
3135 set up to compile the current source file into a binary object file.</p>
3136 <p>Java source files will be compiled to class file bytecode.</p>
3137 <p>Interpreted languages such as Perl, Python, Ruby will compile to
3138 bytecode if the language supports it, or will run a syntax check,
3139 or if that is not available will run the file in its language interpreter.</p>
3140 </div>
3141 <div class="section" id="build">
3142 <h4><a class="toc-backref" href="#id137">Build</a></h4>
3143 <p>For compilable languages such as C and C++, the Build command will link
3144 the current source file's equivalent object file into an executable. If
3145 the object file does not exist, the source will be compiled and linked
3146 in one step, producing just the executable binary.</p>
3147 <p>Interpreted languages do not use the Build command.</p>
3148 <div class="note">
3149 <p class="first admonition-title">Note</p>
3150 <p class="last">If you need complex settings for your build system, or several
3151 different settings, then writing a Makefile and using the Make
3152 commands is recommended; this will also make it easier for users to
3153 build your software.</p>
3154 </div>
3155 </div>
3156 <div class="section" id="make">
3157 <h4><a class="toc-backref" href="#id138">Make</a></h4>
3158 <p>This runs &quot;make&quot; in the same directory as the
3159 current file.</p>
3160 </div>
3161 <div class="section" id="make-custom-target">
3162 <h4><a class="toc-backref" href="#id139">Make custom target</a></h4>
3163 <p>This is similar to running 'Make' but you will be prompted for
3164 the make target name to be passed to the Make tool. For example,
3165 typing 'clean' in the dialog prompt will run &quot;make clean&quot;.</p>
3166 </div>
3167 <div class="section" id="make-object">
3168 <h4><a class="toc-backref" href="#id140">Make object</a></h4>
3169 <p>Make object will run &quot;make current_file.o&quot; in the same directory as
3170 the current file, using the filename for 'current_file'. It is useful
3171 for building just the current file without building the whole project.</p>
3172 </div>
3173 <div class="section" id="next-error">
3174 <h4><a class="toc-backref" href="#id141">Next error</a></h4>
3175 <p>The next error item will move to the next detected error in the file.</p>
3176 </div>
3177 <div class="section" id="previous-error">
3178 <h4><a class="toc-backref" href="#id142">Previous error</a></h4>
3179 <p>The previous error item will move to the previous detected error in the file.</p>
3180 </div>
3181 <div class="section" id="execute">
3182 <h4><a class="toc-backref" href="#id143">Execute</a></h4>
3183 <p>Execute will run the corresponding executable file, shell script or
3184 interpreted script in a terminal window. Note that the Terminal tool
3185 path must be correctly set in the Tools tab of the Preferences dialog -
3186 you can use any terminal program that runs a Bourne compatible shell
3187 and accept the &quot;-e&quot; command line argument to start a command or can be
3188 selected to use the built-in VTE if it is available - see
3189 <a class="reference internal" href="#virtual-terminal-emulator-widget-vte">Virtual terminal emulator widget (VTE)</a>.</p>
3190 <p>After your program or script has finished executing, you will be
3191 prompted to press the return key. This allows you to review any text
3192 output from the program before the terminal window is closed.</p>
3193 <div class="note">
3194 <p class="first admonition-title">Note</p>
3195 <p class="last">The execute command output is not parsed for errors.</p>
3196 </div>
3197 </div>
3198 <div class="section" id="stopping-running-processes">
3199 <h4><a class="toc-backref" href="#id144">Stopping running processes</a></h4>
3200 <p>When there is a running program, the Execute menu item in the menu and
3201 the Run button in the toolbar
3202 each become a stop button so you can stop the current running program (and
3203 any child processes). This works by sending the SIGQUIT signal to the process.</p>
3204 <p>Depending on the process you started it is possible that the process
3205 cannot be stopped. For example this can happen when the process creates
3206 more than one child process.</p>
3207 <div class="section" id="terminal-emulators">
3208 <h5><a class="toc-backref" href="#id145">Terminal emulators</a></h5>
3209 <p>Xterm is known to work properly. If you are using &quot;Terminal&quot;
3210 (the terminal program of Xfce), you should add the command line
3211 option <tt class="docutils literal"><span class="pre">--disable-server</span></tt> otherwise the started process cannot be
3212 stopped. Just add this option in the preferences dialog on the Tools
3213 tab in the terminal field.</p>
3214 </div>
3215 </div>
3216 <div class="section" id="set-build-commands">
3217 <h4><a class="toc-backref" href="#id146">Set build commands</a></h4>
3218 <p>By default Compile, Build and Execute are fairly basic commands. You
3219 may wish to customise them using <em>Set Build Commands</em>.</p>
3220 <p>E.g. for C you can add any include paths and compile flags for the
3221 compiler, any library names and paths for the linker, and any
3222 arguments you want to use when running Execute.</p>
3223 </div>
3224 </div>
3225 <div class="section" id="build-menu-configuration">
3226 <h3><a class="toc-backref" href="#id147">Build menu configuration</a></h3>
3227 <p>The build menu has considerable flexibility and configurability, allowing
3228 both menu labels the commands they execute and the directory they execute
3229 in to be configured.</p>
3230 <p>For example, if you change one of the default make commands to run say 'waf'
3231 you can also change the label to match.</p>
3232 <p>These settings are saved automatically when Geany is shut down.</p>
3233 <p>The build menu is divided into four groups of items each with different
3234 behaviors:</p>
3235 <ul class="simple">
3236 <li>Filetype build commands - are configurable and depend on the filetype of the
3237 current document; they capture output in the compiler tab and parse it for
3238 errors.</li>
3239 <li>Independent build commands - are configurable and mostly don't depend on the
3240 filetype of the current document; they also capture output in the
3241 compiler tab and parse it for errors.</li>
3242 <li>Execute commands - are configurable and intended for executing your
3243 program or other long running programs.  The output is not parsed for errors
3244 and is directed to the terminal selected in preferences.</li>
3245 <li>Fixed commands - these perform built-in actions:<ul>
3246 <li>Go to the next error.</li>
3247 <li>Go to the previous error.</li>
3248 <li>Show the build menu commands dialog.</li>
3249 </ul>
3250 </li>
3251 </ul>
3252 <p>The maximum numbers of items in each of the configurable groups can be
3253 configured in the <a class="reference internal" href="#various-preferences">Various preferences</a>. Even though the maximum number of
3254 items may have been increased, only those menu items that have values
3255 configured are shown in the menu.</p>
3256 <p>The groups of menu items obtain their configuration from four potential
3257 sources.  The highest priority source that has the menu item defined will
3258 be used. The sources in decreasing priority are:</p>
3259 <ul class="simple">
3260 <li>A project file if open</li>
3261 <li>The user preferences</li>
3262 <li>The system filetype definitions</li>
3263 <li>The defaults</li>
3264 </ul>
3265 <p>The detailed relationships between sources and the configurable menu item groups
3266 is shown in the following table.</p>
3267 <table border="1" class="docutils">
3268 <colgroup>
3269 <col width="13%" />
3270 <col width="19%" />
3271 <col width="23%" />
3272 <col width="17%" />
3273 <col width="28%" />
3274 </colgroup>
3275 <thead valign="bottom">
3276 <tr><th class="head">Group</th>
3277 <th class="head">Project File</th>
3278 <th class="head">Preferences</th>
3279 <th class="head">System Filetype</th>
3280 <th class="head">Defaults</th>
3281 </tr>
3282 </thead>
3283 <tbody valign="top">
3284 <tr><td>Filetype</td>
3285 <td><p class="first">Loads From: project
3286 file</p>
3287 <p class="last">Saves To: project
3288 file</p>
3289 </td>
3290 <td><p class="first">Loads From:
3291 filetypes.xxx file in
3292 ~/.config/geany/filedefs</p>
3293 <p class="last">Saves to: as above,
3294 creating if needed.</p>
3295 </td>
3296 <td><p class="first">Loads From:
3297 filetypes.xxx in
3298 Geany install</p>
3299 <p class="last">Saves to: as user
3300 preferences left.</p>
3301 </td>
3302 <td>None</td>
3303 </tr>
3304 <tr><td>Filetype
3305 Independent</td>
3306 <td><p class="first">Loads From: project
3307 file</p>
3308 <p class="last">Saves To: project
3309 file</p>
3310 </td>
3311 <td><p class="first">Loads From:
3312 geany.conf file in
3313 ~/.config/geany</p>
3314 <p class="last">Saves to: as above,
3315 creating if needed.</p>
3316 </td>
3317 <td><p class="first">Loads From:
3318 filetypes.xxx in
3319 Geany install</p>
3320 <p class="last">Saves to: as user
3321 preferences left.</p>
3322 </td>
3323 <td><dl class="first last docutils">
3324 <dt>1:</dt>
3325 <dd>Label: _Make
3326 Command: make</dd>
3327 <dt>2:</dt>
3328 <dd>Label: Make Custom _Target
3329 Command: make</dd>
3330 <dt>3:</dt>
3331 <dd>Label: Make _Object
3332 Command: make %e.o</dd>
3333 </dl>
3334 </td>
3335 </tr>
3336 <tr><td>Execute</td>
3337 <td><p class="first">Loads From: project
3338 file or else
3339 filetype defined in
3340 project file</p>
3341 <p class="last">Saves To:
3342 project file</p>
3343 </td>
3344 <td><p class="first">Loads From:
3345 geany.conf file in
3346 ~/.config/geany or else
3347 filetypes.xxx file in
3348 ~/.config/geany/filedefs</p>
3349 <p class="last">Saves To:
3350 filetypes.xxx file in
3351 ~/.config/geany/filedefs</p>
3352 </td>
3353 <td><p class="first">Loads From:
3354 filetypes.xxx in
3355 Geany install</p>
3356 <p class="last">Saves To: as user
3357 preferences left.</p>
3358 </td>
3359 <td>Label: _Execute
3360 Command: ./%e</td>
3361 </tr>
3362 </tbody>
3363 </table>
3364 <p>The following notes on the table reference cells by coordinate as (group,source):</p>
3365 <ul class="simple">
3366 <li>General - for filetypes.xxx substitute the appropriate extension for
3367 the filetype of the current document for xxx - see <a class="reference internal" href="#filenames">filenames</a>.</li>
3368 <li>System Filetypes - Labels loaded from these sources are locale sensitive
3369 and can contain translations.</li>
3370 <li>(Filetype, Project File) and (Filetype, Preferences) - preferences use a full
3371 filetype file so that users can configure all other filetype preferences
3372 as well.  Projects can only configure menu items per filetype.  Saving
3373 in the project file means that there is only one file per project not
3374 a whole directory.</li>
3375 <li>(Filetype-Independent, System Filetype) - although conceptually strange, defining
3376 filetype-independent commands in a filetype file, this provides the ability to
3377 define filetype dependent default menu items.</li>
3378 <li>(Execute, Project File) and (Execute, Preferences) - the project independent
3379 execute and preferences independent execute commands can only be set by hand
3380 editing the appropriate file, see <a class="reference internal" href="#preferences-file-format">Preferences file format</a> and <a class="reference internal" href="#project-file-format">Project file
3381 format</a>.</li>
3382 </ul>
3383 </div>
3384 <div class="section" id="build-menu-commands-dialog">
3385 <h3><a class="toc-backref" href="#id148">Build menu commands dialog</a></h3>
3386 <p>Most of the configuration of the build menu is done through the Build Menu
3387 Commands Dialog.  You edit the configuration sourced from preferences in the
3388 dialog opened from the Build-&gt;Build Menu Commands item and you edit the
3389 configuration from the project in the build tab of the project preferences
3390 dialog.  Both use the same form shown below.</p>
3391 <img alt="./images/build_menu_commands_dialog.png" src="./images/build_menu_commands_dialog.png" />
3392 <p>The dialog is divided into three sections:</p>
3393 <ul class="simple">
3394 <li>Filetype build commands (selected based on the current document's filetype).</li>
3395 <li>Independent build commands (available regardless of filetype).</li>
3396 <li>Filetype execute commands.</li>
3397 </ul>
3398 <p>The filetype and independent sections also each contain a field for the regular
3399 expression used for parsing command output for error and warning messages.</p>
3400 <p>The columns in the first three sections allow setting of the label, command,
3401 and working directory to run the command in.</p>
3402 <p>An item with an empty label will not be shown in the menu.</p>
3403 <p>An empty working directory will default to the directory of the current document.
3404 If there is no current document then the command will not run.</p>
3405 <p>The dialog will always show the command selected by priority, not just the
3406 commands configured in this configuration source. This ensures that you always
3407 see what the menu item is going to do if activated.</p>
3408 <p>If the current source of the menu item is higher priority than the
3409 configuration source you are editing then the command will be shown
3410 in the dialog but will be insensitive (greyed out).  This can't happen
3411 with the project source but can with the preferences source dialog.</p>
3412 <p>The clear buttons remove the definition from the configuration source you are editing.
3413 When you do this the command from the next lower priority source will be shown.
3414 To hide lower priority menu items without having anything show in the menu
3415 configure with a nothing in the label but at least one character in the command.</p>
3416 <div class="section" id="substitutions-in-commands-and-working-directories">
3417 <h4><a class="toc-backref" href="#id149">Substitutions in commands and working directories</a></h4>
3418 <p>The first occurence of each of the following character sequences in each of the
3419 command and working directory fields is substituted by the items specified below
3420 before the command is run.</p>
3421 <ul class="simple">
3422 <li>%d - substituted by the absolute path to the directory of the current file.</li>
3423 <li>%e - substituted by the name of the current file without the extension or path.</li>
3424 <li>%f - substituted by the name of the current file without the path.</li>
3425 <li>%p - if a project is open, substituted by the base path from the project.</li>
3426 </ul>
3427 <div class="note">
3428 <p class="first admonition-title">Note</p>
3429 <p class="last">If the basepath set in the project preferences is not an absolute path , then it is
3430 taken as relative to the directory of the project file.  This allows a project file
3431 stored in the source tree to specify all commands and working directories relative
3432 to the tree itself, so that the whole tree including the project file, can be moved
3433 and even checked into and out of version control without having to re-configure the
3434 build menu.</p>
3435 </div>
3436 </div>
3437 <div class="section" id="build-menu-keyboard-shortcuts">
3438 <h4><a class="toc-backref" href="#id150">Build menu keyboard shortcuts</a></h4>
3439 <p>Keyboard shortcuts can be defined for the first two filetype menu items, the first three
3440 independent menu items, the first two execute menu items and the fixed menu items.
3441 In the keybindings configuration dialog (see <a class="reference internal" href="#keybinding-preferences">Keybinding preferences</a>)
3442 these items are identified by the default labels shown in the <a class="reference internal" href="#build-menu">Build Menu</a> section above.</p>
3443 <p>It is currently not possible to bind keyboard shortcuts to more than these menu items.</p>
3444 <p>You can also use underlines in the labels to set mnemonic characters.</p>
3445 </div>
3446 <div class="section" id="old-settings">
3447 <h4><a class="toc-backref" href="#id151">Old settings</a></h4>
3448 <p>The configurable Build Menu capability was introduced in Geany 0.19 and
3449 required a new section to be added to the configuration files (See
3450 <a class="reference internal" href="#preferences-file-format">Preferences file format</a>).  Geany will still load older format project,
3451 preferences and filetype file settings and will attempt to map them into the new
3452 configuration format.  There is not a simple clean mapping between the formats.
3453 The mapping used produces the most sensible results for the majority of cases.
3454 However, if they do not map the way you want, you may have to manually
3455 configure some settings using the Build Commands
3456 Dialog or the Build tab of the project preferences dialog.</p>
3457 <p>Any setting configured in either of these dialogs will override settings mapped from
3458 older format configuration files.</p>
3459 </div>
3460 </div>
3461 </div>
3462 <div class="section" id="printing-support">
3463 <h2><a class="toc-backref" href="#id152">Printing support</a></h2>
3464 <p>Since Geany 0.13 there has been printing support using GTK's printing API.
3465 The printed page(s) will look nearly the same as on your screen in Geany.
3466 Additionally, there are some options to modify the printed page(s).</p>
3467 <div class="note">
3468 <p class="first admonition-title">Note</p>
3469 <p class="last">The background text color is set to white, except for text with
3470 a white foreground. This allows dark color schemes to save ink
3471 when printing.</p>
3472 </div>
3473 <p>You can define whether to print line numbers, page numbers at the bottom of
3474 each page and whether to print a page header on each page. This header
3475 contains the filename of the printed document, the current page number and
3476 the date and time of printing. By default, the file name of the document
3477 with full path information is added to the header. If you prefer to add
3478 only the basename of the file(without any path information) you can set it
3479 in the preferences dialog. You can also adjust the format of the date and
3480 time added to the page header. The available conversion specifiers are the
3481 same as the ones which can be used with the ANSI C strftime function.</p>
3482 <p>All of these settings can also be changed in the print dialog just before
3483 actual printing is done.
3484 On Unix-like systems the provided print dialog offers a print preview. The
3485 preview file is opened with a PDF viewer and by default GTK uses <tt class="docutils literal">evince</tt>
3486 for print preview. If you have not installed evince or just want to use
3487 another PDF viewer, you can change the program to use in the file
3488 <tt class="docutils literal"><span class="pre">.gtkrc-2.0</span></tt> (usually found in your home directory). Simply add a line
3489 like:</p>
3490 <pre class="literal-block">
3491 gtk-print-preview-command = &quot;epdfview %f&quot;
3492 </pre>
3493 <p>at the end of the file. Of course, you can also use xpdf, kpdf or whatever
3494 as the print preview command.</p>
3495 <p>Geany also provides an alternative basic printing support using a custom
3496 print command. However, the printed document contains no syntax highlighting.
3497 You can adjust the command to which the filename is passed in the preferences
3498 dialog. The default command is:</p>
3499 <pre class="literal-block">
3500 % lpr %f
3501 </pre>
3502 <p><tt class="docutils literal">%f</tt> will be substituted by the filename of the current file. Geany
3503 will not show errors from the command itself, so you should make
3504 sure that it works before(e.g. by trying to execute it from the
3505 command line).</p>
3506 <p>A nicer example, which many prefer is:</p>
3507 <pre class="literal-block">
3508 % a2ps -1 --medium=A4 -o - %f | xfprint4
3509 </pre>
3510 <p>But this depends on a2ps and xfprint4. As a replacement for xfprint4,
3511 gtklp or similar programs can be used.</p>
3512 </div>
3513 <div class="section" id="plugins">
3514 <h2><a class="toc-backref" href="#id153">Plugins</a></h2>
3515 <p>Plugins are loaded at startup, if the <em>Enable plugin support</em>
3516 general preference is set. There is also a command-line option,
3517 <tt class="docutils literal"><span class="pre">-p</span></tt>, which prevents plugins being loaded. Plugins are scanned in
3518 the following directories:</p>
3519 <ul class="simple">
3520 <li><tt class="docutils literal">$prefix/lib/geany</tt> (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>)</li>
3521 <li>The <tt class="docutils literal">plugins</tt> subfolder of the user configuration directory - see
3522 <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>.</li>
3523 <li>The <cite>Extra plugin path</cite> preference (usually blank) - see <a class="reference internal" href="#paths">Paths</a>.</li>
3524 </ul>
3525 <p>Most plugins add menu items to the <em>Tools</em> menu when they are loaded.</p>
3526 <p>See also <a class="reference internal" href="#plugin-documentation">Plugin documentation</a> for information about single plugins
3527 which are included in Geany.</p>
3528 <div class="section" id="plugin-manager">
3529 <h3><a class="toc-backref" href="#id154">Plugin manager</a></h3>
3530 <p>The Plugin Manager dialog lets you choose which plugins
3531 should be loaded at startup. You can also load and unload plugins on the
3532 fly using this dialog. Once you click the checkbox for a specific plugin
3533 in the dialog, it is loaded or unloaded according to its previous state.
3534 By default, no plugins are loaded at startup until you select some.
3535 You can also configure some plugin specific options if the plugin
3536 provides any.</p>
3537 </div>
3538 </div>
3539 <div class="section" id="keybindings">
3540 <h2><a class="toc-backref" href="#id155">Keybindings</a></h2>
3541 <p>Geany supports the default keyboard shortcuts for the Scintilla
3542 editing widget. For a list of these commands, see <a class="reference internal" href="#scintilla-keyboard-commands">Scintilla
3543 keyboard commands</a>. The Scintilla keyboard shortcuts will be overridden
3544 by any custom keybindings with the same keyboard shortcut.</p>
3545 <div class="section" id="switching-documents">
3546 <h3><a class="toc-backref" href="#id156">Switching documents</a></h3>
3547 <p>There are a few non-configurable bindings to switch between documents,
3548 listed below. These can also be overridden by custom keybindings.</p>
3549 <table border="1" class="docutils">
3550 <colgroup>
3551 <col width="31%" />
3552 <col width="69%" />
3553 </colgroup>
3554 <thead valign="bottom">
3555 <tr><th class="head">Key</th>
3556 <th class="head">Action</th>
3557 </tr>
3558 </thead>
3559 <tbody valign="top">
3560 <tr><td>Alt-[1-9]</td>
3561 <td>Select left-most tab, from 1 to 9.</td>
3562 </tr>
3563 <tr><td>Alt-0</td>
3564 <td>Select right-most tab.</td>
3565 </tr>
3566 <tr><td>Ctrl-Shift-PgUp</td>
3567 <td>Select left-most tab.</td>
3568 </tr>
3569 <tr><td>Ctrl-Shift-PgDn</td>
3570 <td>Select right-most tab.</td>
3571 </tr>
3572 </tbody>
3573 </table>
3574 </div>
3575 <div class="section" id="configurable-keybindings">
3576 <h3><a class="toc-backref" href="#id157">Configurable keybindings</a></h3>
3577 <p>For all actions listed below you can define your own keybindings. Open
3578 the Preferences dialog, select the desired action and click on
3579 change. In the resulting dialog you can press the key combination you
3580 want to assign to the action and it will be saved when you press OK.
3581 You can define only one key combination for each action and each key
3582 combination can only be defined for one action.</p>
3583 <p>Some of the default key combinations are common across many
3584 applications, for example <em>Ctrl-N</em> for New and <em>Ctrl-O</em> for Open.
3585 Because they are so common it is not advisable to change these, but
3586 you can add other key combinations for these actions. For example
3587 <em>Ctrl-O</em> is set to execute menu_open by default, but you can also
3588 define <em>Alt-O</em>, so that the file open dialog is shown by pressing
3589 either <em>Ctrl-O</em> or <em>Alt-O</em>.</p>
3590 <p>The following tables list all customizable keyboard shortcuts, those
3591 which are common to many applications are marked with (C) after the
3592 shortcut.</p>
3593 <div class="section" id="file-keybindings">
3594 <h4><a class="toc-backref" href="#id158">File keybindings</a></h4>
3595 <table border="1" class="docutils">
3596 <colgroup>
3597 <col width="29%" />
3598 <col width="24%" />
3599 <col width="47%" />
3600 </colgroup>
3601 <thead valign="bottom">
3602 <tr><th class="head">Action</th>
3603 <th class="head">Default shortcut</th>
3604 <th class="head">Description</th>
3605 </tr>
3606 </thead>
3607 <tbody valign="top">
3608 <tr><td>New</td>
3609 <td>Ctrl-N  (C)</td>
3610 <td>Creates a new file.</td>
3611 </tr>
3612 <tr><td>Open</td>
3613 <td>Ctrl-O  (C)</td>
3614 <td>Opens a file.</td>
3615 </tr>
3616 <tr><td>Open selected file</td>
3617 <td>Ctrl-Shift-O</td>
3618 <td>Opens the selected filename.</td>
3619 </tr>
3620 <tr><td>Re-open last closed tab</td>
3621 <td>&nbsp;</td>
3622 <td>Re-opens the last closed document tab.</td>
3623 </tr>
3624 <tr><td>Save</td>
3625 <td>Ctrl-S  (C)</td>
3626 <td>Saves the current file.</td>
3627 </tr>
3628 <tr><td>Save As</td>
3629 <td>&nbsp;</td>
3630 <td>Saves the current file under a new name.</td>
3631 </tr>
3632 <tr><td>Save all</td>
3633 <td>Ctrl-Shift-S</td>
3634 <td>Saves all open files.</td>
3635 </tr>
3636 <tr><td>Close all</td>
3637 <td>Ctrl-Shift-W</td>
3638 <td>Closes all open files.</td>
3639 </tr>
3640 <tr><td>Close</td>
3641 <td>Ctrl-W  (C)</td>
3642 <td>Closes the current file.</td>
3643 </tr>
3644 <tr><td>Reload file</td>
3645 <td>Ctrl-R  (C)</td>
3646 <td>Reloads the current file. All unsaved changes
3647 will be lost.</td>
3648 </tr>
3649 <tr><td>Print</td>
3650 <td>Ctrl-P  (C)</td>
3651 <td>Prints the current file.</td>
3652 </tr>
3653 </tbody>
3654 </table>
3655 </div>
3656 <div class="section" id="editor-keybindings">
3657 <h4><a class="toc-backref" href="#id159">Editor keybindings</a></h4>
3658 <table border="1" class="docutils">
3659 <colgroup>
3660 <col width="29%" />
3661 <col width="24%" />
3662 <col width="47%" />
3663 </colgroup>
3664 <thead valign="bottom">
3665 <tr><th class="head">Action</th>
3666 <th class="head">Default shortcut</th>
3667 <th class="head">Description</th>
3668 </tr>
3669 </thead>
3670 <tbody valign="top">
3671 <tr><td>Undo</td>
3672 <td>Ctrl-Z  (C)</td>
3673 <td>Un-does the last action.</td>
3674 </tr>
3675 <tr><td>Redo</td>
3676 <td>Ctrl-Y</td>
3677 <td>Re-does the last action.</td>
3678 </tr>
3679 <tr><td>Delete current line(s)</td>
3680 <td>Ctrl-K</td>
3681 <td>Deletes the current line (and any lines with a
3682 selection).</td>
3683 </tr>
3684 <tr><td>Delete to line end</td>
3685 <td>Ctrl-Shift-Delete</td>
3686 <td>Deletes from the current caret position to the
3687 end of the current line.</td>
3688 </tr>
3689 <tr><td>Duplicate line or selection</td>
3690 <td>Ctrl-D</td>
3691 <td>Duplicates the current line or selection.</td>
3692 </tr>
3693 <tr><td>Transpose current line</td>
3694 <td>Ctrl-T</td>
3695 <td>Transposes the current line with the previous one.</td>
3696 </tr>
3697 <tr><td>Scroll to current line</td>
3698 <td>Ctrl-Shift-L</td>
3699 <td>Scrolls the current line into the centre of the
3700 view. The cursor position and or an existing
3701 selection will not be changed.</td>
3702 </tr>
3703 <tr><td>Scroll up by one line</td>
3704 <td>Alt-Up</td>
3705 <td>Scrolls the view.</td>
3706 </tr>
3707 <tr><td>Scroll down by one line</td>
3708 <td>Alt-Down</td>
3709 <td>Scrolls the view.</td>
3710 </tr>
3711 <tr><td>Complete word</td>
3712 <td>Ctrl-Space</td>
3713 <td>Shows the autocompletion list. If already showing
3714 tag completion, it shows document word completion
3715 instead, even if it is not enabled for automatic
3716 completion. Likewise if no tag suggestions are
3717 available, it shows document word completion.</td>
3718 </tr>
3719 <tr><td>Show calltip</td>
3720 <td>Ctrl-Shift-Space</td>
3721 <td>Shows a calltip for the current function or
3722 method.</td>
3723 </tr>
3724 <tr><td>Show macro list</td>
3725 <td>Ctrl-Return</td>
3726 <td>Shows a list of available macros and variables in
3727 the workspace.</td>
3728 </tr>
3729 <tr><td>Complete snippet</td>
3730 <td>Tab</td>
3731 <td>If you type a construct like if or for and press
3732 this key, it will be completed with a matching
3733 template.</td>
3734 </tr>
3735 <tr><td>Suppress snippet completion</td>
3736 <td>&nbsp;</td>
3737 <td>If you type a construct like if or for and press
3738 this key, it will not be completed, and a space or
3739 tab will be inserted, depending on what the
3740 construct completion keybinding is set to. For
3741 example, if you have set the construct completion
3742 keybinding to space, then setting this to
3743 Shift+space will prevent construct completion and
3744 insert a space.</td>
3745 </tr>
3746 <tr><td>Context Action</td>
3747 <td>&nbsp;</td>
3748 <td>Executes a command and passes the current word
3749 (near the cursor position) or selection as an
3750 argument. See the section called <a class="reference internal" href="#context-actions">Context
3751 actions</a>.</td>
3752 </tr>
3753 <tr><td>Move cursor in snippet</td>
3754 <td>&nbsp;</td>
3755 <td>Jumps to the next defined cursor positions in a
3756 completed snippets if multiple cursor positions
3757 where defined.</td>
3758 </tr>
3759 <tr><td>Word part completion</td>
3760 <td>Tab</td>
3761 <td>When the autocompletion list is visible, complete
3762 the currently selected item up to the next word
3763 part.</td>
3764 </tr>
3765 <tr><td>Move line(s) up</td>
3766 <td>&nbsp;</td>
3767 <td>Move the current line or selected lines up by
3768 one line.</td>
3769 </tr>
3770 <tr><td>Move line(s) down</td>
3771 <td>&nbsp;</td>
3772 <td>Move the current line or selected lines down by
3773 one line.</td>
3774 </tr>
3775 </tbody>
3776 </table>
3777 </div>
3778 <div class="section" id="clipboard-keybindings">
3779 <h4><a class="toc-backref" href="#id160">Clipboard keybindings</a></h4>
3780 <table border="1" class="docutils">
3781 <colgroup>
3782 <col width="29%" />
3783 <col width="23%" />
3784 <col width="48%" />
3785 </colgroup>
3786 <thead valign="bottom">
3787 <tr><th class="head">Action</th>
3788 <th class="head">Default shortcut</th>
3789 <th class="head">Description</th>
3790 </tr>
3791 </thead>
3792 <tbody valign="top">
3793 <tr><td>Cut</td>
3794 <td>Ctrl-X  (C)</td>
3795 <td>Cut the current selection to the clipboard.</td>
3796 </tr>
3797 <tr><td>Copy</td>
3798 <td>Ctrl-C  (C)</td>
3799 <td>Copy the current selection to the clipboard.</td>
3800 </tr>
3801 <tr><td>Paste</td>
3802 <td>Ctrl-V  (C)</td>
3803 <td>Paste the clipboard text into the current document.</td>
3804 </tr>
3805 <tr><td>Cut current line(s)</td>
3806 <td>Ctrl-Shift-X</td>
3807 <td>Cuts the current line (and any lines with a
3808 selection) to the clipboard.</td>
3809 </tr>
3810 <tr><td>Copy current line(s)</td>
3811 <td>Ctrl-Shift-C</td>
3812 <td>Copies the current line (and any lines with a
3813 selection) to the clipboard.</td>
3814 </tr>
3815 </tbody>
3816 </table>
3817 </div>
3818 <div class="section" id="select-keybindings">
3819 <h4><a class="toc-backref" href="#id161">Select keybindings</a></h4>
3820 <table border="1" class="docutils">
3821 <colgroup>
3822 <col width="29%" />
3823 <col width="24%" />
3824 <col width="47%" />
3825 </colgroup>
3826 <thead valign="bottom">
3827 <tr><th class="head">Action</th>
3828 <th class="head">Default shortcut</th>
3829 <th class="head">Description</th>
3830 </tr>
3831 </thead>
3832 <tbody valign="top">
3833 <tr><td>Select all</td>
3834 <td>Ctrl-A  (C)</td>
3835 <td>Makes a selection of all text in the current
3836 document.</td>
3837 </tr>
3838 <tr><td>Select current word</td>
3839 <td>Alt-Shift-W</td>
3840 <td>Selects the current word under the cursor.</td>
3841 </tr>
3842 <tr><td>Select current paragraph</td>
3843 <td>Alt-Shift-P</td>
3844 <td>Selects the current paragraph under the cursor
3845 which is defined by two empty lines around it.</td>
3846 </tr>
3847 <tr><td>Select current line(s)</td>
3848 <td>Alt-Shift-L</td>
3849 <td>Selects the current line under the cursor (and any
3850 partially selected lines).</td>
3851 </tr>
3852 <tr><td>Select to previous word part</td>
3853 <td>&nbsp;</td>
3854 <td>(Extend) selection to previous word part boundary.</td>
3855 </tr>
3856 <tr><td>Select to next word part</td>
3857 <td>&nbsp;</td>
3858 <td>(Extend) selection to next word part boundary.</td>
3859 </tr>
3860 </tbody>
3861 </table>
3862 </div>
3863 <div class="section" id="insert-keybindings">
3864 <h4><a class="toc-backref" href="#id162">Insert keybindings</a></h4>
3865 <table border="1" class="docutils">
3866 <colgroup>
3867 <col width="29%" />
3868 <col width="24%" />
3869 <col width="47%" />
3870 </colgroup>
3871 <thead valign="bottom">
3872 <tr><th class="head">Action</th>
3873 <th class="head">Default shortcut</th>
3874 <th class="head">Description</th>
3875 </tr>
3876 </thead>
3877 <tbody valign="top">
3878 <tr><td>Insert date</td>
3879 <td>Shift-Alt-D</td>
3880 <td>Inserts a customisable date.</td>
3881 </tr>
3882 <tr><td>Insert alternative whitespace</td>
3883 <td>&nbsp;</td>
3884 <td>Inserts a tab character when spaces should
3885 be used for indentation and inserts space
3886 characters of the amount of a tab width when
3887 tabs should be used for indentation.</td>
3888 </tr>
3889 <tr><td>Insert New Line Before Current</td>
3890 <td>&nbsp;</td>
3891 <td>Inserts a new line with indentation.</td>
3892 </tr>
3893 <tr><td>Insert New Line After Current</td>
3894 <td>&nbsp;</td>
3895 <td>Inserts a new line with indentation.</td>
3896 </tr>
3897 </tbody>
3898 </table>
3899 </div>
3900 <div class="section" id="format-keybindings">
3901 <h4><a class="toc-backref" href="#id163">Format keybindings</a></h4>
3902 <table border="1" class="docutils">
3903 <colgroup>
3904 <col width="29%" />
3905 <col width="24%" />
3906 <col width="47%" />
3907 </colgroup>
3908 <thead valign="bottom">
3909 <tr><th class="head">Action</th>
3910 <th class="head">Default shortcut</th>
3911 <th class="head">Description</th>
3912 </tr>
3913 </thead>
3914 <tbody valign="top">
3915 <tr><td>Toggle case of selection</td>
3916 <td>Ctrl-Alt-U</td>
3917 <td>Changes the case of the selection. A lowercase
3918 selection will be changed into uppercase and vice
3919 versa. If the selection contains lower- and
3920 uppercase characters, all will be converted to
3921 lowercase.</td>
3922 </tr>
3923 <tr><td>Comment line</td>
3924 <td>&nbsp;</td>
3925 <td>Comments current line or selection.</td>
3926 </tr>
3927 <tr><td>Uncomment line</td>
3928 <td>&nbsp;</td>
3929 <td>Uncomments current line or selection.</td>
3930 </tr>
3931 <tr><td>Toggle line commentation</td>
3932 <td>Ctrl-E</td>
3933 <td>Comments a line if it is not commented or removes
3934 a comment if the line is commented.</td>
3935 </tr>
3936 <tr><td>Increase indent</td>
3937 <td>Ctrl-I</td>
3938 <td>Indents the current line or selection by one tab
3939 or by spaces in the amount of the tab width
3940 setting.</td>
3941 </tr>
3942 <tr><td>Decrease indent</td>
3943 <td>Ctrl-U</td>
3944 <td>Removes one tab or the amount of spaces of
3945 the tab width setting from the indentation of the
3946 current line or selection.</td>
3947 </tr>
3948 <tr><td>Increase indent by one space</td>
3949 <td>&nbsp;</td>
3950 <td>Indents the current line or selection by one
3951 space.</td>
3952 </tr>
3953 <tr><td>Decrease indent by one space</td>
3954 <td>&nbsp;</td>
3955 <td>Deindents the current line or selection by one
3956 space.</td>
3957 </tr>
3958 <tr><td>Smart line indent</td>
3959 <td>&nbsp;</td>
3960 <td>Indents the current line or all selected lines
3961 with the same indentation as the previous line.</td>
3962 </tr>
3963 <tr><td>Send to Custom Command 1 (2,3)</td>
3964 <td>Ctrl-1 (2,3)</td>
3965 <td>Passes the current selection to a configured
3966 external command (available for the first
3967 three configured commands, see
3968 <a class="reference internal" href="#sending-text-through-custom-commands">Sending text through custom commands</a> for
3969 details).</td>
3970 </tr>
3971 <tr><td>Send Selection to Terminal</td>
3972 <td>&nbsp;</td>
3973 <td>Sends the current selection or the current
3974 line (if there is no selection) to the
3975 embedded Terminal (VTE).</td>
3976 </tr>
3977 <tr><td>Reflow lines/block</td>
3978 <td>&nbsp;</td>
3979 <td>Reformat selected lines or current
3980 (indented) text block,
3981 breaking lines at the long line marker or the
3982 line breaking column if line breaking is
3983 enabled for the current document.</td>
3984 </tr>
3985 </tbody>
3986 </table>
3987 </div>
3988 <div class="section" id="settings-keybindings">
3989 <h4><a class="toc-backref" href="#id164">Settings keybindings</a></h4>
3990 <table border="1" class="docutils">
3991 <colgroup>
3992 <col width="29%" />
3993 <col width="24%" />
3994 <col width="47%" />
3995 </colgroup>
3996 <thead valign="bottom">
3997 <tr><th class="head">Action</th>
3998 <th class="head">Default shortcut</th>
3999 <th class="head">Description</th>
4000 </tr>
4001 </thead>
4002 <tbody valign="top">
4003 <tr><td>Preferences</td>
4004 <td>Ctrl-Alt-P</td>
4005 <td>Opens preferences dialog.</td>
4006 </tr>
4007 <tr><td>Plugin Preferences</td>
4008 <td>&nbsp;</td>
4009 <td>Opens plugin preferences dialog.</td>
4010 </tr>
4011 </tbody>
4012 </table>
4013 </div>
4014 <div class="section" id="search-keybindings">
4015 <h4><a class="toc-backref" href="#id165">Search keybindings</a></h4>
4016 <table border="1" class="docutils">
4017 <colgroup>
4018 <col width="29%" />
4019 <col width="24%" />
4020 <col width="47%" />
4021 </colgroup>
4022 <thead valign="bottom">
4023 <tr><th class="head">Action</th>
4024 <th class="head">Default shortcut</th>
4025 <th class="head">Description</th>
4026 </tr>
4027 </thead>
4028 <tbody valign="top">
4029 <tr><td>Find</td>
4030 <td>Ctrl-F  (C)</td>
4031 <td>Opens the Find dialog.</td>
4032 </tr>
4033 <tr><td>Find Next</td>
4034 <td>Ctrl-G</td>
4035 <td>Finds next result.</td>
4036 </tr>
4037 <tr><td>Find Previous</td>
4038 <td>Ctrl-Shift-G</td>
4039 <td>Finds previous result.</td>
4040 </tr>
4041 <tr><td>Find Next Selection</td>
4042 <td>&nbsp;</td>
4043 <td>Finds next occurence of selected text.</td>
4044 </tr>
4045 <tr><td>Find Previous Selection</td>
4046 <td>&nbsp;</td>
4047 <td>Finds previous occurence of selected text.</td>
4048 </tr>
4049 <tr><td>Replace</td>
4050 <td>Ctrl-H  (C)</td>
4051 <td>Opens the Replace dialog.</td>
4052 </tr>
4053 <tr><td>Find in files</td>
4054 <td>Ctrl-Shift-F</td>
4055 <td>Opens the Find in files dialog.</td>
4056 </tr>
4057 <tr><td>Next message</td>
4058 <td>&nbsp;</td>
4059 <td>Jumps to the line with the next message in
4060 the Messages window.</td>
4061 </tr>
4062 <tr><td>Previous message</td>
4063 <td>&nbsp;</td>
4064 <td>Jumps to the line with the previous message
4065 in the Messages window.</td>
4066 </tr>
4067 <tr><td>Find Usage</td>
4068 <td>&nbsp;</td>
4069 <td>Finds all occurrences of the current word (near
4070 the keyboard cursor) or selection in all open
4071 documents and displays them in the messages
4072 window.</td>
4073 </tr>
4074 <tr><td>Find Document Usage</td>
4075 <td>&nbsp;</td>
4076 <td>Finds all occurrences of the current word (near
4077 the keyboard cursor) or selection in the current
4078 document and displays them in the messages
4079 window.</td>
4080 </tr>
4081 <tr><td>Mark All</td>
4082 <td>Ctrl-Shift-M</td>
4083 <td>Highlight all matches of the current
4084 word/selection in the current document
4085 with a colored box. If there's nothing to
4086 find, highlighted matches will be cleared.</td>
4087 </tr>
4088 </tbody>
4089 </table>
4090 </div>
4091 <div class="section" id="go-to-keybindings">
4092 <h4><a class="toc-backref" href="#id166">Go to keybindings</a></h4>
4093 <table border="1" class="docutils">
4094 <colgroup>
4095 <col width="29%" />
4096 <col width="24%" />
4097 <col width="47%" />
4098 </colgroup>
4099 <thead valign="bottom">
4100 <tr><th class="head">Action</th>
4101 <th class="head">Default shortcut</th>
4102 <th class="head">Description</th>
4103 </tr>
4104 </thead>
4105 <tbody valign="top">
4106 <tr><td>Navigate forward a location</td>
4107 <td>&nbsp;</td>
4108 <td>Switches to the next location in the navigation
4109 history. See the section called <a class="reference internal" href="#code-navigation-history">Code Navigation
4110 History</a>.</td>
4111 </tr>
4112 <tr><td>Navigate back a location</td>
4113 <td>&nbsp;</td>
4114 <td>Switches to the previous location in the
4115 navigation history. See the section called
4116 <a class="reference internal" href="#code-navigation-history">Code navigation history</a>.</td>
4117 </tr>
4118 <tr><td>Go to line</td>
4119 <td>Ctrl-L</td>
4120 <td>Focuses the Go to Line entry (if visible) or
4121 shows the Go to line dialog.</td>
4122 </tr>
4123 <tr><td>Goto matching brace</td>
4124 <td>Ctrl-B</td>
4125 <td>If the cursor is ahead or behind a brace, then it
4126 is moved to the brace which belongs to the current
4127 one. If this keyboard shortcut is pressed again,
4128 the cursor is moved back to the first brace.</td>
4129 </tr>
4130 <tr><td>Toggle marker</td>
4131 <td>Ctrl-M</td>
4132 <td>Set a marker on the current line, or clear the
4133 marker if there already is one.</td>
4134 </tr>
4135 <tr><td>Goto next marker</td>
4136 <td>Ctrl-.</td>
4137 <td>Goto the next marker in the current document.</td>
4138 </tr>
4139 <tr><td>Goto previous marker</td>
4140 <td>Ctrl-,</td>
4141 <td>Goto the previous marker in the current document.</td>
4142 </tr>
4143 <tr><td>Go to tag definition</td>
4144 <td>&nbsp;</td>
4145 <td>Jump to the definition of the current word (near
4146 the keyboard cursor). If the definition cannot be
4147 found (e.g. the relevant file is not open) Geany
4148 will beep and do nothing. See the section called
4149 <a class="reference internal" href="#go-to-tag-definition">Go to tag definition</a>.</td>
4150 </tr>
4151 <tr><td>Go to tag declaration</td>
4152 <td>&nbsp;</td>
4153 <td>Jump to the declaration of the current word (near
4154 the keyboard cursor). If the declaration cannot be
4155 found (e.g. the relevant file is not open) Geany
4156 will beep and do nothing. See the section called
4157 <a class="reference internal" href="#go-to-tag-declaration">Go to tag declaration</a>.</td>
4158 </tr>
4159 <tr><td>Go to Start of Line</td>
4160 <td>Home</td>
4161 <td>Move the caret to the end of the line indentation
4162 unless it is already there, in which case it moves
4163 it to the start of the line.</td>
4164 </tr>
4165 <tr><td>Go to End of Line</td>
4166 <td>End</td>
4167 <td>Move the caret to the end of the line.</td>
4168 </tr>
4169 <tr><td>Go to End of Display Line</td>
4170 <td>Alt-End</td>
4171 <td>Move the caret to the end of the display line.
4172 This is useful when you use line wrapping and
4173 want to jump to the end of the wrapped, virtual
4174 line, not the real end of the whole line.
4175 If the line is not wrapped, it behaves like
4176 <cite>Go to End of Line</cite>, see above.</td>
4177 </tr>
4178 <tr><td>Go to Previous Word Part</td>
4179 <td>Ctrl-/</td>
4180 <td>Goto the previous part of the current word.</td>
4181 </tr>
4182 <tr><td>Go to Next Word Part</td>
4183 <td>Ctrl-</td>
4184 <td>Goto the next part of the current word.</td>
4185 </tr>
4186 </tbody>
4187 </table>
4188 </div>
4189 <div class="section" id="view-keybindings">
4190 <h4><a class="toc-backref" href="#id167">View keybindings</a></h4>
4191 <table border="1" class="docutils">
4192 <colgroup>
4193 <col width="29%" />
4194 <col width="24%" />
4195 <col width="47%" />
4196 </colgroup>
4197 <thead valign="bottom">
4198 <tr><th class="head">Action</th>
4199 <th class="head">Default shortcut</th>
4200 <th class="head">Description</th>
4201 </tr>
4202 </thead>
4203 <tbody valign="top">
4204 <tr><td>Fullscreen</td>
4205 <td>F11  (C)</td>
4206 <td>Switches to fullscreen mode.</td>
4207 </tr>
4208 <tr><td>Toggle Messages Window</td>
4209 <td>&nbsp;</td>
4210 <td>Toggles the message window (status and compiler
4211 messages) on and off.</td>
4212 </tr>
4213 <tr><td>Toggle Sidebar</td>
4214 <td>&nbsp;</td>
4215 <td>Shows or hides the sidebar.</td>
4216 </tr>
4217 <tr><td>Toggle all additional widgets</td>
4218 <td>&nbsp;</td>
4219 <td>Hide and show all additional widgets like the
4220 notebook tabs, the toolbar, the messages window
4221 and the status bar.</td>
4222 </tr>
4223 <tr><td>Zoom In</td>
4224 <td>Ctrl-+  (C)</td>
4225 <td>Zooms in the text.</td>
4226 </tr>
4227 <tr><td>Zoom Out</td>
4228 <td>Ctrl--  (C)</td>
4229 <td>Zooms out the text.</td>
4230 </tr>
4231 <tr><td>Zoom Reset</td>
4232 <td>Ctrl-0</td>
4233 <td>Reset any previous zoom on the text.</td>
4234 </tr>
4235 </tbody>
4236 </table>
4237 </div>
4238 <div class="section" id="focus-keybindings">
4239 <h4><a class="toc-backref" href="#id168">Focus keybindings</a></h4>
4240 <table border="1" class="docutils">
4241 <colgroup>
4242 <col width="30%" />
4243 <col width="23%" />
4244 <col width="47%" />
4245 </colgroup>
4246 <thead valign="bottom">
4247 <tr><th class="head">Action</th>
4248 <th class="head">Default shortcut</th>
4249 <th class="head">Description</th>
4250 </tr>
4251 </thead>
4252 <tbody valign="top">
4253 <tr><td>Switch to Editor</td>
4254 <td>F2</td>
4255 <td>Switches to editor widget.
4256 Also reshows the document statistics line
4257 (after a short timeout).</td>
4258 </tr>
4259 <tr><td>Switch to Search Bar</td>
4260 <td>F7</td>
4261 <td>Switches to the search bar in the toolbar (if
4262 visible).</td>
4263 </tr>
4264 <tr><td>Switch to Message Window</td>
4265 <td>&nbsp;</td>
4266 <td>Focus the Message Window's current tab.</td>
4267 </tr>
4268 <tr><td>Switch to Compiler</td>
4269 <td>&nbsp;</td>
4270 <td>Focus the Compiler message window tab.</td>
4271 </tr>
4272 <tr><td>Switch to Messages</td>
4273 <td>&nbsp;</td>
4274 <td>Focus the Messages message window tab.</td>
4275 </tr>
4276 <tr><td>Switch to Scribble</td>
4277 <td>F6</td>
4278 <td>Switches to scribble widget.</td>
4279 </tr>
4280 <tr><td>Switch to VTE</td>
4281 <td>F4</td>
4282 <td>Switches to VTE widget.</td>
4283 </tr>
4284 <tr><td>Switch to Sidebar</td>
4285 <td>&nbsp;</td>
4286 <td>Focus the Sidebar.</td>
4287 </tr>
4288 <tr><td>Switch to Sidebar Symbol List</td>
4289 <td>&nbsp;</td>
4290 <td>Focus the Symbol list tab in the Sidebar
4291 (if visible).</td>
4292 </tr>
4293 <tr><td>Switch to Sidebar Document List</td>
4294 <td>&nbsp;</td>
4295 <td>Focus the Document list tab in the Sidebar
4296 (if visible).</td>
4297 </tr>
4298 </tbody>
4299 </table>
4300 </div>
4301 <div class="section" id="notebook-tab-keybindings">
4302 <h4><a class="toc-backref" href="#id169">Notebook tab keybindings</a></h4>
4303 <table border="1" class="docutils">
4304 <colgroup>
4305 <col width="28%" />
4306 <col width="23%" />
4307 <col width="49%" />
4308 </colgroup>
4309 <thead valign="bottom">
4310 <tr><th class="head">Action</th>
4311 <th class="head">Default shortcut</th>
4312 <th class="head">Description</th>
4313 </tr>
4314 </thead>
4315 <tbody valign="top">
4316 <tr><td>Switch to left document</td>
4317 <td>Ctrl-PageUp   (C)</td>
4318 <td>Switches to the previous open document.</td>
4319 </tr>
4320 <tr><td>Switch to right document</td>
4321 <td>Ctrl-PageDown (C)</td>
4322 <td>Switches to the next open document.</td>
4323 </tr>
4324 <tr><td>Switch to last used document</td>
4325 <td>Ctrl-Tab</td>
4326 <td>Switches to the previously shown document (if it's
4327 still open).
4328 Holding Ctrl (or another modifier if the keybinding
4329 has been changed) will show a dialog, then repeated
4330 presses of the keybinding will switch to the 2nd-last
4331 used document, 3rd-last, etc. Also known as
4332 Most-Recently-Used documents switching.</td>
4333 </tr>
4334 <tr><td>Move document left</td>
4335 <td>Alt-PageUp</td>
4336 <td>Changes the current document with the left hand
4337 one.</td>
4338 </tr>
4339 <tr><td>Move document right</td>
4340 <td>Alt-PageDown</td>
4341 <td>Changes the current document with the right hand
4342 one.</td>
4343 </tr>
4344 <tr><td>Move document first</td>
4345 <td>&nbsp;</td>
4346 <td>Moves the current document to the first position.</td>
4347 </tr>
4348 <tr><td>Move document last</td>
4349 <td>&nbsp;</td>
4350 <td>Moves the current document to the last position.</td>
4351 </tr>
4352 </tbody>
4353 </table>
4354 </div>
4355 <div class="section" id="document-keybindings">
4356 <h4><a class="toc-backref" href="#id170">Document keybindings</a></h4>
4357 <table border="1" class="docutils">
4358 <colgroup>
4359 <col width="33%" />
4360 <col width="19%" />
4361 <col width="48%" />
4362 </colgroup>
4363 <thead valign="bottom">
4364 <tr><th class="head">Action</th>
4365 <th class="head">Default shortcut</th>
4366 <th class="head">Description</th>
4367 </tr>
4368 </thead>
4369 <tbody valign="top">
4370 <tr><td>Replace tabs by space</td>
4371 <td>&nbsp;</td>
4372 <td>Replaces all tabs with the right amount of spaces.</td>
4373 </tr>
4374 <tr><td>Replace spaces by tabs</td>
4375 <td>&nbsp;</td>
4376 <td>Replaces all spaces with tab characters.</td>
4377 </tr>
4378 <tr><td>Toggle current fold</td>
4379 <td>&nbsp;</td>
4380 <td>Toggles the folding state of the current code block.</td>
4381 </tr>
4382 <tr><td>Fold all</td>
4383 <td>&nbsp;</td>
4384 <td>Folds all contractible code blocks.</td>
4385 </tr>
4386 <tr><td>Unfold all</td>
4387 <td>&nbsp;</td>
4388 <td>Unfolds all contracted code blocks.</td>
4389 </tr>
4390 <tr><td>Reload symbol list</td>
4391 <td>Ctrl-Shift-R</td>
4392 <td>Reloads the tag/symbol list.</td>
4393 </tr>
4394 <tr><td>Toggle Line wrapping</td>
4395 <td>&nbsp;</td>
4396 <td>Enables or disables wrapping of long lines.</td>
4397 </tr>
4398 <tr><td>Toggle Line breaking</td>
4399 <td>&nbsp;</td>
4400 <td>Enables or disables automatic breaking of long
4401 lines at a configurable column.</td>
4402 </tr>
4403 <tr><td>Remove Markers</td>
4404 <td>&nbsp;</td>
4405 <td>Remove any markers on lines or words which
4406 were set by using 'Mark All' in the
4407 search dialog or by manually marking lines.</td>
4408 </tr>
4409 <tr><td>Remove Error Indicators</td>
4410 <td>&nbsp;</td>
4411 <td>Remove any error indicators in the
4412 current document.</td>
4413 </tr>
4414 <tr><td>Remove Markers and Error Indicators</td>
4415 <td>&nbsp;</td>
4416 <td>Combines <tt class="docutils literal">Remove Markers</tt> and
4417 <tt class="docutils literal">Remove Error Indicators</tt>.</td>
4418 </tr>
4419 </tbody>
4420 </table>
4421 </div>
4422 <div class="section" id="build-keybindings">
4423 <h4><a class="toc-backref" href="#id171">Build keybindings</a></h4>
4424 <table border="1" class="docutils">
4425 <colgroup>
4426 <col width="29%" />
4427 <col width="24%" />
4428 <col width="47%" />
4429 </colgroup>
4430 <thead valign="bottom">
4431 <tr><th class="head">Action</th>
4432 <th class="head">Default shortcut</th>
4433 <th class="head">Description</th>
4434 </tr>
4435 </thead>
4436 <tbody valign="top">
4437 <tr><td>Compile</td>
4438 <td>F8</td>
4439 <td>Compiles the current file.</td>
4440 </tr>
4441 <tr><td>Build</td>
4442 <td>F9</td>
4443 <td>Builds (compiles if necessary and links) the
4444 current file.</td>
4445 </tr>
4446 <tr><td>Make all</td>
4447 <td>Shift-F9</td>
4448 <td>Builds the current file with the Make tool.</td>
4449 </tr>
4450 <tr><td>Make custom target</td>
4451 <td>Ctrl-Shift-F9</td>
4452 <td>Builds the current file with the Make tool and a
4453 given target.</td>
4454 </tr>
4455 <tr><td>Make object</td>
4456 <td>&nbsp;</td>
4457 <td>Compiles the current file with the Make tool.</td>
4458 </tr>
4459 <tr><td>Next error</td>
4460 <td>&nbsp;</td>
4461 <td>Jumps to the line with the next error from the
4462 last build process.</td>
4463 </tr>
4464 <tr><td>Previous error</td>
4465 <td>&nbsp;</td>
4466 <td>Jumps to the line with the previous error from
4467 the last build process.</td>
4468 </tr>
4469 <tr><td>Run</td>
4470 <td>F5</td>
4471 <td>Executes the current file in a terminal emulation.</td>
4472 </tr>
4473 <tr><td>Set Build Commands</td>
4474 <td>&nbsp;</td>
4475 <td>Opens the build commands dialog.</td>
4476 </tr>
4477 </tbody>
4478 </table>
4479 </div>
4480 <div class="section" id="tools-keybindings">
4481 <h4><a class="toc-backref" href="#id172">Tools keybindings</a></h4>
4482 <table border="1" class="docutils">
4483 <colgroup>
4484 <col width="29%" />
4485 <col width="24%" />
4486 <col width="47%" />
4487 </colgroup>
4488 <thead valign="bottom">
4489 <tr><th class="head">Action</th>
4490 <th class="head">Default shortcut</th>
4491 <th class="head">Description</th>
4492 </tr>
4493 </thead>
4494 <tbody valign="top">
4495 <tr><td>Show Color Chooser</td>
4496 <td>&nbsp;</td>
4497 <td>Opens the Color Chooser dialog.</td>
4498 </tr>
4499 </tbody>
4500 </table>
4501 </div>
4502 <div class="section" id="help-keybindings">
4503 <h4><a class="toc-backref" href="#id173">Help keybindings</a></h4>
4504 <table border="1" class="docutils">
4505 <colgroup>
4506 <col width="29%" />
4507 <col width="24%" />
4508 <col width="47%" />
4509 </colgroup>
4510 <thead valign="bottom">
4511 <tr><th class="head">Action</th>
4512 <th class="head">Default shortcut</th>
4513 <th class="head">Description</th>
4514 </tr>
4515 </thead>
4516 <tbody valign="top">
4517 <tr><td>Help</td>
4518 <td>F1 (C)</td>
4519 <td>Opens the manual.</td>
4520 </tr>
4521 </tbody>
4522 </table>
4523 </div>
4524 </div>
4525 </div>
4526 </div>
4527 <div class="section" id="configuration-files">
4528 <h1><a class="toc-backref" href="#id174">Configuration files</a></h1>
4529 <div class="warning">
4530 <p class="first admonition-title">Warning</p>
4531 <p class="last">You must use UTF-8 encoding <em>without BOM</em> for configuration files.</p>
4532 </div>
4533 <div class="section" id="configuration-file-paths">
4534 <h2><a class="toc-backref" href="#id175">Configuration file paths</a></h2>
4535 <p>Geany has default configuration files installed for the system and
4536 also per-user configuration files.</p>
4537 <p>The system files should not normally be edited because they will be
4538 overwritten when upgrading Geany.</p>
4539 <p>The user configuration directory can be overridden with the <tt class="docutils literal"><span class="pre">-c</span></tt>
4540 switch, but this is not normally done. See <a class="reference internal" href="#command-line-options">Command line options</a>.</p>
4541 <div class="note">
4542 <p class="first admonition-title">Note</p>
4543 <p class="last">Any missing subdirectories in the user configuration directory
4544 will be created when Geany starts.</p>
4545 </div>
4546 <p>You can check the paths Geany is using with <em>Help-&gt;Debug Messages</em>.
4547 Near the top there should be 2 lines with something like:</p>
4548 <pre class="literal-block">
4549 Geany-INFO: System data dir: /usr/share/geany
4550 Geany-INFO: User config dir: /home/username/.config/geany
4551 </pre>
4552 <div class="section" id="paths-on-unix-like-systems">
4553 <h3><a class="toc-backref" href="#id176">Paths on Unix-like systems</a></h3>
4554 <p>The system path is <tt class="docutils literal">$prefix/share/geany</tt>, where <tt class="docutils literal">$prefix</tt> is the
4555 path where Geany is installed (see <a class="reference internal" href="#installation-prefix">Installation prefix</a>).</p>
4556 <p>The user configuration directory is normally
4557 <tt class="docutils literal"><span class="pre">/home/username/.config/geany/</span></tt>.</p>
4558 </div>
4559 </div>
4560 <div class="section" id="tools-menu-items">
4561 <h2><a class="toc-backref" href="#id177">Tools menu items</a></h2>
4562 <p>There's a <em>Configuration files</em> submenu in the <em>Tools</em> menu that
4563 contains items for some of the available user configuration files.
4564 Clicking on one opens it in the editor for you to update. Geany will
4565 reload the file after you have saved it.</p>
4566 <div class="note">
4567 <p class="first admonition-title">Note</p>
4568 <p class="last">Other configuration files not shown here will need to be opened
4569 manually, and will not be automatically reloaded when saved.
4570 (see <em>Reload Configuration</em> below).</p>
4571 </div>
4572 <p>There's also a <em>Reload Configuration</em> item which can be used if you
4573 updated one of the other configuration files, or modified or added
4574 template files.</p>
4575 <p><em>Reload Configuration</em> is also necessary to update syntax highlighting colors.</p>
4576 <div class="note">
4577 <p class="first admonition-title">Note</p>
4578 <p class="last">Syntax highlighting colors aren't updated in open documents after
4579 saving filetypes.common as this may take a significant
4580 amount of time.</p>
4581 </div>
4582 </div>
4583 <div class="section" id="global-configuration-file">
4584 <h2><a class="toc-backref" href="#id178">Global configuration file</a></h2>
4585 <p>System administrators can add a global configuration file for Geany
4586 which will be used when starting Geany and a user configuration file
4587 does not exist.</p>
4588 <p>The global configuration file is read from <tt class="docutils literal">geany.conf</tt> in the
4589 system configuration path - see <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>. It can
4590 contain any settings which are found in the usual configuration file
4591 created by Geany, but does not have to contain all settings.</p>
4592 <div class="note">
4593 <p class="first admonition-title">Note</p>
4594 <p class="last">This feature is mainly intended for package maintainers or system
4595 admins who want to set up Geany in a multi user environment and
4596 set some sane default values for this environment. Usually users won't
4597 need to do that.</p>
4598 </div>
4599 </div>
4600 <div class="section" id="filetype-definition-files">
4601 <h2><a class="toc-backref" href="#id179">Filetype definition files</a></h2>
4602 <p>All color definitions and other filetype specific settings are
4603 stored in the filetype definition files. Those settings are colors
4604 for syntax highlighting, general settings like comment characters or
4605 word delimiter characters as well as compiler and linker settings.</p>
4606 <p>See also <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>.</p>
4607 <div class="section" id="filenames">
4608 <h3><a class="toc-backref" href="#id180">Filenames</a></h3>
4609 <p>Each filetype has a corresponding filetype definition file. The format
4610 for built-in filetype <cite>Foo</cite> is:</p>
4611 <pre class="literal-block">
4612 filetypes.foo
4613 </pre>
4614 <p>The extension is normally just the filetype name in lower case.</p>
4615 <p>However there are some exceptions:</p>
4616 <table border="1" class="docutils">
4617 <colgroup>
4618 <col width="63%" />
4619 <col width="38%" />
4620 </colgroup>
4621 <thead valign="bottom">
4622 <tr><th class="head">Filetype</th>
4623 <th class="head">Extension</th>
4624 </tr>
4625 </thead>
4626 <tbody valign="top">
4627 <tr><td>C++</td>
4628 <td>cpp</td>
4629 </tr>
4630 <tr><td>C#</td>
4631 <td>cs</td>
4632 </tr>
4633 <tr><td>Make</td>
4634 <td>makefile</td>
4635 </tr>
4636 <tr><td>Matlab/Octave</td>
4637 <td>matlab</td>
4638 </tr>
4639 </tbody>
4640 </table>
4641 <p>There is also the <a class="reference internal" href="#special-file-filetypes-common">special file filetypes.common</a>.</p>
4642 <p>For <a class="reference internal" href="#custom-filetypes">custom filetypes</a>, the filename for <cite>Foo</cite> is different:</p>
4643 <pre class="literal-block">
4644 filetypes.Foo.conf
4645 </pre>
4646 <p>See the link for details.</p>
4647 </div>
4648 <div class="section" id="system-files">
4649 <h3><a class="toc-backref" href="#id181">System files</a></h3>
4650 <p>The system-wide filetype configuration files can be found in the
4651 system configuration path and are called <tt class="docutils literal"><span class="pre">filetypes.$ext</span></tt>,
4652 where $ext is the name of the filetype. For every
4653 filetype there is a corresponding definition file. There is one
4654 exception: <tt class="docutils literal">filetypes.common</tt> -- this file is for general settings,
4655 which are not specific to a certain filetype.</p>
4656 <div class="warning">
4657 <p class="first admonition-title">Warning</p>
4658 <p class="last">It is not recommended that users edit the system-wide files,
4659 because they will be overridden when Geany is updated.</p>
4660 </div>
4661 </div>
4662 <div class="section" id="user-files">
4663 <h3><a class="toc-backref" href="#id182">User files</a></h3>
4664 <p>To change the settings, copy a file from the system configuration
4665 path to the subdirectory <tt class="docutils literal">filedefs</tt> in your user configuration
4666 directory. Then you can edit the file and the changes will still be
4667 available after an update of Geany.</p>
4668 <p>Alternatively, you can create the file yourself and add only the
4669 settings you want to change. All missing settings will be read from
4670 the corresponding system configuration file.</p>
4671 </div>
4672 <div class="section" id="custom-filetypes">
4673 <h3><a class="toc-backref" href="#id183">Custom filetypes</a></h3>
4674 <p>At startup Geany looks for <tt class="docutils literal"><span class="pre">filetypes.*.conf</span></tt> files in the system and
4675 user filetype paths, adding any filetypes found with the name matching
4676 the '<tt class="docutils literal">*</tt>' wildcard - e.g. <tt class="docutils literal">filetypes.Bar.conf</tt>.</p>
4677 <p>Custom filetypes are not as powerful as built-in filetypes, but
4678 support for the following has been implemented:</p>
4679 <ul>
4680 <li><p class="first">Recognizing and setting the filetype (after the user has manually edited
4681 <tt class="docutils literal">filetype_extensions.conf</tt>).</p>
4682 </li>
4683 <li><dl class="first docutils">
4684 <dt>Reading filetype settings in the <tt class="docutils literal">[settings]</tt> section, including:</dt>
4685 <dd><ul class="first last simple">
4686 <li>Using an existing syntax highlighting lexer (<a class="reference internal" href="#lexer-filetype">lexer_filetype</a> key).</li>
4687 <li>Using an existing tag parser (<tt class="docutils literal">tag_parser</tt> key).</li>
4688 </ul>
4689 </dd>
4690 </dl>
4691 </li>
4692 <li><p class="first">Build commands (<tt class="docutils literal"><span class="pre">[build-menu]</span></tt> section).</p>
4693 </li>
4694 <li><p class="first">Loading global tags files (sharing the <tt class="docutils literal">tag_parser</tt> namespace).</p>
4695 </li>
4696 </ul>
4697 <p>See <a class="reference internal" href="#filetype-configuration">Filetype configuration</a> for details on each setting.</p>
4698 <div class="section" id="creating-a-custom-filetype-from-an-existing-filetype">
4699 <h4><a class="toc-backref" href="#id184">Creating a custom filetype from an existing filetype</a></h4>
4700 <p>Because most filetype settings will relate to the syntax
4701 highlighting (e.g. styling, keywords, <tt class="docutils literal">lexer_properties</tt>
4702 sections), it is best to copy an existing filetype file that uses
4703 the lexer you wish to use as the basis of a custom filetype, using
4704 the correct filename extension format shown above, e.g.:</p>
4705 <pre class="literal-block">
4706 cp filetypes.foo filetypes.Bar.conf
4707 </pre>
4708 <p>Then add the <tt class="docutils literal">lexer_filetype=Foo</tt> setting (if not already present)
4709 and add/adjust other settings.</p>
4710 <div class="warning">
4711 <p class="first admonition-title">Warning</p>
4712 <p class="last">The <tt class="docutils literal">[styling]</tt> and <tt class="docutils literal">[keywords]</tt> sections have key names
4713 specific to each filetype/lexer. You must follow the same
4714 names - in particular, some lexers only support one keyword
4715 list, or none.</p>
4716 </div>
4717 </div>
4718 </div>
4719 <div class="section" id="filetype-configuration">
4720 <h3><a class="toc-backref" href="#id185">Filetype configuration</a></h3>
4721 <p>As well as the sections listed below, each filetype file can contain
4722 a [build-menu] section as described in <a class="reference internal" href="#build-menu-section">[build-menu] section</a>.</p>
4723 <div class="section" id="styling-section">
4724 <h4><a class="toc-backref" href="#id186">[styling] section</a></h4>
4725 <p>In this section the colors for syntax highlighting are defined. The
4726 manual format is:</p>
4727 <ul class="simple">
4728 <li><tt class="docutils literal">key=foreground_color;background_color;bold_flag;italic_flag</tt></li>
4729 </ul>
4730 <p>Colors have to be specified as RGB hex values prefixed by
4731 0x. For example red is 0xff0000, blue is 0x0000ff. The values are
4732 case-insensitive, but it is a good idea to use small letters. Bold
4733 and italic are flags and should only be &quot;true&quot; or &quot;false&quot;. If their
4734 value is something other than &quot;true&quot; or &quot;false&quot;, &quot;false&quot; is assumed.</p>
4735 <p>You can omit fields to use the values from the style named <tt class="docutils literal">&quot;default&quot;</tt>.</p>
4736 <p>E.g. <tt class="docutils literal"><span class="pre">key=0xff0000;;true</span></tt></p>
4737 <p>This makes the key style have red foreground text, default background
4738 color text and bold emphasis.</p>
4739 <div class="section" id="using-a-named-style">
4740 <h5><a class="toc-backref" href="#id187">Using a named style</a></h5>
4741 <p>The second format uses a <em>named style</em> name to reference a style
4742 defined in filetypes.common.</p>
4743 <ul class="simple">
4744 <li><tt class="docutils literal">key=named_style</tt></li>
4745 <li><tt class="docutils literal">key2=named_style2,bold,italic</tt></li>
4746 </ul>
4747 <p>The bold and italic parts are optional, and if present are used to
4748 toggle the bold or italic flags to the opposite of the named style's
4749 flags. In contrast to style definition booleans, they are a literal
4750 &quot;,bold,italic&quot; and commas are used instead of semi-colons.</p>
4751 <p>E.g. <tt class="docutils literal">key=comment,italic</tt></p>
4752 <p>This makes the key style match the <tt class="docutils literal">&quot;comment&quot;</tt> named style, but with
4753 italic emphasis.</p>
4754 <p>To define named styles, see the filetypes.common <a class="reference internal" href="#named-styles-section">[named_styles]
4755 Section</a>.</p>
4756 </div>
4757 <div class="section" id="reading-styles-from-another-filetype">
4758 <h5><a class="toc-backref" href="#id188">Reading styles from another filetype</a></h5>
4759 <p>You can automatically copy all of the styles from another filetype
4760 definition file by using the following syntax for the <tt class="docutils literal">[styling]</tt>
4761 group:</p>
4762 <pre class="literal-block">
4763 [styling=Foo]
4764 </pre>
4765 <p>Where Foo is a filetype name. The corresponding <tt class="docutils literal">[styling]</tt>
4766 section from <tt class="docutils literal">filetypes.foo</tt> will be read.</p>
4767 <p>This is useful when the same lexer is being used for multiple
4768 filetypes (e.g. C/C++/C#/Java/etc).  For example, to make the C++
4769 styling the same as the C styling, you would put the following in
4770 <tt class="docutils literal">filetypes.cpp</tt>:</p>
4771 <pre class="literal-block">
4772 [styling=C]
4773 </pre>
4774 </div>
4775 </div>
4776 <div class="section" id="keywords-section">
4777 <h4><a class="toc-backref" href="#id189">[keywords] section</a></h4>
4778 <p>This section contains keys for different keyword lists specific to
4779 the filetype. Some filetypes do not support keywords, so adding a
4780 new key will not work. You can only add or remove keywords to/from
4781 an existing list.</p>
4782 <div class="important">
4783 <p class="first admonition-title">Important</p>
4784 <p class="last">The keywords list must be in one line without line ending characters.</p>
4785 </div>
4786 </div>
4787 <div class="section" id="lexer-properties-section">
4788 <h4><a class="toc-backref" href="#id190">[lexer_properties] section</a></h4>
4789 <p>Here any special properties for the Scintilla lexer can be set in the
4790 format <tt class="docutils literal">key.name.field=some.value</tt>.</p>
4791 <p>Properties Geany uses are listed in the system filetype files. To find
4792 other properties you need Geany's source code:</p>
4793 <pre class="literal-block">
4794 egrep -o 'GetProperty\w*\(&quot;([^&quot;]+)&quot;[^)]+\)' scintilla/Lex*.cxx
4795 </pre>
4796 </div>
4797 <div class="section" id="settings-section">
4798 <h4><a class="toc-backref" href="#id191">[settings] section</a></h4>
4799 <dl class="docutils">
4800 <dt>extension</dt>
4801 <dd><p class="first">This is the default file extension used when saving files, not
4802 including the period character (<tt class="docutils literal">.</tt>). The extension used should
4803 match one of the patterns associated with that filetype (see
4804 <a class="reference internal" href="#filetype-extensions">Filetype extensions</a>).</p>
4805 <p class="last"><em>Example:</em> <tt class="docutils literal">extension=cxx</tt></p>
4806 </dd>
4807 <dt>wordchars</dt>
4808 <dd><p class="first">These characters define word boundaries when making selections
4809 and searching using word matching options.</p>
4810 <p><em>Example:</em> (look at system filetypes.* files)</p>
4811 <div class="note last">
4812 <p class="first admonition-title">Note</p>
4813 <p class="last">This can be overridden by the <em>whitespace_chars</em>
4814 filetypes.common setting.</p>
4815 </div>
4816 </dd>
4817 <dt>comment_single</dt>
4818 <dd><p class="first">A character or string which is used to comment code. If you want to use
4819 multiline comments only, don't set this but rather comment_open and
4820 comment_close.</p>
4821 <p>Single-line comments are used in priority over multiline comments to
4822 comment a line, e.g. with the <cite>Comment/Uncomment line</cite> command.</p>
4823 <p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">comment_single=//</span></tt></p>
4824 </dd>
4825 <dt>comment_open</dt>
4826 <dd><p class="first">A character or string which is used to comment code. You need to also
4827 set comment_close to really use multiline comments. If you want to use
4828 single-line comments, prefer setting comment_single.</p>
4829 <p>Multiline comments are used in priority over single-line comments to
4830 comment a block, e.g. template comments.</p>
4831 <p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">comment_open=/*</span></tt></p>
4832 </dd>
4833 <dt>comment_close</dt>
4834 <dd><p class="first">If multiline comments are used, this is the character or string to
4835 close the comment.</p>
4836 <p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">comment_close=*/</span></tt></p>
4837 </dd>
4838 <dt>comment_use_indent</dt>
4839 <dd><p class="first">Set this to false if a comment character or string should start at
4840 column 0 of a line. If set to true it uses any indentation of the
4841 line.</p>
4842 <p>Note: Comment indentation</p>
4843 <p><tt class="docutils literal">comment_use_indent=true</tt> would generate this if a line is
4844 commented (e.g. with Ctrl-D):</p>
4845 <pre class="literal-block">
4846 #command_example();
4847 </pre>
4848 <p><tt class="docutils literal">comment_use_indent=false</tt> would generate this if a line is
4849 commented (e.g. with Ctrl-D):</p>
4850 <pre class="literal-block">
4851 #   command_example();
4852 </pre>
4853 <p>Note: This setting only works for single line comments (like '//',
4854 '#' or ';').</p>
4855 <p class="last"><em>Example:</em> <tt class="docutils literal">comment_use_indent=true</tt></p>
4856 </dd>
4857 <dt>context_action_cmd</dt>
4858 <dd><p class="first">A command which can be executed on the current word or the current
4859 selection.</p>
4860 <p>Example usage: Open the API documentation for the
4861 current function call at the cursor position.</p>
4862 <p>The command can
4863 be set for every filetype or if not set, a global command will
4864 be used. The command itself can be specified without the full
4865 path, then it is searched in $PATH. But for security reasons,
4866 it is recommended to specify the full path to the command. The
4867 wildcard %s will be replaced by the current word at the cursor
4868 position or by the current selection.</p>
4869 <p>Hint: for PHP files the following could be quite useful:
4870 context_action_cmd=firefox &quot;<a class="reference external" href="http://www.php.net/%s">http://www.php.net/%s</a>&quot;</p>
4871 <p class="last"><em>Example:</em> <tt class="docutils literal">context_action_cmd=devhelp <span class="pre">-s</span> &quot;%s&quot;</tt></p>
4872 </dd>
4873 <dt>tag_parser</dt>
4874 <dd>The TagManager language name, e.g. &quot;C&quot;. Usually the same as the
4875 filetype name.</dd>
4876 </dl>
4877 <dl class="docutils" id="lexer-filetype">
4878 <dt>lexer_filetype</dt>
4879 <dd><p class="first">A filetype name to setup syntax highlighting from another filetype.
4880 This must not be recursive, i.e. it should be a filetype name that
4881 doesn't use the <em>lexer_filetype</em> key itself, e.g.:</p>
4882 <pre class="literal-block">
4883 lexer_filetype=C
4884 #lexer_filetype=C++
4885 </pre>
4886 <p class="last">The second line is wrong, because <tt class="docutils literal">filetypes.cpp</tt> itself uses
4887 <tt class="docutils literal">lexer_filetype=C</tt>, which would be recursive.</p>
4888 </dd>
4889 <dt>symbol_list_sort_mode</dt>
4890 <dd><p class="first">What the default symbol list sort order should be.</p>
4891 <table border="1" class="last docutils">
4892 <colgroup>
4893 <col width="12%" />
4894 <col width="88%" />
4895 </colgroup>
4896 <thead valign="bottom">
4897 <tr><th class="head">Value</th>
4898 <th class="head">Meaning</th>
4899 </tr>
4900 </thead>
4901 <tbody valign="top">
4902 <tr><td>0</td>
4903 <td>Sort tags by name</td>
4904 </tr>
4905 <tr><td>1</td>
4906 <td>Sort tags by appearance (line number)</td>
4907 </tr>
4908 </tbody>
4909 </table>
4910 </dd>
4911 </dl>
4912 <dl class="docutils" id="xml-indent-tags">
4913 <dt>xml_indent_tags</dt>
4914 <dd>If this setting is set to <em>true</em>, a new line after a line ending with an
4915 unclosed XML/HTML tag will be automatically indented. This only applies
4916 to filetypes for which the HTML or XML lexer is used. Such filetypes have
4917 this setting in their system configuration files.</dd>
4918 </dl>
4919 </div>
4920 <div class="section" id="indentation-section">
4921 <h4><a class="toc-backref" href="#id192">[indentation] section</a></h4>
4922 <p>This section allows definition of default indentation settings specific to
4923 the file type, overriding the ones configured in the preferences.  This can
4924 be useful for file types requiring specific indentation settings (e.g. tabs
4925 only for Makefile).  These settings don't override auto-detection if activated.</p>
4926 <dl class="docutils">
4927 <dt>width</dt>
4928 <dd>The forced indentation width.</dd>
4929 <dt>type</dt>
4930 <dd><p class="first">The forced indentation type.</p>
4931 <table border="1" class="last docutils">
4932 <colgroup>
4933 <col width="18%" />
4934 <col width="82%" />
4935 </colgroup>
4936 <thead valign="bottom">
4937 <tr><th class="head">Value</th>
4938 <th class="head">Indentation type</th>
4939 </tr>
4940 </thead>
4941 <tbody valign="top">
4942 <tr><td>0</td>
4943 <td>Spaces only</td>
4944 </tr>
4945 <tr><td>1</td>
4946 <td>Tabs only</td>
4947 </tr>
4948 <tr><td>2</td>
4949 <td>Mixed (tabs and spaces)</td>
4950 </tr>
4951 </tbody>
4952 </table>
4953 </dd>
4954 </dl>
4955 </div>
4956 <div class="section" id="build-settings-section">
4957 <h4><a class="toc-backref" href="#id193">[build_settings] section</a></h4>
4958 <p>As of Geany 0.19 this section is supplemented by the <a class="reference internal" href="#build-menu-section">[build-menu] section</a>.
4959 Values that are set in the [build-menu] section will override those in this section.</p>
4960 <dl class="docutils">
4961 <dt>error_regex</dt>
4962 <dd><p class="first">This is a GNU-style extended regular expression to parse a filename
4963 and line number from build output. If undefined, Geany will fall
4964 back to its default error message parsing.</p>
4965 <p>Only the first two matches will be read by Geany. Geany will look for
4966 a match that is purely digits, and use this for the line number. The
4967 remaining match will be used as the filename.</p>
4968 <p><em>Example:</em> <tt class="docutils literal"><span class="pre">error_regex=(.+):([0-9]+):[0-9]+</span></tt></p>
4969 <p class="last">This will parse a message such as:
4970 <tt class="docutils literal">test.py:7:24: E202 whitespace before ']'</tt></p>
4971 </dd>
4972 </dl>
4973 <p><strong>Build commands</strong></p>
4974 <p>If any build menu item settings have been configured in the Build Menu Commands
4975 dialog or the Build tab of the project preferences dialog then these
4976 settings are stored in the [build-menu] section and override the settings in
4977 this section for that item.</p>
4978 <dl class="docutils">
4979 <dt>compiler</dt>
4980 <dd><p class="first">This item specifies the command to compile source code files. But
4981 it is also possible to use it with interpreted languages like Perl
4982 or Python. With these filetypes you can use this option as a kind of
4983 syntax parser, which sends output to the compiler message window.</p>
4984 <p>You should quote the filename to also support filenames with
4985 spaces. The following wildcards for filenames are available:</p>
4986 <ul class="simple">
4987 <li>%f -- complete filename without path</li>
4988 <li>%e -- filename without path and without extension</li>
4989 </ul>
4990 <p class="last"><em>Example:</em> <tt class="docutils literal">compiler=gcc <span class="pre">-Wall</span> <span class="pre">-c</span> &quot;%f&quot;</tt></p>
4991 </dd>
4992 <dt>linker</dt>
4993 <dd><p class="first">This item specifies the command to link the file. If the file is not
4994 already compiled, it will be compiled while linking. The -o option
4995 is automatically added by Geany. This item works well with GNU gcc,
4996 but may be problematic with other compilers (esp. with the linker).</p>
4997 <p class="last"><em>Example:</em> <tt class="docutils literal">linker=gcc <span class="pre">-Wall</span> &quot;%f&quot;</tt></p>
4998 </dd>
4999 <dt>run_cmd</dt>
5000 <dd><p class="first">Use this item to execute your file. It has to have been built
5001 already. Use the %e wildcard to have only the name of the executable
5002 (i.e. without extension) or use the %f wildcard if you need the
5003 complete filename, e.g. for shell scripts.</p>
5004 <p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">run_cmd=&quot;./%e&quot;</span></tt></p>
5005 </dd>
5006 </dl>
5007 </div>
5008 </div>
5009 <div class="section" id="special-file-filetypes-common">
5010 <h3><a class="toc-backref" href="#id194">Special file filetypes.common</a></h3>
5011 <p>There is a special filetype definition file called
5012 filetypes.common. This file defines some general non-filetype-specific
5013 settings.</p>
5014 <p>You can open the user filetypes.common with the
5015 <em>Tools-&gt;Configuration Files-&gt;filetypes.common</em> menu item. This adds
5016 the default settings to the user file if the file doesn't exist.
5017 Alternatively the file can be created manually, adding only the
5018 settings you want to change. All missing settings will be read from
5019 the system file.</p>
5020 <div class="note">
5021 <p class="first admonition-title">Note</p>
5022 <p class="last">See the <a class="reference internal" href="#filetype-configuration">Filetype configuration</a> section for how to define styles.</p>
5023 </div>
5024 <div class="section" id="named-styles-section">
5025 <h4><a class="toc-backref" href="#id195">[named_styles] section</a></h4>
5026 <p>Named styles declared here can be used in the [styling] section of any
5027 filetypes.* file.</p>
5028 <p>For example:</p>
5029 <p><em>In filetypes.common</em>:</p>
5030 <pre class="literal-block">
5031 [named_styles]
5032 foo=0xc00000;0xffffff;false;true
5033 bar=foo
5034 </pre>
5035 <p><em>In filetypes.c</em>:</p>
5036 <pre class="literal-block">
5037 [styling]
5038 comment=foo
5039 </pre>
5040 <p>This saves copying and pasting the whole style definition into several
5041 different files.</p>
5042 <div class="note">
5043 <p class="first admonition-title">Note</p>
5044 <p class="last">You can define aliases for named styles, as shown with the <tt class="docutils literal">bar</tt>
5045 entry in the above example, but they must be declared after the
5046 original style.</p>
5047 </div>
5048 <p>This section can be overridden with color scheme files - see the <a class="reference internal" href="#color-schemes-menu">Color
5049 schemes menu</a>.</p>
5050 </div>
5051 <div class="section" id="id4">
5052 <h4><a class="toc-backref" href="#id196">[styling] section</a></h4>
5053 <dl class="docutils">
5054 <dt>default</dt>
5055 <dd><p class="first">This is the default style. It is used for styling files without a
5056 filetype set.</p>
5057 <p class="last"><em>Example:</em> <tt class="docutils literal">default=0x000000;0xffffff;false;false</tt></p>
5058 </dd>
5059 <dt>selection</dt>
5060 <dd><p class="first">The style for coloring selected text. The format is:</p>
5061 <ul class="simple">
5062 <li>Foreground color</li>
5063 <li>Background color</li>
5064 <li>Use foreground color</li>
5065 <li>Use background color</li>
5066 </ul>
5067 <p>The colors are only set if the 3rd or 4th argument is true. When
5068 the colors are not overridden, the default is a dark grey
5069 background with syntax highlighted foreground text.</p>
5070 <p class="last"><em>Example:</em> <tt class="docutils literal">selection=0xc0c0c0;0x00007F;true;true</tt></p>
5071 </dd>
5072 <dt>brace_good</dt>
5073 <dd><p class="first">The style for brace highlighting when a matching brace was found.</p>
5074 <p class="last"><em>Example:</em> <tt class="docutils literal">brace_good=0xff0000;0xFFFFFF;true;false</tt></p>
5075 </dd>
5076 <dt>brace_bad</dt>
5077 <dd><p class="first">The style for brace highlighting when no matching brace was found.</p>
5078 <p class="last"><em>Example:</em> <tt class="docutils literal">brace_bad=0x0000ff;0xFFFFFF;true;false</tt></p>
5079 </dd>
5080 <dt>caret</dt>
5081 <dd><p class="first">The style for coloring the caret(the blinking cursor). Only first
5082 and third argument is interpreted.
5083 Set the third argument to true to change the caret into a block caret.</p>
5084 <p class="last"><em>Example:</em> <tt class="docutils literal">caret=0x000000;0x0;false;false</tt></p>
5085 </dd>
5086 <dt>caret_width</dt>
5087 <dd><p class="first">The width for the caret(the blinking cursor). Only the first
5088 argument is interpreted. The width is specified in pixels with
5089 a maximum of three pixel. Use the width 0 to make the caret
5090 invisible.</p>
5091 <p class="last"><em>Example:</em> <tt class="docutils literal">caret=1;0;false;false</tt></p>
5092 </dd>
5093 <dt>current_line</dt>
5094 <dd><p class="first">The style for coloring the background of the current line. Only
5095 the second and third arguments are interpreted. The second argument
5096 is the background color. Use the third argument to enable or
5097 disable background highlighting for the current line (has to be
5098 true/false).</p>
5099 <p class="last"><em>Example:</em> <tt class="docutils literal">current_line=0x0;0xe5e5e5;true;false</tt></p>
5100 </dd>
5101 <dt>indent_guide</dt>
5102 <dd><p class="first">The style for coloring the indentation guides. Only the first and
5103 second arguments are interpreted.</p>
5104 <p class="last"><em>Example:</em> <tt class="docutils literal">indent_guide=0xc0c0c0;0xffffff;false;false</tt></p>
5105 </dd>
5106 <dt>white_space</dt>
5107 <dd><p class="first">The style for coloring the white space if it is shown. The first
5108 both arguments define the foreground and background colors, the
5109 third argument sets whether to use the defined foreground color
5110 or to use the color defined by each filetype for the white space.
5111 The fourth argument defines whether to use the background color.</p>
5112 <p class="last"><em>Example:</em> <tt class="docutils literal">white_space=0xc0c0c0;0xffffff;true;true</tt></p>
5113 </dd>
5114 <dt>margin_linenumber</dt>
5115 <dd>Line number margin foreground and background colors.</dd>
5116 </dl>
5117 <dl class="docutils" id="folding-settings">
5118 <dt>margin_folding</dt>
5119 <dd>Fold margin foreground and background colors.</dd>
5120 <dt>fold_symbol_highlight</dt>
5121 <dd>Highlight color of folding symbols.</dd>
5122 <dt>folding_style</dt>
5123 <dd><p class="first">The style of folding icons. Only first and second arguments are
5124 used.</p>
5125 <p>Valid values for the first argument are:</p>
5126 <ul class="simple">
5127 <li>1 -- for boxes</li>
5128 <li>2 -- for circles</li>
5129 <li>3 -- for arrows</li>
5130 <li>4 -- for +/-</li>
5131 </ul>
5132 <p>Valid values for the second argument are:</p>
5133 <ul class="simple">
5134 <li>0 -- for no lines</li>
5135 <li>1 -- for straight lines</li>
5136 <li>2 -- for curved lines</li>
5137 </ul>
5138 <p><em>Default:</em> <tt class="docutils literal">folding_style=1;1;</tt></p>
5139 <p class="last"><em>Arrows:</em> <tt class="docutils literal">folding_style=3;0;</tt></p>
5140 </dd>
5141 <dt>folding_horiz_line</dt>
5142 <dd><p class="first">Draw a thin horizontal line at the line where text is folded. Only
5143 first argument is used.</p>
5144 <p>Valid values for the first argument are:</p>
5145 <ul class="simple">
5146 <li>0 -- disable, do not draw a line</li>
5147 <li>1 -- draw the line above folded text</li>
5148 <li>2 -- draw the line below folded text</li>
5149 </ul>
5150 <p class="last"><em>Example:</em> <tt class="docutils literal">folding_horiz_line=0;0;false;false</tt></p>
5151 </dd>
5152 <dt>line_wrap_visuals</dt>
5153 <dd><p class="first">First argument: drawing of visual flags to indicate a line is wrapped.
5154 This is a bitmask of the values:</p>
5155 <ul class="simple">
5156 <li>0 -- No visual flags</li>
5157 <li>1 -- Visual flag at end of subline of a wrapped line</li>
5158 <li>2 -- Visual flag at begin of subline of a wrapped line. Subline is
5159 indented by at least 1 to make room for the flag.</li>
5160 </ul>
5161 <p>Second argument: wether the visual flags to indicate a line is wrapped
5162 are drawn near the border or near the text. This is a bitmask of the values:</p>
5163 <ul class="simple">
5164 <li>0 -- Visual flags drawn near border</li>
5165 <li>1 -- Visual flag at end of subline drawn near text</li>
5166 <li>2 -- Visual flag at begin of subline drawn near text</li>
5167 </ul>
5168 <p>Only first and second arguments are interpreted.</p>
5169 <p class="last"><em>Example:</em> <tt class="docutils literal">line_wrap_visuals=3;0;false;false</tt></p>
5170 </dd>
5171 <dt>line_wrap_indent</dt>
5172 <dd><p class="first">First argument: sets the size of indentation of sublines for wrapped lines
5173 in terms of the width of a space, only used when the second argument is <tt class="docutils literal">0</tt>.</p>
5174 <p>Second argument: wrapped sublines can be indented to the position of their
5175 first subline or one more indent level. Possible values:</p>
5176 <ul class="simple">
5177 <li>0 - Wrapped sublines aligned to left of window plus amount set by the first argument</li>
5178 <li>1 - Wrapped sublines are aligned to first subline indent (use the same indentation)</li>
5179 <li>2 - Wrapped sublines are aligned to first subline indent plus one more level of indentation</li>
5180 </ul>
5181 <p>Only first and second arguments are interpreted.</p>
5182 <p class="last"><em>Example:</em> <tt class="docutils literal">line_wrap_indent=0;1;false;false</tt></p>
5183 </dd>
5184 <dt>translucency</dt>
5185 <dd><p class="first">Translucency for the current line (first argument) and the selection
5186 (second argument). Values between 0 and 256 are accepted.</p>
5187 <p>Note for Windows 95, 98 and ME users:
5188 keep this value at 256 to disable translucency otherwise Geany might crash.</p>
5189 <p>Only the first and second arguments are interpreted.</p>
5190 <p class="last"><em>Example:</em> <tt class="docutils literal">translucency=256;256;false;false</tt></p>
5191 </dd>
5192 <dt>marker_line</dt>
5193 <dd><p class="first">The style for a highlighted line (e.g when using Goto line or goto tag).
5194 The foreground color (first argument) is only used when the Markers margin
5195 is enabled (see View menu).</p>
5196 <p>Only the first and second arguments are interpreted.</p>
5197 <p class="last"><em>Example:</em> <tt class="docutils literal">marker_line=0x000000;0xffff00;false;false</tt></p>
5198 </dd>
5199 <dt>marker_search</dt>
5200 <dd><p class="first">The style for a marked search results (when using &quot;Mark&quot; in Search dialogs).
5201 The second argument sets the background colour for the drawn rectangle.</p>
5202 <p>Only the second argument is interpreted.</p>
5203 <p class="last"><em>Example:</em> <tt class="docutils literal">marker_search=0x000000;0xb8f4b8;false;false</tt></p>
5204 </dd>
5205 <dt>marker_mark</dt>
5206 <dd><p class="first">The style for a marked line (e.g when using the &quot;Toggle Marker&quot; keybinding
5207 (Ctrl-M)). The foreground color (first argument) is only used
5208 when the Markers margin is enabled (see View menu).</p>
5209 <p>Only the first and second arguments are interpreted.</p>
5210 <p class="last"><em>Example:</em> <tt class="docutils literal">marker_mark=0x000000;0xb8f4b8;false;false</tt></p>
5211 </dd>
5212 <dt>marker_translucency</dt>
5213 <dd><p class="first">Translucency for the line marker (first argument) and the search marker
5214 (second argument). Values between 0 and 256 are accepted.</p>
5215 <p>Note for Windows 95, 98 and ME users:
5216 keep this value at 256 to disable translucency otherwise Geany might crash.</p>
5217 <p>Only the first and second arguments are interpreted.</p>
5218 <p class="last"><em>Example:</em> <tt class="docutils literal">marker_translucency=256;256;false;false</tt></p>
5219 </dd>
5220 <dt>line_height</dt>
5221 <dd><p class="first">Amount of space to be drawn above and below the line's baseline.
5222 The first argument defines the amount of space to be drawn above the line, the second
5223 argument defines the amount of space to be drawn below.</p>
5224 <p>Only the first and second arguments are interpreted.</p>
5225 <p class="last"><em>Example:</em> <tt class="docutils literal">line_height=0;0;false;false</tt></p>
5226 </dd>
5227 <dt>calltips</dt>
5228 <dd><p class="first">The style for coloring the calltips. The first two arguments
5229 define the foreground and background colors, the third and fourth
5230 arguments set whether to use the defined colors.</p>
5231 <p class="last"><em>Example:</em> <tt class="docutils literal">calltips=0xc0c0c0;0xffffff;false;false</tt></p>
5232 </dd>
5233 </dl>
5234 </div>
5235 <div class="section" id="id5">
5236 <h4><a class="toc-backref" href="#id197">[settings] section</a></h4>
5237 <dl class="docutils">
5238 <dt>whitespace_chars</dt>
5239 <dd><p class="first">Characters to treat as whitespace. These characters are ignored
5240 when moving, selecting and deleting across word boundaries
5241 (see <a class="reference internal" href="#scintilla-keyboard-commands">Scintilla keyboard commands</a>).</p>
5242 <p>This should include space (\s) and tab (\t).</p>
5243 <p class="last"><em>Example:</em> <tt class="docutils literal"><span class="pre">whitespace_chars=\s\t!\&quot;#$%&amp;'()*+,-./:;&lt;=&gt;?&#64;[\\]^`{|}~</span></tt></p>
5244 </dd>
5245 </dl>
5246 </div>
5247 </div>
5248 </div>
5249 <div class="section" id="filetype-extensions">
5250 <h2><a class="toc-backref" href="#id198">Filetype extensions</a></h2>
5251 <p>To change the default filetype extension used when saving a new file,
5252 see <a class="reference internal" href="#filetype-definition-files">Filetype definition files</a>.</p>
5253 <p>You can override the list of file extensions that Geany uses to detect
5254 filetypes using the user <tt class="docutils literal">filetype_extensions.conf</tt> file. Use the
5255 <em>Tools-&gt;Configuration Files-&gt;filetype_extensions.conf</em> menu item. See
5256 also <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>.</p>
5257 <p>You should only list lines for filetype extensions that you want to
5258 override in the user configuration file and remove or comment out
5259 others. The patterns are listed after the <tt class="docutils literal">=</tt> sign, using a
5260 semi-colon separated list of patterns which should be matched for
5261 that filetype.</p>
5262 <p>For example, to override the filetype extensions for Make, the file
5263 should look like:</p>
5264 <pre class="literal-block">
5265 [Extensions]
5266 Make=Makefile*;*.mk;Buildfile;
5267 </pre>
5268 </div>
5269 <div class="section" id="filetype-group-membership">
5270 <h2><a class="toc-backref" href="#id199">Filetype group membership</a></h2>
5271 <p>Group membership is also stored in <tt class="docutils literal">filetype_extensions.conf</tt>. This
5272 file is used to store information Geany needs at startup, whereas the
5273 separate filetype definition files hold information only needed when
5274 a document with their filetype is used.</p>
5275 <p>The format looks like:</p>
5276 <pre class="literal-block">
5277 [Groups]
5278 Programming=C;C++;
5279 Script=Perl;Python;
5280 Markup=HTML;XML;
5281 Misc=Diff;Conf;
5282 None=None;
5283 </pre>
5284 <p>The key names cannot be configured.</p>
5285 <div class="note">
5286 <p class="first admonition-title">Note</p>
5287 <p class="last">Group membership is only read at startup.</p>
5288 </div>
5289 </div>
5290 <div class="section" id="preferences-file-format">
5291 <h2><a class="toc-backref" href="#id200">Preferences file format</a></h2>
5292 <p>The user preferences file <tt class="docutils literal">geany.conf</tt> holds settings for all the items configured
5293 in the preferences dialog. This file should not be edited while Geany is running
5294 as the file will be overwritten when the preferences in Geany are changed or Geany
5295 is quit.</p>
5296 <div class="section" id="build-menu-section">
5297 <h3><a class="toc-backref" href="#id201">[build-menu] section</a></h3>
5298 <p>The [build-menu] section contains the configuration of the build menu.
5299 This section can occur in filetype, preferences and project files and
5300 always has the format described here.  Different menu items are loaded
5301 from different files, see the table in the <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a>
5302 section for details.  All the settings can be configured from the dialogs
5303 except the execute command in filetype files and filetype definitions in
5304 the project file, so these are the only ones which need hand editing.</p>
5305 <p>The build-menu section stores one entry for each setting for each menu item that
5306 is configured.  The keys for these settings have the format:</p>
5307 <blockquote>
5308 <tt class="docutils literal">GG_NN_FF</tt></blockquote>
5309 <p>where:</p>
5310 <ul class="simple">
5311 <li>GG - is the menu item group,<ul>
5312 <li>FT for filetype</li>
5313 <li>NF for independent (non-filetype)</li>
5314 <li>EX for execute</li>
5315 </ul>
5316 </li>
5317 <li>NN - is a two decimal digit number of the item within the group,
5318 starting at 00</li>
5319 <li>FF - is the field,<ul>
5320 <li>LB for label</li>
5321 <li>CM for command</li>
5322 <li>WD for working directory</li>
5323 </ul>
5324 </li>
5325 </ul>
5326 </div>
5327 </div>
5328 <div class="section" id="project-file-format">
5329 <h2><a class="toc-backref" href="#id202">Project file format</a></h2>
5330 <p>The project file contains project related settings and possibly a
5331 record of the current session files.</p>
5332 <div class="section" id="build-menu-additions">
5333 <h3><a class="toc-backref" href="#id203">[build-menu] additions</a></h3>
5334 <p>The project file also can have extra fields in the [build-menu] section
5335 in addition to those listed in <a class="reference internal" href="#build-menu-section">[build-menu] section</a> above.</p>
5336 <p>When filetype menu items are configured for the project they are stored
5337 in the project file.</p>
5338 <p>The <tt class="docutils literal">filetypes</tt> entry is a list of the filetypes which exist in the
5339 project file.</p>
5340 <p>For each filetype the entries for that filetype have the format defined in
5341 <a class="reference internal" href="#build-menu-section">[build-menu] section</a> but the key is prefixed by the name of the filetype
5342 as it appears in the <tt class="docutils literal">filetypes</tt> entry, eg the entry for the label of
5343 filetype menu item 0 for the C filetype would be</p>
5344 <blockquote>
5345 <tt class="docutils literal">CFT_00_LB=Label</tt></blockquote>
5346 </div>
5347 </div>
5348 <div class="section" id="templates">
5349 <h2><a class="toc-backref" href="#id204">Templates</a></h2>
5350 <p>Geany supports the following templates:</p>
5351 <ul class="simple">
5352 <li>ChangeLog entry</li>
5353 <li>File header</li>
5354 <li>Function description</li>
5355 <li>Short GPL notice</li>
5356 <li>Short BSD notice</li>
5357 <li>File templates</li>
5358 </ul>
5359 <p>To use these templates, just open the Edit menu or open the popup menu
5360 by right-clicking in the editor widget, and choose &quot;Insert Comments&quot;
5361 and insert templates as you want.</p>
5362 <p>Some templates (like File header or ChangeLog entry) will always be
5363 inserted at the top of the file.</p>
5364 <p>To insert a function description, the cursor must be inside
5365 of the function, so that the function name can be determined
5366 automatically. The description will be positioned correctly one line
5367 above the function, just check it out. If the cursor is not inside
5368 of a function or the function name cannot be determined, the inserted
5369 function description won't contain the correct function name but &quot;unknown&quot;
5370 instead.</p>
5371 <div class="note">
5372 <p class="first admonition-title">Note</p>
5373 <p class="last">Geany automatically reloads template information when it notices you
5374 save a file in the user's template configuration directory. You can
5375 also force this by selecting <em>Tools-&gt;Reload Configuration</em>.</p>
5376 </div>
5377 <div class="section" id="template-meta-data">
5378 <h3><a class="toc-backref" href="#id205">Template meta data</a></h3>
5379 <p>Meta data can be used with all templates, but by default user set
5380 meta data is only used for the ChangeLog and File header templates.</p>
5381 <p>In the configuration dialog you can find a tab &quot;Templates&quot; (see
5382 <a class="reference internal" href="#template-preferences">Template preferences</a>). You can define the default values
5383 which will be inserted in the templates.</p>
5384 </div>
5385 <div class="section" id="file-templates">
5386 <h3><a class="toc-backref" href="#id206">File templates</a></h3>
5387 <p>File templates are templates used as the basis of a new file. To
5388 use them, choose the <em>New (with Template)</em> menu item from the <em>File</em>
5389 menu.</p>
5390 <p>By default, file templates are installed for some filetypes. Custom
5391 file templates can be added by creating the appropriate template file. You can
5392 also edit the default file templates.</p>
5393 <p>The file's contents are just the text to place in the document, with
5394 optional template wildcards like <tt class="docutils literal">{fileheader}</tt>. The fileheader
5395 wildcard can be placed anywhere, but it's usually put on the first
5396 line of the file, followed by a blank line.</p>
5397 <div class="section" id="adding-file-templates">
5398 <h4><a class="toc-backref" href="#id207">Adding file templates</a></h4>
5399 <p>File templates are read from <tt class="docutils literal">templates/files</tt> under the
5400 <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>.</p>
5401 <p>The filetype to use is detected from the template file's extension, if
5402 any. For example, creating a file <tt class="docutils literal">module.c</tt> would add a menu item
5403 which created a new document with the filetype set to 'C'.</p>
5404 <p>The template file is read from disk when the corresponding menu item is
5405 clicked.</p>
5406 </div>
5407 </div>
5408 <div class="section" id="customizing-templates">
5409 <h3><a class="toc-backref" href="#id208">Customizing templates</a></h3>
5410 <p>Each template can be customized to your needs. The templates are
5411 stored in the <tt class="docutils literal"><span class="pre">~/.config/geany/templates/</span></tt> directory (see the section called
5412 <a class="reference internal" href="#command-line-options">Command line options</a> for further information about the configuration
5413 directory). Just open the desired template with an editor (ideally,
5414 Geany ;-) ) and edit the template to your needs. There are some
5415 wildcards which will be automatically replaced by Geany at startup.</p>
5416 <div class="section" id="template-wildcards">
5417 <h4><a class="toc-backref" href="#id209">Template wildcards</a></h4>
5418 <p>All wildcards must be enclosed by &quot;{&quot; and &quot;}&quot;, e.g. {date}.</p>
5419 <p><strong>Wildcards for character escaping</strong></p>
5420 <table border="1" class="docutils">
5421 <colgroup>
5422 <col width="14%" />
5423 <col width="46%" />
5424 <col width="40%" />
5425 </colgroup>
5426 <thead valign="bottom">
5427 <tr><th class="head">Wildcard</th>
5428 <th class="head">Description</th>
5429 <th class="head">Available in</th>
5430 </tr>
5431 </thead>
5432 <tbody valign="top">
5433 <tr><td>ob</td>
5434 <td>{ Opening Brace (used to prevent other
5435 wildcards being expanded).</td>
5436 <td>file templates, file header, snippets.</td>
5437 </tr>
5438 <tr><td>cb</td>
5439 <td>} Closing Brace.</td>
5440 <td>file templates, file header, snippets.</td>
5441 </tr>
5442 <tr><td>pc</td>
5443 <td>% Percent (used to escape e.g. %block% in
5444 snippets).</td>
5445 <td>snippets.</td>
5446 </tr>
5447 </tbody>
5448 </table>
5449 <p><strong>Global wildcards</strong></p>
5450 <p>These are configurable, see <a class="reference internal" href="#template-preferences">Template preferences</a>.</p>
5451 <table border="1" class="docutils">
5452 <colgroup>
5453 <col width="14%" />
5454 <col width="46%" />
5455 <col width="40%" />
5456 </colgroup>
5457 <thead valign="bottom">
5458 <tr><th class="head">Wildcard</th>
5459 <th class="head">Description</th>
5460 <th class="head">Available in</th>
5461 </tr>
5462 </thead>
5463 <tbody valign="top">
5464 <tr><td>developer</td>
5465 <td>The name of the developer.</td>
5466 <td>file templates, file header,
5467 function description, ChangeLog entry,
5468 bsd, gpl, snippets.</td>
5469 </tr>
5470 <tr><td>initial</td>
5471 <td>The developer's initials, e.g. &quot;ET&quot; for
5472 Enrico Tröger or &quot;JFD&quot; for John Foobar Doe.</td>
5473 <td>file templates, file header,
5474 function description, ChangeLog entry,
5475 bsd, gpl, snippets.</td>
5476 </tr>
5477 <tr><td>mail</td>
5478 <td>The email address of the developer.</td>
5479 <td>file templates, file header,
5480 function description, ChangeLog entry,
5481 bsd, gpl, snippets.</td>
5482 </tr>
5483 <tr><td>company</td>
5484 <td>The company the developer is working for.</td>
5485 <td>file templates, file header,
5486 function description, ChangeLog entry,
5487 bsd, gpl, snippets.</td>
5488 </tr>
5489 <tr><td>version</td>
5490 <td>The initial version of a new file.</td>
5491 <td>file templates, file header,
5492 function description, ChangeLog entry,
5493 bsd, gpl, snippets.</td>
5494 </tr>
5495 </tbody>
5496 </table>
5497 <p><strong>Date &amp; time wildcards</strong></p>
5498 <p>The format for these wildcards can be changed in the preferences
5499 dialog, see <a class="reference internal" href="#template-preferences">Template preferences</a>. You can use any conversion
5500 specifiers which can be used with the ANSI C strftime function.
5501 For details please see <a class="reference external" href="http://man.cx/strftime">http://man.cx/strftime</a>.</p>
5502 <table border="1" class="docutils">
5503 <colgroup>
5504 <col width="14%" />
5505 <col width="46%" />
5506 <col width="40%" />
5507 </colgroup>
5508 <thead valign="bottom">
5509 <tr><th class="head">Wildcard</th>
5510 <th class="head">Description</th>
5511 <th class="head">Available in</th>
5512 </tr>
5513 </thead>
5514 <tbody valign="top">
5515 <tr><td>year</td>
5516 <td>The current year. Default format is: YYYY.</td>
5517 <td>file templates, file header,
5518 function description, ChangeLog entry,
5519 bsd, gpl, snippets.</td>
5520 </tr>
5521 <tr><td>date</td>
5522 <td>The current date. Default format:
5523 YYYY-MM-DD.</td>
5524 <td>file templates, file header,
5525 function description, ChangeLog entry,
5526 bsd, gpl, snippets.</td>
5527 </tr>
5528 <tr><td>datetime</td>
5529 <td>The current date and time. Default format:
5530 DD.MM.YYYY HH:mm:ss ZZZZ.</td>
5531 <td>file templates, file header,
5532 function description, ChangeLog entry,
5533 bsd, gpl, snippets.</td>
5534 </tr>
5535 </tbody>
5536 </table>
5537 <p><strong>Dynamic wildcards</strong></p>
5538 <table border="1" class="docutils">
5539 <colgroup>
5540 <col width="14%" />
5541 <col width="46%" />
5542 <col width="40%" />
5543 </colgroup>
5544 <thead valign="bottom">
5545 <tr><th class="head">Wildcard</th>
5546 <th class="head">Description</th>
5547 <th class="head">Available in</th>
5548 </tr>
5549 </thead>
5550 <tbody valign="top">
5551 <tr><td>untitled</td>
5552 <td>The string &quot;untitled&quot; (this will be
5553 translated to your locale), used in
5554 file templates.</td>
5555 <td>file templates, file header,
5556 function description, ChangeLog entry,
5557 bsd, gpl, snippets.</td>
5558 </tr>
5559 <tr><td>geanyversion</td>
5560 <td>The actual Geany version, e.g.
5561 &quot;Geany 0.21&quot;.</td>
5562 <td>file templates, file header,
5563 function description, ChangeLog entry,
5564 bsd, gpl, snippets.</td>
5565 </tr>
5566 <tr><td>filename</td>
5567 <td>The filename of the current file.
5568 For new files, it's only replaced when
5569 first saving if found on the first 3 lines
5570 of the file.</td>
5571 <td>file header, snippets, file
5572 templates.</td>
5573 </tr>
5574 <tr><td>project</td>
5575 <td>The current project's name, if any.</td>
5576 <td>file header, snippets, file templates.</td>
5577 </tr>
5578 <tr><td>description</td>
5579 <td>The current project's description, if any.</td>
5580 <td>file header, snippets, file templates.</td>
5581 </tr>
5582 <tr><td>functionname</td>
5583 <td>The function name of the function at the
5584 cursor position. This wildcard will only be
5585 replaced in the function description
5586 template.</td>
5587 <td>function description.</td>
5588 </tr>
5589 <tr><td>command:path</td>
5590 <td>Executes the specified command and replace
5591 the wildcard with the command's standard
5592 output. See <a class="reference internal" href="#special-command-wildcard">Special {command:} wildcard</a>
5593 for details.</td>
5594 <td>file templates, file header,
5595 function description, ChangeLog entry,
5596 bsd, gpl, snippets.</td>
5597 </tr>
5598 </tbody>
5599 </table>
5600 <p><strong>Template insertion wildcards</strong></p>
5601 <table border="1" class="docutils">
5602 <colgroup>
5603 <col width="14%" />
5604 <col width="46%" />
5605 <col width="40%" />
5606 </colgroup>
5607 <thead valign="bottom">
5608 <tr><th class="head">Wildcard</th>
5609 <th class="head">Description</th>
5610 <th class="head">Available in</th>
5611 </tr>
5612 </thead>
5613 <tbody valign="top">
5614 <tr><td>gpl</td>
5615 <td>This wildcard inserts a short GPL notice.</td>
5616 <td>file header.</td>
5617 </tr>
5618 <tr><td>bsd</td>
5619 <td>This wildcard inserts a BSD licence notice.</td>
5620 <td>file header.</td>
5621 </tr>
5622 <tr><td>fileheader</td>
5623 <td>The file header template. This wildcard
5624 will only be replaced in file templates.</td>
5625 <td>snippets, file templates.</td>
5626 </tr>
5627 </tbody>
5628 </table>
5629 <div class="section" id="special-command-wildcard">
5630 <h5><a class="toc-backref" href="#id210">Special {command:} wildcard</a></h5>
5631 <p>The {command:} wildcard is a special one because it can execute
5632 a specified command and put the command's output (stdout) into
5633 the template.</p>
5634 <p>Example:</p>
5635 <pre class="literal-block">
5636 {command:uname -a}
5637 </pre>
5638 <p>will result in:</p>
5639 <pre class="literal-block">
5640 Linux localhost 2.6.9-023stab046.2-smp #1 SMP Mon Dec 10 15:04:55 MSK 2007 x86_64 GNU/Linux
5641 </pre>
5642 <p>Using this wildcard you can insert nearly any arbitrary text into the
5643 template.</p>
5644 <p>In the environment of the executed command the variables
5645 <tt class="docutils literal">GEANY_FILENAME</tt>, <tt class="docutils literal">GEANY_FILETYPE</tt> and <tt class="docutils literal">GEANY_FUNCNAME</tt> are set.
5646 The value of these variables is filled in only if Geany knows about it.
5647 For example, <tt class="docutils literal">GEANY_FUNCNAME</tt> is only filled within the function
5648 description template. However, these variables are <tt class="docutils literal">always</tt> set,
5649 just maybe with an empty value.
5650 You can easily access them e.g. within an executed shell script using:</p>
5651 <pre class="literal-block">
5652 $GEANY_FILENAME
5653 </pre>
5654 <div class="note">
5655 <p class="first admonition-title">Note</p>
5656 <p class="last">If the specified command could not be found or not executed, the wildcard is substituted
5657 by an empty string. In such cases, you can find the occurred error message on Geany's
5658 standard error and in the Help-&gt;Debug Messages dialog.</p>
5659 </div>
5660 </div>
5661 </div>
5662 </div>
5663 </div>
5664 <div class="section" id="customizing-the-toolbar">
5665 <h2><a class="toc-backref" href="#id211">Customizing the toolbar</a></h2>
5666 <p>You can add, remove and reorder the elements in the toolbar by using
5667 the toolbar editor, or by manually editing the configuration file
5668 <tt class="docutils literal">ui_toolbar.xml</tt>.</p>
5669 <p>The toolbar editor can be opened from the preferences editor on the Toolbar tab or
5670 by right-clicking on the toolbar itself and choosing it from the menu.</p>
5671 <div class="section" id="manually-editing-the-toolbar-layout">
5672 <h3><a class="toc-backref" href="#id212">Manually editing the toolbar layout</a></h3>
5673 <p>To override the system-wide configuration file, copy it to your user
5674 configuration directory (see <a class="reference internal" href="#configuration-file-paths">Configuration file paths</a>).</p>
5675 <p>For example:</p>
5676 <pre class="literal-block">
5677 % cp /usr/local/share/geany/ui_toolbar.xml /home/username/.config/geany/
5678 </pre>
5679 <p>Then edit it and add any of the available elements listed in the file or remove
5680 any of the existing elements. Of course, you can also reorder the elements as
5681 you wish and add or remove additional separators.
5682 This file must be valid XML, otherwise the global toolbar UI definition
5683 will be used instead.</p>
5684 <p>Your changes are applied once you save the file.</p>
5685 <div class="note">
5686 <p class="first admonition-title">Note</p>
5687 <ol class="last arabic simple">
5688 <li>You cannot add new actions which are not listed below.</li>
5689 <li>Everything you add or change must be inside the /ui/toolbar/ path.</li>
5690 </ol>
5691 </div>
5692 </div>
5693 <div class="section" id="available-toolbar-elements">
5694 <h3><a class="toc-backref" href="#id213">Available toolbar elements</a></h3>
5695 <table border="1" class="docutils">
5696 <colgroup>
5697 <col width="19%" />
5698 <col width="81%" />
5699 </colgroup>
5700 <thead valign="bottom">
5701 <tr><th class="head">Element name</th>
5702 <th class="head">Description</th>
5703 </tr>
5704 </thead>
5705 <tbody valign="top">
5706 <tr><td>New</td>
5707 <td>Create a new file</td>
5708 </tr>
5709 <tr><td>Open</td>
5710 <td>Open an existing file</td>
5711 </tr>
5712 <tr><td>Save</td>
5713 <td>Save the current file</td>
5714 </tr>
5715 <tr><td>SaveAll</td>
5716 <td>Save all open files</td>
5717 </tr>
5718 <tr><td>Reload</td>
5719 <td>Reload the current file from disk</td>
5720 </tr>
5721 <tr><td>Close</td>
5722 <td>Close the current file</td>
5723 </tr>
5724 <tr><td>CloseAll</td>
5725 <td>Close all open files</td>
5726 </tr>
5727 <tr><td>Print</td>
5728 <td>Print the current file</td>
5729 </tr>
5730 <tr><td>Cut</td>
5731 <td>Cut the current selection</td>
5732 </tr>
5733 <tr><td>Copy</td>
5734 <td>Copy the current selection</td>
5735 </tr>
5736 <tr><td>Paste</td>
5737 <td>Paste the contents of the clipboard</td>
5738 </tr>
5739 <tr><td>Delete</td>
5740 <td>Delete the current selection</td>
5741 </tr>
5742 <tr><td>Undo</td>
5743 <td>Undo the last modification</td>
5744 </tr>
5745 <tr><td>Redo</td>
5746 <td>Redo the last modification</td>
5747 </tr>
5748 <tr><td>NavBack</td>
5749 <td>Navigate back a location</td>
5750 </tr>
5751 <tr><td>NavFor</td>
5752 <td>Navigate forward a location</td>
5753 </tr>
5754 <tr><td>Compile</td>
5755 <td>Compile the current file</td>
5756 </tr>
5757 <tr><td>Build</td>
5758 <td>Build the current file, includes a submenu for Make commands. Geany
5759 remembers the last chosen action from the submenu and uses this as default
5760 action when the button itself is clicked.</td>
5761 </tr>
5762 <tr><td>Run</td>
5763 <td>Run or view the current file</td>
5764 </tr>
5765 <tr><td>Color</td>
5766 <td>Open a color chooser dialog, to interactively pick colors from a palette</td>
5767 </tr>
5768 <tr><td>ZoomIn</td>
5769 <td>Zoom in the text</td>
5770 </tr>
5771 <tr><td>ZoomOut</td>
5772 <td>Zoom out the text</td>
5773 </tr>
5774 <tr><td>UnIndent</td>
5775 <td>Decrease indentation</td>
5776 </tr>
5777 <tr><td>Indent</td>
5778 <td>Increase indentation</td>
5779 </tr>
5780 <tr><td>Replace</td>
5781 <td>Replace text in the current document</td>
5782 </tr>
5783 <tr><td>SearchEntry</td>
5784 <td>The search field belonging to the 'Search' element (can be used alone)</td>
5785 </tr>
5786 <tr><td>Search</td>
5787 <td>Find the entered text in the current file (only useful if you also
5788 use 'SearchEntry')</td>
5789 </tr>
5790 <tr><td>GotoEntry</td>
5791 <td>The goto field belonging to the 'Goto' element (can be used alone)</td>
5792 </tr>
5793 <tr><td>Goto</td>
5794 <td>Jump to the entered line number (only useful if you also use 'GotoEntry')</td>
5795 </tr>
5796 <tr><td>Preferences</td>
5797 <td>Show the preferences dialog</td>
5798 </tr>
5799 <tr><td>Quit</td>
5800 <td>Quit Geany</td>
5801 </tr>
5802 </tbody>
5803 </table>
5804 </div>
5805 </div>
5806 </div>
5807 <div class="section" id="plugin-documentation">
5808 <h1><a class="toc-backref" href="#id214">Plugin documentation</a></h1>
5809 <div class="section" id="html-characters">
5810 <h2><a class="toc-backref" href="#id215">HTML Characters</a></h2>
5811 <p>The HTML Characters plugin helps when working with special
5812 characters in XML/HTML, e.g. German Umlauts ü and ä.</p>
5813 <div class="section" id="insert-entity-dialog">
5814 <h3><a class="toc-backref" href="#id216">Insert entity dialog</a></h3>
5815 <p>When the plugin is enabled, you can insert special character
5816 entities using <em>Tools-&gt;Insert Special HTML Characters</em>.</p>
5817 <p>This opens up a dialog where you can find a huge amount of special
5818 characters sorted by category that you might like to use inside your
5819 document. You can expand and collapse the categories by clicking on
5820 the little arrow on the left hand side. Once you have found the
5821 desired character click on it and choose &quot;Insert&quot;. This will insert
5822 the entity for the character at the current cursor position. You
5823 might also like to double click the chosen entity instead.</p>
5824 </div>
5825 <div class="section" id="replace-special-chars-by-its-entity">
5826 <h3><a class="toc-backref" href="#id217">Replace special chars by its entity</a></h3>
5827 <p>To help make a XML/HTML document valid the plugin supports
5828 replacement of special chars known by the plugin. Both bulk
5829 replacement and immediate replacement during typing are supported.</p>
5830 <dl class="docutils">
5831 <dt>A few characters will not be replaced. These are</dt>
5832 <dd><ul class="first last simple">
5833 <li>&quot;</li>
5834 <li>&amp;</li>
5835 <li>&lt;</li>
5836 <li>&gt;</li>
5837 <li>(<cite>&amp;nbsp;</cite>)</li>
5838 </ul>
5839 </dd>
5840 </dl>
5841 <div class="section" id="at-typing-time">
5842 <h4><a class="toc-backref" href="#id218">At typing time</a></h4>
5843 <p>You can activate/deactivate this feature using the <em>Tools-&gt;HTML
5844 Replacement-&gt;Auto-replace Special Characters</em> menu item. If it's
5845 activated, all special characters (beside the given exceptions from
5846 above) known by the plugin will be replaced by their entities.</p>
5847 <p>You could also set a keybinding for the plugin to toggle the status
5848 of this feature.</p>
5849 </div>
5850 <div class="section" id="bulk-replacement">
5851 <h4><a class="toc-backref" href="#id219">Bulk replacement</a></h4>
5852 <p>After inserting a huge amount of text, e.g. by using copy &amp; paste, the
5853 plugin allows bulk replacement of all known characters (beside the
5854 mentioned exceptions). You can find the function under the same
5855 menu at <em>Tools-&gt;HTML Replacement-&gt;Replace Characters in Selection</em>, or
5856 configure a keybinding for the plugin.</p>
5857 </div>
5858 </div>
5859 </div>
5860 <div class="section" id="save-actions">
5861 <h2><a class="toc-backref" href="#id220">Save Actions</a></h2>
5862 <div class="section" id="instant-save">
5863 <h3><a class="toc-backref" href="#id221">Instant Save</a></h3>
5864 <p>This plugin sets on every new file (<em>File-&gt;New</em> or <em>File-&gt;New (with template)</em>)
5865 a randomly chosen filename and set its filetype appropriate to the used template
5866 or when no template was used, to a configurable default filetype.
5867 This enables you to quickly compile, build and/or run the new file without the
5868 need to give it an explicit filename using the Save As dialog. This might be
5869 useful when you often create new files just for testing some code or something
5870 similar.</p>
5871 </div>
5872 <div class="section" id="backup-copy">
5873 <h3><a class="toc-backref" href="#id222">Backup Copy</a></h3>
5874 <p>This plugin creates a backup copy of the current file in Geany when it is
5875 saved. You can specify the directory where the backup copy is saved and
5876 you can configure the automatically added extension in the configure dialog
5877 in Geany's plugin manager.</p>
5878 <p>After the plugin was loaded in Geany's plugin manager, every file is
5879 copied into the configured backup directory when the file is saved in Geany.</p>
5880 </div>
5881 </div>
5882 </div>
5883 <div class="section" id="contributing-to-this-document">
5884 <h1><a class="toc-backref" href="#id223">Contributing to this document</a></h1>
5885 <p>This document (<tt class="docutils literal">geany.txt</tt>) is written in <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>
5886 (or &quot;reST&quot;). The source file for it is located in Geany's <tt class="docutils literal">doc</tt>
5887 subdirectory.  If you intend on making changes, you should grab the
5888 source right from SVN to make sure you've got the newest version. After
5889 editing the file, to build the HTML document to see how your changes
5890 look, run &quot;<tt class="docutils literal">make doc</tt>&quot; in the subdirectory <tt class="docutils literal">doc</tt> of Geany's source
5891 directory. This regenerates the <tt class="docutils literal">geany.html</tt> file. To generate a PDF
5892 file, use the command &quot;<tt class="docutils literal">make pdf</tt>&quot; which should generate a file called
5893 geany-0.21.pdf.</p>
5894 <p>After you are happy with your changes, create a patch:</p>
5895 <pre class="literal-block">
5896 % svn diff geany.txt &gt; foo.patch
5897 </pre>
5898 <p>and then submit that file to the mailing list for review.</p>
5899 <p>Note, you will need the Python docutils software package installed
5900 to build the docs. The package is named <tt class="docutils literal"><span class="pre">python-docutils</span></tt> on Debian
5901 and Fedora systems.</p>
5902 </div>
5903 <div class="section" id="scintilla-keyboard-commands">
5904 <h1><a class="toc-backref" href="#id224">Scintilla keyboard commands</a></h1>
5905 <p>Copyright © 1998, 2006 Neil Hodgson &lt;neilh(at)scintilla(dot)org&gt;</p>
5906 <p>This appendix is distributed under the terms of the License for
5907 Scintilla and SciTE. A copy of this license can be found in the file
5908 <tt class="docutils literal">scintilla/License.txt</tt> included with the source code of this
5909 program and in the appendix of this document. See <a class="reference internal" href="#license-for-scintilla-and-scite">License for
5910 Scintilla and SciTE</a>.</p>
5911 <p>20 June 2006</p>
5912 <div class="section" id="keyboard-commands">
5913 <h2><a class="toc-backref" href="#id225">Keyboard commands</a></h2>
5914 <p>Keyboard commands for Scintilla mostly follow common Windows and GTK+
5915 conventions. All move keys (arrows, page up/down, home and end)
5916 allows to extend or reduce the stream selection when holding the
5917 Shift key, and the rectangular selection when holding the Shift and
5918 Ctrl keys. Some keys may not be available with some national keyboards
5919 or because they are taken by the system such as by a window manager
5920 or GTK. Keyboard equivalents of menu commands are listed in the
5921 menus. Some less common commands with no menu equivalent are:</p>
5922 <table border="1" class="docutils">
5923 <colgroup>
5924 <col width="67%" />
5925 <col width="33%" />
5926 </colgroup>
5927 <thead valign="bottom">
5928 <tr><th class="head">Action</th>
5929 <th class="head">Shortcut key</th>
5930 </tr>
5931 </thead>
5932 <tbody valign="top">
5933 <tr><td>Magnify text size.</td>
5934 <td>Ctrl-Keypad+</td>
5935 </tr>
5936 <tr><td>Reduce text size.</td>
5937 <td>Ctrl-Keypad-</td>
5938 </tr>
5939 <tr><td>Restore text size to normal.</td>
5940 <td>Ctrl-Keypad/</td>
5941 </tr>
5942 <tr><td>Indent block.</td>
5943 <td>Tab</td>
5944 </tr>
5945 <tr><td>Dedent block.</td>
5946 <td>Shift-Tab</td>
5947 </tr>
5948 <tr><td>Delete to start of word.</td>
5949 <td>Ctrl-BackSpace</td>
5950 </tr>
5951 <tr><td>Delete to end of word.</td>
5952 <td>Ctrl-Delete</td>
5953 </tr>
5954 <tr><td>Delete to start of line.</td>
5955 <td>Ctrl-Shift-BackSpace</td>
5956 </tr>
5957 <tr><td>Go to start of document.</td>
5958 <td>Ctrl-Home</td>
5959 </tr>
5960 <tr><td>Extend selection to start of document.</td>
5961 <td>Ctrl-Shift-Home</td>
5962 </tr>
5963 <tr><td>Go to start of display line.</td>
5964 <td>Alt-Home</td>
5965 </tr>
5966 <tr><td>Extend selection to start of display line.</td>
5967 <td>Alt-Shift-Home</td>
5968 </tr>
5969 <tr><td>Go to end of document.</td>
5970 <td>Ctrl-End</td>
5971 </tr>
5972 <tr><td>Extend selection to end of document.</td>
5973 <td>Ctrl-Shift-End</td>
5974 </tr>
5975 <tr><td>Extend selection to end of display line.</td>
5976 <td>Alt-Shift-End</td>
5977 </tr>
5978 <tr><td>Previous paragraph. Shift extends selection.</td>
5979 <td>Ctrl-Up</td>
5980 </tr>
5981 <tr><td>Next paragraph. Shift extends selection.</td>
5982 <td>Ctrl-Down</td>
5983 </tr>
5984 <tr><td>Previous word. Shift extends selection.</td>
5985 <td>Ctrl-Left</td>
5986 </tr>
5987 <tr><td>Next word. Shift extends selection.</td>
5988 <td>Ctrl-Right</td>
5989 </tr>
5990 </tbody>
5991 </table>
5992 </div>
5993 </div>
5994 <div class="section" id="tips-and-tricks">
5995 <h1><a class="toc-backref" href="#id226">Tips and tricks</a></h1>
5996 <div class="section" id="document-notebook">
5997 <h2><a class="toc-backref" href="#id227">Document notebook</a></h2>
5998 <ul class="simple">
5999 <li>Double-click on empty space in the notebook tab bar to open a
6000 new document.</li>
6001 <li>Middle-click on a document's notebook tab to close the document.</li>
6002 <li>Hold <cite>Ctrl</cite> and click on any notebook tab to switch to the last used
6003 document.</li>
6004 <li>Double-click on a document's notebook tab to toggle all additional
6005 widgets (to show them again use the View menu or the keyboard
6006 shortcut). The interface pref must be enabled for this to work.</li>
6007 </ul>
6008 </div>
6009 <div class="section" id="editor">
6010 <h2><a class="toc-backref" href="#id228">Editor</a></h2>
6011 <ul class="simple">
6012 <li>Alt-scroll wheel moves up/down a page.</li>
6013 <li>Ctrl-scroll wheel zooms in/out.</li>
6014 <li>Shift-scroll wheel scrolls 8 characters right/left.</li>
6015 <li>Ctrl-click on a word in a document to perform <em>Go to Tag Definition</em>.</li>
6016 <li>Ctrl-click on a bracket/brace to perform <em>Go to Matching Brace</em>.</li>
6017 </ul>
6018 </div>
6019 <div class="section" id="interface">
6020 <h2><a class="toc-backref" href="#id229">Interface</a></h2>
6021 <ul class="simple">
6022 <li>Double-click on a symbol-list group to expand or compact it.</li>
6023 </ul>
6024 </div>
6025 <div class="section" id="gtk-related">
6026 <h2><a class="toc-backref" href="#id230">GTK-related</a></h2>
6027 <ul class="simple">
6028 <li>Scrolling the mouse wheel over a notebook tab bar will switch
6029 notebook pages.</li>
6030 </ul>
6031 <p>The following are derived from X-Windows features (but GTK still supports
6032 them on Windows):</p>
6033 <ul class="simple">
6034 <li>Middle-click pastes the last selected text.</li>
6035 <li>Middle-click on a scrollbar moves the scrollbar to that
6036 position without having to drag it.</li>
6037 </ul>
6038 </div>
6039 </div>
6040 <div class="section" id="compile-time-options">
6041 <h1><a class="toc-backref" href="#id231">Compile-time options</a></h1>
6042 <p>There are some options which can only be changed at compile time,
6043 and some options which are used as the default for configurable
6044 options. To change these options, edit the appropriate source file
6045 in the <tt class="docutils literal">src</tt> subdirectory. Look for a block of lines starting with
6046 <tt class="docutils literal">#define GEANY_*</tt>. Any definitions which are not listed here should
6047 not be changed.</p>
6048 <div class="note">
6049 <p class="first admonition-title">Note</p>
6050 <p class="last">Most users should not need to change these options.</p>
6051 </div>
6052 <div class="section" id="src-geany-h">
6053 <h2><a class="toc-backref" href="#id232">src/geany.h</a></h2>
6054 <table border="1" class="docutils">
6055 <colgroup>
6056 <col width="33%" />
6057 <col width="48%" />
6058 <col width="20%" />
6059 </colgroup>
6060 <thead valign="bottom">
6061 <tr><th class="head">Option</th>
6062 <th class="head">Description</th>
6063 <th class="head">Default</th>
6064 </tr>
6065 </thead>
6066 <tbody valign="top">
6067 <tr><td>GEANY_STRING_UNTITLED</td>
6068 <td>A string used as the default name for new
6069 files. Be aware that the string can be
6070 translated, so change it only if you know
6071 what you are doing.</td>
6072 <td>untitled</td>
6073 </tr>
6074 <tr><td>GEANY_WINDOW_MINIMAL_WIDTH</td>
6075 <td>The minimal width of the main window.</td>
6076 <td>620</td>
6077 </tr>
6078 <tr><td>GEANY_WINDOW_MINIMAL_HEIGHT</td>
6079 <td>The minimal height of the main window.</td>
6080 <td>440</td>
6081 </tr>
6082 <tr><td>GEANY_WINDOW_DEFAULT_WIDTH</td>
6083 <td>The default width of the main window at the
6084 first start.</td>
6085 <td>900</td>
6086 </tr>
6087 <tr><td>GEANY_WINDOW_DEFAULT_HEIGHT</td>
6088 <td>The default height of the main window at the
6089 first start.</td>
6090 <td>600</td>
6091 </tr>
6092 <tr><td><strong>Windows specific</strong></td>
6093 <td>&nbsp;</td>
6094 <td>&nbsp;</td>
6095 </tr>
6096 <tr><td>GEANY_USE_WIN32_DIALOG</td>
6097 <td>Set this to 1 if you want to use the default
6098 Windows file open and save dialogs instead
6099 GTK's file open and save dialogs. The
6100 default Windows file dialogs are missing
6101 some nice features like choosing a filetype
6102 or an encoding. <em>Do not touch this setting
6103 when building on a non-Win32 system.</em></td>
6104 <td>0</td>
6105 </tr>
6106 </tbody>
6107 </table>
6108 </div>
6109 <div class="section" id="project-h">
6110 <h2><a class="toc-backref" href="#id233">project.h</a></h2>
6111 <table border="1" class="docutils">
6112 <colgroup>
6113 <col width="33%" />
6114 <col width="48%" />
6115 <col width="20%" />
6116 </colgroup>
6117 <thead valign="bottom">
6118 <tr><th class="head">Option</th>
6119 <th class="head">Description</th>
6120 <th class="head">Default</th>
6121 </tr>
6122 </thead>
6123 <tbody valign="top">
6124 <tr><td>GEANY_PROJECT_EXT</td>
6125 <td>The default filename extension for Geany
6126 project files. It is used when creating new
6127 projects and as filter mask for the project
6128 open dialog.</td>
6129 <td>geany</td>
6130 </tr>
6131 </tbody>
6132 </table>
6133 </div>
6134 <div class="section" id="editor-h">
6135 <h2><a class="toc-backref" href="#id234">editor.h</a></h2>
6136 <table border="1" class="docutils">
6137 <colgroup>
6138 <col width="33%" />
6139 <col width="48%" />
6140 <col width="20%" />
6141 </colgroup>
6142 <thead valign="bottom">
6143 <tr><th class="head">Option</th>
6144 <th class="head">Description</th>
6145 <th class="head">Default</th>
6146 </tr>
6147 </thead>
6148 <tbody valign="top">
6149 <tr><td>GEANY_WORDCHARS</td>
6150 <td>These characters define word boundaries when
6151 making selections and searching using word
6152 matching options.</td>
6153 <td>a string with:
6154 a-z, A-Z, 0-9 and
6155 underscore.</td>
6156 </tr>
6157 </tbody>
6158 </table>
6159 </div>
6160 <div class="section" id="keyfile-c">
6161 <h2><a class="toc-backref" href="#id235">keyfile.c</a></h2>
6162 <p>These are default settings that can be overridden in the <a class="reference internal" href="#preferences">Preferences</a> dialog.</p>
6163 <table border="1" class="docutils">
6164 <colgroup>
6165 <col width="33%" />
6166 <col width="48%" />
6167 <col width="20%" />
6168 </colgroup>
6169 <thead valign="bottom">
6170 <tr><th class="head">Option</th>
6171 <th class="head">Description</th>
6172 <th class="head">Default</th>
6173 </tr>
6174 </thead>
6175 <tbody valign="top">
6176 <tr><td>GEANY_MIN_SYMBOLLIST_CHARS</td>
6177 <td>How many characters you need to type to
6178 trigger the autocompletion list.</td>
6179 <td>4</td>
6180 </tr>
6181 <tr><td>GEANY_DISK_CHECK_TIMEOUT</td>
6182 <td>Time in seconds between checking a file for
6183 external changes.</td>
6184 <td>30</td>
6185 </tr>
6186 <tr><td>GEANY_DEFAULT_TOOLS_MAKE</td>
6187 <td>The make tool. This can also include a path.</td>
6188 <td>&quot;make&quot;</td>
6189 </tr>
6190 <tr><td>GEANY_DEFAULT_TOOLS_TERMINAL</td>
6191 <td>A terminal emulator. It has to accept the
6192 command line option &quot;-e&quot;. This can also
6193 include a path.</td>
6194 <td>&quot;xterm&quot;</td>
6195 </tr>
6196 <tr><td>GEANY_DEFAULT_TOOLS_BROWSER</td>
6197 <td>A web browser. This can also include a path.</td>
6198 <td>&quot;firefox&quot;</td>
6199 </tr>
6200 <tr><td>GEANY_DEFAULT_TOOLS_PRINTCMD</td>
6201 <td>A printing tool. It should be able to accept
6202 and process plain text files. This can also
6203 include a path.</td>
6204 <td>&quot;lpr&quot;</td>
6205 </tr>
6206 <tr><td>GEANY_DEFAULT_TOOLS_GREP</td>
6207 <td>A grep tool. It should be compatible with
6208 GNU grep. This can also include a path.</td>
6209 <td>&quot;grep&quot;</td>
6210 </tr>
6211 <tr><td>GEANY_DEFAULT_MRU_LENGTH</td>
6212 <td>The length of the &quot;Recent files&quot; list.</td>
6213 <td>10</td>
6214 </tr>
6215 <tr><td>GEANY_DEFAULT_FONT_SYMBOL_LIST</td>
6216 <td>The font used in sidebar to show symbols and
6217 open files.</td>
6218 <td>&quot;Sans 9&quot;</td>
6219 </tr>
6220 <tr><td>GEANY_DEFAULT_FONT_MSG_WINDOW</td>
6221 <td>The font used in the messages window.</td>
6222 <td>&quot;Sans 9&quot;</td>
6223 </tr>
6224 <tr><td>GEANY_DEFAULT_FONT_EDITOR</td>
6225 <td>The font used in the editor window.</td>
6226 <td>&quot;Monospace 10&quot;</td>
6227 </tr>
6228 <tr><td>GEANY_TOGGLE_MARK</td>
6229 <td>A string which is used to mark a toggled
6230 comment.</td>
6231 <td>&quot;~ &quot;</td>
6232 </tr>
6233 <tr><td>GEANY_MAX_AUTOCOMPLETE_WORDS</td>
6234 <td>How many autocompletion suggestions should
6235 Geany provide.</td>
6236 <td>30</td>
6237 </tr>
6238 </tbody>
6239 </table>
6240 </div>
6241 <div class="section" id="build-c">
6242 <h2><a class="toc-backref" href="#id236">build.c</a></h2>
6243 <table border="1" class="docutils">
6244 <colgroup>
6245 <col width="33%" />
6246 <col width="48%" />
6247 <col width="20%" />
6248 </colgroup>
6249 <thead valign="bottom">
6250 <tr><th class="head">Option</th>
6251 <th class="head">Description</th>
6252 <th class="head">Default</th>
6253 </tr>
6254 </thead>
6255 <tbody valign="top">
6256 <tr><td>GEANY_BUILD_ERR_HIGHLIGHT_MAX</td>
6257 <td>Amount of build error indicators to
6258 be shown in the editor window.
6259 This affects the special coloring
6260 when Geany detects a compiler output line as
6261 an error message and then highlights the
6262 corresponding line in the source code.
6263 Usually only the first few messages are
6264 interesting because following errors are
6265 just after-effects.
6266 All errors in the Compiler window are parsed
6267 and unaffected by this value.</td>
6268 <td>50</td>
6269 </tr>
6270 <tr><td>PRINTBUILDCMDS</td>
6271 <td>Every time a build menu item priority
6272 calculation is run, print the state of the
6273 menu item table in the form of the table
6274 in <a class="reference internal" href="#build-menu-configuration">Build Menu Configuration</a>.  May be
6275 useful to debug configuration file
6276 overloading.  Warning produces a lot of
6277 output.  Can also be enabled/disabled by the
6278 debugger by setting printbuildcmds to 1/0
6279 overriding the compile setting.</td>
6280 <td>FALSE</td>
6281 </tr>
6282 </tbody>
6283 </table>
6284 </div>
6285 </div>
6286 <div class="section" id="gnu-general-public-license">
6287 <h1><a class="toc-backref" href="#id237">GNU General Public License</a></h1>
6288 <pre class="literal-block">
6289             GNU GENERAL PUBLIC LICENSE
6290                Version 2, June 1991
6291
6292  Copyright (C) 1989, 1991 Free Software Foundation, Inc.
6293     51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
6294  Everyone is permitted to copy and distribute verbatim copies
6295  of this license document, but changing it is not allowed.
6296
6297                 Preamble
6298
6299   The licenses for most software are designed to take away your
6300 freedom to share and change it.  By contrast, the GNU General Public
6301 License is intended to guarantee your freedom to share and change free
6302 software--to make sure the software is free for all its users.  This
6303 General Public License applies to most of the Free Software
6304 Foundation's software and to any other program whose authors commit to
6305 using it.  (Some other Free Software Foundation software is covered by
6306 the GNU Library General Public License instead.)  You can apply it to
6307 your programs, too.
6308
6309   When we speak of free software, we are referring to freedom, not
6310 price.  Our General Public Licenses are designed to make sure that you
6311 have the freedom to distribute copies of free software (and charge for
6312 this service if you wish), that you receive source code or can get it
6313 if you want it, that you can change the software or use pieces of it
6314 in new free programs; and that you know you can do these things.
6315
6316   To protect your rights, we need to make restrictions that forbid
6317 anyone to deny you these rights or to ask you to surrender the rights.
6318 These restrictions translate to certain responsibilities for you if you
6319 distribute copies of the software, or if you modify it.
6320
6321   For example, if you distribute copies of such a program, whether
6322 gratis or for a fee, you must give the recipients all the rights that
6323 you have.  You must make sure that they, too, receive or can get the
6324 source code.  And you must show them these terms so they know their
6325 rights.
6326
6327   We protect your rights with two steps: (1) copyright the software, and
6328 (2) offer you this license which gives you legal permission to copy,
6329 distribute and/or modify the software.
6330
6331   Also, for each author's protection and ours, we want to make certain
6332 that everyone understands that there is no warranty for this free
6333 software.  If the software is modified by someone else and passed on, we
6334 want its recipients to know that what they have is not the original, so
6335 that any problems introduced by others will not reflect on the original
6336 authors' reputations.
6337
6338   Finally, any free program is threatened constantly by software
6339 patents.  We wish to avoid the danger that redistributors of a free
6340 program will individually obtain patent licenses, in effect making the
6341 program proprietary.  To prevent this, we have made it clear that any
6342 patent must be licensed for everyone's free use or not licensed at all.
6343
6344   The precise terms and conditions for copying, distribution and
6345 modification follow.
6346
6347             GNU GENERAL PUBLIC LICENSE
6348    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
6349
6350   0. This License applies to any program or other work which contains
6351 a notice placed by the copyright holder saying it may be distributed
6352 under the terms of this General Public License.  The &quot;Program&quot;, below,
6353 refers to any such program or work, and a &quot;work based on the Program&quot;
6354 means either the Program or any derivative work under copyright law:
6355 that is to say, a work containing the Program or a portion of it,
6356 either verbatim or with modifications and/or translated into another
6357 language.  (Hereinafter, translation is included without limitation in
6358 the term &quot;modification&quot;.)  Each licensee is addressed as &quot;you&quot;.
6359
6360 Activities other than copying, distribution and modification are not
6361 covered by this License; they are outside its scope.  The act of
6362 running the Program is not restricted, and the output from the Program
6363 is covered only if its contents constitute a work based on the
6364 Program (independent of having been made by running the Program).
6365 Whether that is true depends on what the Program does.
6366
6367   1. You may copy and distribute verbatim copies of the Program's
6368 source code as you receive it, in any medium, provided that you
6369 conspicuously and appropriately publish on each copy an appropriate
6370 copyright notice and disclaimer of warranty; keep intact all the
6371 notices that refer to this License and to the absence of any warranty;
6372 and give any other recipients of the Program a copy of this License
6373 along with the Program.
6374
6375 You may charge a fee for the physical act of transferring a copy, and
6376 you may at your option offer warranty protection in exchange for a fee.
6377
6378   2. You may modify your copy or copies of the Program or any portion
6379 of it, thus forming a work based on the Program, and copy and
6380 distribute such modifications or work under the terms of Section 1
6381 above, provided that you also meet all of these conditions:
6382
6383     a) You must cause the modified files to carry prominent notices
6384     stating that you changed the files and the date of any change.
6385
6386     b) You must cause any work that you distribute or publish, that in
6387     whole or in part contains or is derived from the Program or any
6388     part thereof, to be licensed as a whole at no charge to all third
6389     parties under the terms of this License.
6390
6391     c) If the modified program normally reads commands interactively
6392     when run, you must cause it, when started running for such
6393     interactive use in the most ordinary way, to print or display an
6394     announcement including an appropriate copyright notice and a
6395     notice that there is no warranty (or else, saying that you provide
6396     a warranty) and that users may redistribute the program under
6397     these conditions, and telling the user how to view a copy of this
6398     License.  (Exception: if the Program itself is interactive but
6399     does not normally print such an announcement, your work based on
6400     the Program is not required to print an announcement.)
6401
6402 These requirements apply to the modified work as a whole.  If
6403 identifiable sections of that work are not derived from the Program,
6404 and can be reasonably considered independent and separate works in
6405 themselves, then this License, and its terms, do not apply to those
6406 sections when you distribute them as separate works.  But when you
6407 distribute the same sections as part of a whole which is a work based
6408 on the Program, the distribution of the whole must be on the terms of
6409 this License, whose permissions for other licensees extend to the
6410 entire whole, and thus to each and every part regardless of who wrote it.
6411
6412 Thus, it is not the intent of this section to claim rights or contest
6413 your rights to work written entirely by you; rather, the intent is to
6414 exercise the right to control the distribution of derivative or
6415 collective works based on the Program.
6416
6417 In addition, mere aggregation of another work not based on the Program
6418 with the Program (or with a work based on the Program) on a volume of
6419 a storage or distribution medium does not bring the other work under
6420 the scope of this License.
6421
6422   3. You may copy and distribute the Program (or a work based on it,
6423 under Section 2) in object code or executable form under the terms of
6424 Sections 1 and 2 above provided that you also do one of the following:
6425
6426     a) Accompany it with the complete corresponding machine-readable
6427     source code, which must be distributed under the terms of Sections
6428     1 and 2 above on a medium customarily used for software interchange; or,
6429
6430     b) Accompany it with a written offer, valid for at least three
6431     years, to give any third party, for a charge no more than your
6432     cost of physically performing source distribution, a complete
6433     machine-readable copy of the corresponding source code, to be
6434     distributed under the terms of Sections 1 and 2 above on a medium
6435     customarily used for software interchange; or,
6436
6437     c) Accompany it with the information you received as to the offer
6438     to distribute corresponding source code.  (This alternative is
6439     allowed only for noncommercial distribution and only if you
6440     received the program in object code or executable form with such
6441     an offer, in accord with Subsection b above.)
6442
6443 The source code for a work means the preferred form of the work for
6444 making modifications to it.  For an executable work, complete source
6445 code means all the source code for all modules it contains, plus any
6446 associated interface definition files, plus the scripts used to
6447 control compilation and installation of the executable.  However, as a
6448 special exception, the source code distributed need not include
6449 anything that is normally distributed (in either source or binary
6450 form) with the major components (compiler, kernel, and so on) of the
6451 operating system on which the executable runs, unless that component
6452 itself accompanies the executable.
6453
6454 If distribution of executable or object code is made by offering
6455 access to copy from a designated place, then offering equivalent
6456 access to copy the source code from the same place counts as
6457 distribution of the source code, even though third parties are not
6458 compelled to copy the source along with the object code.
6459
6460   4. You may not copy, modify, sublicense, or distribute the Program
6461 except as expressly provided under this License.  Any attempt
6462 otherwise to copy, modify, sublicense or distribute the Program is
6463 void, and will automatically terminate your rights under this License.
6464 However, parties who have received copies, or rights, from you under
6465 this License will not have their licenses terminated so long as such
6466 parties remain in full compliance.
6467
6468   5. You are not required to accept this License, since you have not
6469 signed it.  However, nothing else grants you permission to modify or
6470 distribute the Program or its derivative works.  These actions are
6471 prohibited by law if you do not accept this License.  Therefore, by
6472 modifying or distributing the Program (or any work based on the
6473 Program), you indicate your acceptance of this License to do so, and
6474 all its terms and conditions for copying, distributing or modifying
6475 the Program or works based on it.
6476
6477   6. Each time you redistribute the Program (or any work based on the
6478 Program), the recipient automatically receives a license from the
6479 original licensor to copy, distribute or modify the Program subject to
6480 these terms and conditions.  You may not impose any further
6481 restrictions on the recipients' exercise of the rights granted herein.
6482 You are not responsible for enforcing compliance by third parties to
6483 this License.
6484
6485   7. If, as a consequence of a court judgment or allegation of patent
6486 infringement or for any other reason (not limited to patent issues),
6487 conditions are imposed on you (whether by court order, agreement or
6488 otherwise) that contradict the conditions of this License, they do not
6489 excuse you from the conditions of this License.  If you cannot
6490 distribute so as to satisfy simultaneously your obligations under this
6491 License and any other pertinent obligations, then as a consequence you
6492 may not distribute the Program at all.  For example, if a patent
6493 license would not permit royalty-free redistribution of the Program by
6494 all those who receive copies directly or indirectly through you, then
6495 the only way you could satisfy both it and this License would be to
6496 refrain entirely from distribution of the Program.
6497
6498 If any portion of this section is held invalid or unenforceable under
6499 any particular circumstance, the balance of the section is intended to
6500 apply and the section as a whole is intended to apply in other
6501 circumstances.
6502
6503 It is not the purpose of this section to induce you to infringe any
6504 patents or other property right claims or to contest validity of any
6505 such claims; this section has the sole purpose of protecting the
6506 integrity of the free software distribution system, which is
6507 implemented by public license practices.  Many people have made
6508 generous contributions to the wide range of software distributed
6509 through that system in reliance on consistent application of that
6510 system; it is up to the author/donor to decide if he or she is willing
6511 to distribute software through any other system and a licensee cannot
6512 impose that choice.
6513
6514 This section is intended to make thoroughly clear what is believed to
6515 be a consequence of the rest of this License.
6516
6517   8. If the distribution and/or use of the Program is restricted in
6518 certain countries either by patents or by copyrighted interfaces, the
6519 original copyright holder who places the Program under this License
6520 may add an explicit geographical distribution limitation excluding
6521 those countries, so that distribution is permitted only in or among
6522 countries not thus excluded.  In such case, this License incorporates
6523 the limitation as if written in the body of this License.
6524
6525   9. The Free Software Foundation may publish revised and/or new versions
6526 of the General Public License from time to time.  Such new versions will
6527 be similar in spirit to the present version, but may differ in detail to
6528 address new problems or concerns.
6529
6530 Each version is given a distinguishing version number.  If the Program
6531 specifies a version number of this License which applies to it and &quot;any
6532 later version&quot;, you have the option of following the terms and conditions
6533 either of that version or of any later version published by the Free
6534 Software Foundation.  If the Program does not specify a version number of
6535 this License, you may choose any version ever published by the Free Software
6536 Foundation.
6537
6538   10. If you wish to incorporate parts of the Program into other free
6539 programs whose distribution conditions are different, write to the author
6540 to ask for permission.  For software which is copyrighted by the Free
6541 Software Foundation, write to the Free Software Foundation; we sometimes
6542 make exceptions for this.  Our decision will be guided by the two goals
6543 of preserving the free status of all derivatives of our free software and
6544 of promoting the sharing and reuse of software generally.
6545
6546                 NO WARRANTY
6547
6548   11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
6549 FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
6550 OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
6551 PROVIDE THE PROGRAM &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
6552 OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
6553 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
6554 TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
6555 PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
6556 REPAIR OR CORRECTION.
6557
6558   12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
6559 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
6560 REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
6561 INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
6562 OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
6563 TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
6564 YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
6565 PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
6566 POSSIBILITY OF SUCH DAMAGES.
6567
6568              END OF TERMS AND CONDITIONS
6569
6570         How to Apply These Terms to Your New Programs
6571
6572   If you develop a new program, and you want it to be of the greatest
6573 possible use to the public, the best way to achieve this is to make it
6574 free software which everyone can redistribute and change under these terms.
6575
6576   To do so, attach the following notices to the program.  It is safest
6577 to attach them to the start of each source file to most effectively
6578 convey the exclusion of warranty; and each file should have at least
6579 the &quot;copyright&quot; line and a pointer to where the full notice is found.
6580
6581     &lt;one line to give the program's name and a brief idea of what it does.&gt;
6582     Copyright (C) &lt;year&gt;  &lt;name of author&gt;
6583
6584     This program is free software; you can redistribute it and/or modify
6585     it under the terms of the GNU General Public License as published by
6586     the Free Software Foundation; either version 2 of the License, or
6587     (at your option) any later version.
6588
6589     This program is distributed in the hope that it will be useful,
6590     but WITHOUT ANY WARRANTY; without even the implied warranty of
6591     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
6592     GNU General Public License for more details.
6593
6594     You should have received a copy of the GNU General Public License
6595     along with this program; if not, write to the Free Software
6596     Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA
6597
6598
6599 Also add information on how to contact you by electronic and paper mail.
6600
6601 If the program is interactive, make it output a short notice like this
6602 when it starts in an interactive mode:
6603
6604     Gnomovision version 69, Copyright (C) year  name of author
6605     Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
6606     This is free software, and you are welcome to redistribute it
6607     under certain conditions; type `show c' for details.
6608
6609 The hypothetical commands `show w' and `show c' should show the appropriate
6610 parts of the General Public License.  Of course, the commands you use may
6611 be called something other than `show w' and `show c'; they could even be
6612 mouse-clicks or menu items--whatever suits your program.
6613
6614 You should also get your employer (if you work as a programmer) or your
6615 school, if any, to sign a &quot;copyright disclaimer&quot; for the program, if
6616 necessary.  Here is a sample; alter the names:
6617
6618   Yoyodyne, Inc., hereby disclaims all copyright interest in the program
6619   `Gnomovision' (which makes passes at compilers) written by James Hacker.
6620
6621   &lt;signature of Ty Coon&gt;, 1 April 1989
6622   Ty Coon, President of Vice
6623
6624 This General Public License does not permit incorporating your program into
6625 proprietary programs.  If your program is a subroutine library, you may
6626 consider it more useful to permit linking proprietary applications with the
6627 library.  If this is what you want to do, use the GNU Library General
6628 Public License instead of this License.
6629 </pre>
6630 </div>
6631 <div class="section" id="license-for-scintilla-and-scite">
6632 <h1><a class="toc-backref" href="#id238">License for Scintilla and SciTE</a></h1>
6633 <p>Copyright 1998-2003 by Neil Hodgson &lt;neilh(at)scintilla(dot)org&gt;</p>
6634 <p>All Rights Reserved</p>
6635 <p>Permission to use, copy, modify, and distribute this software and
6636 its documentation for any purpose and without fee is hereby granted,
6637 provided that the above copyright notice appear in all copies and
6638 that both that copyright notice and this permission notice appear in
6639 supporting documentation.</p>
6640 <p>NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
6641 INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
6642 NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR
6643 CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
6644 OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
6645 OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE
6646 USE OR PERFORMANCE OF THIS SOFTWARE.</p>
6647 </div>
6648 </div>
6649 <div class="footer">
6650 <hr class="footer" />
6651 <a class="reference external" href="geany.txt">View document source</a>.
6652 Generated on: 2011-10-02 13:04 UTC.
6653 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
6654
6655 </div>
6656 </body>
6657 </html>