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