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