/usr/share/doc/gnat-gps/html/The-Preferences-Dialog.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Copyright (C) 2002-2010 AdaCore.

This document is free; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, see http://www.gnu.org/licenses/.

A copy of the license is included in the section entitled
"GNU General Public License". -->
<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Using the GNAT Programming Studio: The Preferences Dialog</title>

<meta name="description" content="Using the GNAT Programming Studio: The Preferences Dialog">
<meta name="keywords" content="Using the GNAT Programming Studio: The Preferences Dialog">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Index-table.html#Index-table" rel="index" title="Index table">
<link href="Customizing-and-Extending-GPS.html#Customizing-and-Extending-GPS" rel="up" title="Customizing and Extending GPS">
<link href="GPS-Themes.html#GPS-Themes" rel="next" title="GPS Themes">
<link href="Customizing-and-Extending-GPS.html#Customizing-and-Extending-GPS" rel="previous" title="Customizing and Extending GPS">
<style type="text/css">
<!--
   

a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
pre.smallexample {background-color:rgb(240,240,240);
                     font-family: courier new,courier,fixed;
                     font-size: 14px;
                     margin: 0px 40px 0px 40px;
                     border-width: 1px 2px 2px 1px;
                     border-top-style: dotted;
                     border-left-style: dotted;
                     border-right-style: solid;
                     border-bottom-style: solid;
                     border-color: black;}
   code             {color:black;
                     font-family: courier new,courier,fixed;
                     font-size: 14px;}
   body             {font-family: arial,helvetica,sans-serif;
                     font-size: 16px;
                     max-width: 800px;
                     text-align: justify}
   samp             {font-family: courier new,courier,fixed;
                     font-size: 14px}
                    

-->
</style>


</head>

<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="The-Preferences-Dialog"></a>
<div class="header">
<p>
Next: <a href="GPS-Themes.html#GPS-Themes" accesskey="n" rel="next">GPS Themes</a>, Up: <a href="Customizing-and-Extending-GPS.html#Customizing-and-Extending-GPS" accesskey="u" rel="up">Customizing and Extending GPS</a> &nbsp; [<a href="Index-table.html#Index-table" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="The-Preferences-Dialog-1"></a>
<h3 class="section">16.1 The Preferences Dialog</h3>
<a name="preferences-dialog"></a><a name="index-preferences-7"></a>
<p>This dialog, available through the menu <code>Edit-&gt;Preferences</code>, allows you to
modify the global preferences of GPS.
To enable the new preferences, you simply need to confirm by pressing
the <code>OK</code> button. To test your changes, you can use the <code>Apply</code>
button. Pressing the <code>Cancel</code> button will undo all your changes.
</p>

<a name="index-screen-shot-53"></a>
<img src="preferences-general.jpg" alt="preferences-general">

<p>Each preference is composed of a label displaying the name of the
preference, and an editing area to modify its value. If you leave to mouse
over the label, a tool tip will be displayed giving an on-line help on the
preference.
</p>
<p>The preferences dialog is composed of several areas, accessible through the
tabs at the left of the dialog.
Each page corresponds to a set of preferences.
</p>
<ul>
<li> <b>Themes</b>

<p>This page allows you to quickly change the current settings for GPS, including
preferences, key bindings, menus&hellip;; See <a href="GPS-Themes.html#GPS-Themes">GPS Themes</a> for more
information on themes. It is only displayed when there are themes registered.
</p>
</li><li> <b>General</b>

<dl compact="compact">
<dt><i>Default font</i></dt>
<dd><a name="index-font"></a>
<a name="index-background-color"></a>
<p>The default font used in GPS. The background color you select for this
preference will set the background color for all consoles and most views (the
ones that display their data as trees, mostly). To change the background color
of editors, see the preference Edit/Fonts&amp;Colors/Default.
</p>
</dd>
<dt><i>Fixed view font</i></dt>
<dd><a name="index-font-1"></a>
<p>The fixed (monospace) font used in views like the outline view, the bookmark
view, &hellip;; As much as possible, this font should use a fixed width for
characters, for a better rendering
</p>
</dd>
<dt><i>Character set</i></dt>
<dd><a name="index-character-set-1"></a>
<a name="index-ISO_002d8859_002d1"></a>
<p>Name of character set to use when reading or writting text files.
GPS uses UTF-8 and Unicode internally, which can handle any character in
any language. However, your system will generally not support Unicode natively,
and thus the contents of the files should be translated from the file system
encoding to unicode.
</p>
<p>This preference indicates the file system encoding in use. It defaults to
ISO-8859-1, which corresponds to western european characters.
</p>
</dd>
<dt><i>Display splash screen</i></dt>
<dd><a name="index-splash-screen"></a>
<p>Whether a splash screen should be displayed when starting GPS.
</p>
</dd>
<dt><i>Display welcome window</i></dt>
<dd><a name="index-welcome-dialog-1"></a>
<p>Whether GPS should display the welcome window for the selection of the project
to use.
</p>
</dd>
<dt><i>Show text in tool bar</i></dt>
<dd><a name="index-tool-bar-1"></a>
<p>Whether the tool bar should show both text and icons, or only icons.
</p>
</dd>
<dt><i>Auto save</i></dt>
<dd><a name="index-auto-save-1"></a>
<p>Whether unsaved files and projects should be saved automatically before
calling external tools (e.g. before a build).
</p>
</dd>
<dt><i>Save desktop on exit</i></dt>
<dd><a name="index-desktop"></a>
<p>Whether the desktop (size and positions of all windows) should be saved when
exiting.
If you are working with a project created automatically by GPS, the desktop
will not be saved.
</p>
</dd>
<dt><i>Save editor in desktop</i></dt>
<dd><a name="index-desktop-1"></a>
<p>Determines when source editors should be saved in the desktop: <code>Never</code>,
<code>Always</code>, or when a source file is associated with the current project
(<code>From_Project</code>).
</p>
</dd>
<dt><i>Multi language builder</i></dt>
<dd><p>The multi-language builder to be used in case a multi-language or non Ada
project has been loaded.
</p>
<p>By default, <code>gprbuild</code> will be used. Alternatively, its prototype
<code>gprmake</code> can be selected to help the transition, although we do not
recommend it at this stage.
</p>
<p>Finally, if you want to force the use of gnatmake, even for projects
that contain other sources, you can use the <code>gnatmake</code> setting. Note
that Gnatmake will only consider Ada files.
</p>
</dd>
<dt><i>Jump to first location</i></dt>
<dd><a name="index-location-1"></a>
<p>Whether the first entry of the location window should be selected
automatically, and thus whether the corresponding editor should be
immediately open.
</p>
</dd>
<dt><i>Wrap around on next/previous</i></dt>
<dd><a name="index-location-2"></a>
<p>Whether using the <code>Next Tag</code> and <code>Previous Tag</code> actions/menus
should wrap around to the beginning when reaching the end of the category.
The default is to wrap around, as was done in previous GPS versions.
</p>
</dd>
<dt><i>Auto close Locations view</i></dt>
<dd><a name="index-location-3"></a>
<p>Whether the Locations view should be closed automatically when it becomes
empty.
</p>
</dd>
<dt><i>Hyper links</i></dt>
<dd><a name="index-hyper-mode"></a>
<p>Whether to display hyper links in the editors when the Control key is pressed.
See <a href="Navigating-with-hyperlinks.html#Navigating-with-hyperlinks">Navigating with hyperlinks</a>.
</p>
</dd>
<dt><i>Clipboard size</i></dt>
<dd><a name="index-clipboard-1"></a>
<p>This controls the size of the list where all the entries copied into the
clipboard through <code>Edit-&gt;Copy</code> and <code>Edit-&gt;Cut</code> are saved. This list
is navigated through the menu <code>Edit-&gt;Paste</code> and
<code>Edit-&gt;Paste Previous</code>, as described earlier in this guide.
</p>
</dd>
<dt><i>Tool bar style</i></dt>
<dd><a name="index-tool-bar-2"></a>
<p>How the tool bar should be displayed: not at all, with small icons or with
large icons
</p>
</dd>
<dt><i>Show status bar</i></dt>
<dd><a name="index-status-bar-1"></a>
<p>Whether the status bar at the bottom of the GPS window should be displayed.
This status bar contains one or more progress bars while GPS is executing long
actions like a build or a search. These progress bars can be used to monitor
the progress of those actions.
</p>
<p>If you wish to save vertical screen space, you can hide this status
bar. The progress bars will no longer be visible. Instead, you can
display the Task Manager through the <code>Tools-&gt;Views-&gt;Tasks</code> menu,
to get similar information.  This manager can then be put on the right
or left side of the GPS window, for instance just below the Project
View.
</p>
</dd>
<dt><i>Remove policy when fixing code</i></dt>
<dd><a name="index-code-fix"></a>
<p>Prefered way to fix code when parts have to be removed.
<code>Always_Remove</code> means that the code will be removed by GPS.
<code>Always_Comment</code> means that the code will always be commented out.
<code>Propose_Both_Choices</code> will propose a menu with both choices.
</p>
</dd>
<dt><i>Tip of the Day</i></dt>
<dd><a name="index-tip-of-the-day-1"></a>
<p>Whether GPS will display a <i>Tip of the Day</i> dialog at start up.
</p>
</dd>
</dl>

</li><li> <b>Windows</b>

<a name="index-MDI-3"></a>
<a name="index-Multiple-Document-Interface-3"></a>
<p>This section specifies preferences that apply to the <i>Multiple Document
Interface</i> described in <a href="Multiple-Document-Interface.html#Multiple-Document-Interface">Multiple Document Interface</a>.
</p>
<dl compact="compact">
<dt><i>Opaque</i></dt>
<dd><a name="index-opaque"></a>
<p>If True, items will be resized or moved opaquely when not maximized.
</p>
</dd>
<dt><i>Destroy floats</i></dt>
<dd><a name="index-float"></a>
<p>If False, closing the window associated with a floating item will put the item
back in the main GPS window, but will not destroy it. If True, the item is
destroyed.
</p>
</dd>
<dt><i>All floating</i></dt>
<dd><a name="index-float-1"></a>
<p>If True, then all the windows will be floating by default, i.e. be under the
control of your system (Windows) or your window manager (Unix machines). This
replaces the MDI.
</p>
</dd>
<dt><i>Short titles for floats</i></dt>
<dd><a name="index-float-2"></a>
<p>If True, all floating windows will have a short title. In particular, base
file names will be used for editors instead of full names.
</p>
</dd>
<dt><i>Background color</i></dt>
<dd><a name="index-color"></a>
<p>Color to use for the background of the MDI.
</p>
</dd>
<dt><i>Title bar color</i></dt>
<dd><a name="index-color-1"></a>
<p>Color to use for the title bar of unselected items.
</p>
</dd>
<dt><i>Selected title bar color</i></dt>
<dd><a name="index-color-2"></a>
<p>Color to use for the title bar of selected items.
</p>
</dd>
<dt><i>Show title bars</i></dt>
<dd><p>If Always, each window in GPS will have its own title bars, showing some
particular information (like the name of the file edited for editors), and
some buttons to iconify, maximize or close the window. This title bar is
highlighted when the window is the one currently selected.
</p>
<p>If Never, the title bar is not displayed, to save space on the screen. The
tabs of the notebooks will then be highlighted.
</p>
<p>If Central Only, then only the windows in the central area (ie the part that
gets preserved when switching perspective, mostly editors) will have a title
bar. All other windows will not show the title bar. This is often a good way
to save space on the screen: the title bar is useful for editors since it
gives the full name of the file as well as provide an easy handle for drag
and drop operations, whereas the other views do not change position as much
and it is better to save space on the screen by not displaying their title.
</p>
</dd>
<dt><i>Notebook tabs policy</i></dt>
<dd><p>Indicates when the notebook tabs should be displayed. If set to &quot;Never&quot;, you
will have to select the window in the Window menu, or through the keyboard.
If set to &quot;Automatic&quot;, then the tabs will be shown when two or more windows
are stacked.
</p>
</dd>
<dt><i>Notebook tabs position</i></dt>
<dd><p>Indicates where the notebook tabs should be displayed by default. It is
possible to select the position of tabs individually for each notebook
by right-clicking in any of their tabs and chosing a new position in the
contextual menu. This position will be saved as part of the desktop and
restored the next time you restart GPS. However, if you change the value
of this preference, all notebooks will reset the position of their tabs
to match the new value of the preference.
</p>
</dd>
</dl>

</li><li> <b>Editor</b>
<a name="index-editor-1"></a>
<dl compact="compact">
<dt><i>General</i></dt>
<dd>
<dl compact="compact">
<dt><b>Strip blanks</b></dt>
<dd><a name="index-strip-blanks"></a>
<p>Whether the editor should remove trailing blanks when saving a file.
</p>
</dd>
<dt><b>Line terminator</b></dt>
<dd><a name="index-line-terminator"></a>
<p>Choose between <i>Unix</i>, <i>Windows</i> and <i>Unchanged</i> line terminators when
saving files. Choosing <i>Unchanged</i> will use the original line terminator
when saving the file; <i>Unix</i> will use LF line terminators;
<i>Windows</i> will use CRLF line terminators.
</p>
</dd>
<dt><b>Display line numbers</b></dt>
<dd><a name="index-display-line-numbers"></a>
<p>Whether the line numbers should be displayed in file editors.
</p>
</dd>
<dt><b>Display subprogram names</b></dt>
<dd><a name="index-Display-subprogram-names"></a>
<p>Whether the subprogram name should be displayed in the editor&rsquo;s status bar.
</p>
</dd>
<dt><b>Tooltips</b></dt>
<dd><a name="index-tooltip-2"></a>
<p>Whether tool tips should be displayed automatically.
</p>
</dd>
<dt><b>Tooltips timeout</b></dt>
<dd><a name="index-tooltip-timeout"></a>
<p>Time (in milliseconds) before displaying tooltips.
</p>
</dd>
<dt><b>Highlight delimiters</b></dt>
<dd><a name="index-highlight-delimiter"></a>
<p>Determine whether the delimiter matching the character following the
cursor should be highlighted. The list of delimiters includes: <code>{}[]()</code>
</p>
</dd>
<dt><b>Autosave delay</b></dt>
<dd><a name="index-autosave-delay"></a>
<a name="autosave-delay"></a><p>The period (in seconds) after which an editor is automatically saved,
0 if none.
</p>
<p>Each modified file is saved under a file called <code>.#filename#</code>, which is
removed on the next explicit save operation.
</p>
</dd>
<dt><b>Right margin</b></dt>
<dd><a name="index-right-margin"></a>
<p>The right margin to highlight. 0 if none.
This value is also used to implement the <code>Edit-&gt;Refill</code> command.
</p>
</dd>
<dt><b>Block highlighting</b></dt>
<dd><a name="index-block-highlighting"></a>
<p>Whether the editor should highlight the current block.
The current block depends on the programming language, and will include
e.g. procedures, loops, if statements, &hellip;
</p>
</dd>
<dt><b>Block folding</b></dt>
<dd><a name="index-block-folding"></a>
<p>Whether the editor should provide the ability to fold/unfold blocks.
</p>

</dd>
<dt><b>Speed Column Policy</b></dt>
<dd><a name="index-speed-column-policy"></a>
<p>When the Speed Column should be shown on the side of the editors:
</p><dl compact="compact">
<dt><code>Never</code></dt>
<dd><p>The Speed Column is never displayed.
</p>
</dd>
<dt><code>Automatic</code></dt>
<dd><p>The Speed Column is shown whenever lines are highlighted in the editor, for
example to show the current execution point, or lines
containing compilation errors, &hellip;;
It disappears when no lines are highlighted.
</p>
</dd>
<dt><code>Always</code></dt>
<dd><p>The Speed Column is always displayed.
</p>
</dd>
</dl>

</dd>
<dt><b>Use Windows ACL</b></dt>
<dd><p>This is a Windows specific preference which is disabled by default. When
enabled GPS will use the ACL to change the file&rsquo;s write permission. Note
that ACL can&rsquo;t be used on network drives.
</p>
</dd>
<dt><b>External editor</b></dt>
<dd><a name="index-external-editor-1"></a>
<p>The default external editor to use.
</p>
</dd>
<dt><b>Custom editor command</b></dt>
<dd><a name="custom-editor-command"></a><p>Specify the command line for launching a custom editor.
It is assumed that the command will create a new window/terminal as needed.
If the editor itself does not provide this capability (such as vi or pico under
Unix systems), you can use an external terminal command, e.g:
</p>
<div class="smallexample">
<pre class="smallexample">xterm -geo 80x50 -exe vi +%l %f
</pre></div>

<p>The following substitutions are provided:
</p><dl compact="compact">
<dt><code>%l</code></dt>
<dd><p>line to display
</p>
</dd>
<dt><code>%c</code></dt>
<dd><p>column to display
</p>
</dd>
<dt><code>%f</code></dt>
<dd><p>full pathname of file to edit
</p>
</dd>
<dt><code>%e</code></dt>
<dd><p>extended lisp inline command
</p>
</dd>
<dt><code>%p</code></dt>
<dd><p>top level project file name
</p>
</dd>
<dt><code>%%</code></dt>
<dd><p>percent sign (&rsquo;%&rsquo;)
</p></dd>
</dl>

</dd>
<dt><b>Always use external editor</b></dt>
<dd><p>True if all editions should be done with the external editor. This will
deactivate completely the internal editor. False if the external editor
needs to be explicitly called by the user.
</p>
</dd>
<dt><b>Smart completion</b></dt>
<dd><a name="index-smart-completion"></a>
<p>When enabled, GPS loads on startup all the information needed for the
Smart completion to work.
</p>
</dd>
<dt><b>Smart completion timeout</b></dt>
<dd><p>The timeout, expressed in milliseconds, after which the Smart completion
window appears automatically after entering a triggering character, such as &rsquo;.&rsquo;
</p>
</dd>
</dl>

</dd>
<dt><i>Fonts &amp; Colors</i></dt>
<dd><a name="index-font-2"></a>
<a name="index-color-3"></a>

<dl compact="compact">
<dt><b>Default</b></dt>
<dd><p>The default font, default foreground and default background colors used
in the source editor.
</p>
</dd>
<dt><b>Block</b></dt>
<dd><p>Font variant and colors used to highlight blocks (subprograms, task, entries,
...) in declarations.
</p>
</dd>
<dt><b>Type</b></dt>
<dd><p>Font variant and colors used to highlight types in declarations.
</p>
</dd>
<dt><b>Keywords</b></dt>
<dd><p>Font variant and colors used to highlight keywords.
</p>
</dd>
<dt><b>Comments</b></dt>
<dd><p>Font variant and colors used to highlight comments.
Setting the color to white will set a transparent color.
</p>
</dd>
<dt><b>Annotated  Comments</b></dt>
<dd><p>Font variant and colors used to highlight annotated comments.
Only relevant to Ada currently. Annotated comments are comments immediately
followed by a special character, e.g. <code>#[]</code>.
Setting the color to white will set a transparent color.
</p>
</dd>
<dt><b>Strings</b></dt>
<dd><p>Font variant and colors used to highlight strings.
Setting the color to white will set a transparent color.
</p>
</dd>
<dt><b>Current line color</b></dt>
<dd><p>Color for highlighting the current line. Leave it to blank for no highlighting.
Setting the color to white will set a transparent color.
</p>
</dd>
<dt><b>Draw current line as a thin line</b></dt>
<dd><p>Whether to use a thin line rather than full background highlighting on the
current line.
</p>
</dd>
<dt><b>Current block color</b></dt>
<dd><p>Color for highlighting the current source block.
</p>
</dd>
<dt><b>Delimiter highlighting color</b></dt>
<dd><p>Color for highlighting delimiters.
</p>
</dd>
<dt><b>Search results highlighting</b></dt>
<dd><p>Color for highlighting the search results in the text of source editors.
</p>
</dd>
<dt><b>Cursor color</b></dt>
<dd><p>Color used for the cursor in editors and interactive consoles
</p>
</dd>
<dt><b>Cursor aspect ratio</b></dt>
<dd><p>Defines the size of the cursor, relatively to characters. 100 means the
cursor will occupy the same size as a character, 10 means it will only
occupy 10% of the size occupies by a character.
</p>
</dd>
</dl>

</dd>
<dt><i>Ada</i></dt>
<dd><a name="index-Ada-6"></a>

<dl compact="compact">
<dt><b>Auto indentation</b></dt>
<dd><a name="index-indentation-1"></a>
<p>How the editor should indent Ada sources.
None means no indentation; Simple means that indentation from the previous
line is used for the next line; Extended means that a language specific
parser is used for indenting sources.
</p>
</dd>
<dt><b>Use tabulations</b></dt>
<dd><a name="index-tabulation"></a>
<p>Whether the editor should use tabulations when indenting.
Note that this preference does not modify the <tt class="key">Tab</tt> key which will still
insert Tab characters. Consider also the <code>/Edit/Insert Tab With Spaces</code> key
shortcut which can be mapped (to e.g. <tt class="key">Tab</tt>) via <a href="The-Key-Manager-Dialog.html#The-Key-Manager-Dialog">The Key Manager Dialog</a>. Finally, another alternative is to reconfigure the default key
binding for the automatic indentation action: by default, it is mapped to
<tt class="key">Ctrl-Tab</tt>
and can be changed to <tt class="key">Tab</tt> by modifying the <code>/Edit/Format Selection</code>
action from <a href="The-Key-Manager-Dialog.html#The-Key-Manager-Dialog">The Key Manager Dialog</a>.
</p>
</dd>
<dt><b>Default indentation</b></dt>
<dd><a name="index-indentation-level"></a>
<p>The number of spaces for the default Ada indentation.
</p>
</dd>
<dt><b>Continuation lines</b></dt>
<dd><a name="index-continuation-line"></a>
<p>The number of extra spaces for continuation lines.
</p>
</dd>
<dt><b>Declaration lines</b></dt>
<dd><a name="index-declaration-line"></a>
<p>The number of extra spaces for multiple line declarations.
For example, using a value of 4, here is how the following code would be
indented:
</p>
<a name="index-example-3"></a>
<div class="smallexample">
<pre class="smallexample">variable1,
    variable2,
    variable3 : Integer;
</pre></div>

</dd>
<dt><b>Conditional continuation lines</b></dt>
<dd><a name="index-conditional-line"></a>
<p>The number of extra spaces used to indent multiple lines conditionals
within parentheses.
</p>
<p>For example, when this preference is set to 1 (the default), continuation
lines are indented based on the previous parenthesis plus one space:
</p>
<a name="index-example-4"></a>
<div class="smallexample">
<pre class="smallexample">if (Condition1
    and then Condition2)
then
</pre></div>

<p>When this preference is set to 3, this gives:
</p>
<a name="index-example-5"></a>
<div class="smallexample">
<pre class="smallexample">if (Condition1
      and then Condition2)
then
</pre></div>

</dd>
<dt><b>Record indentation</b></dt>
<dd><a name="index-record-indentation"></a>
<p>The number of extra spaces for record definitions, when the <code>record</code>
keyword is on its own line.
</p>
<p>For example, when this preference is set to 3 (the default), the
following sample will be indented as:
</p>
<a name="index-example-6"></a>
<div class="smallexample">
<pre class="smallexample">type T is
   record
      F : Integer;
   end record;
</pre></div>

<p>When this preference is set to 1, this gives:
</p>
<a name="index-example-7"></a>
<div class="smallexample">
<pre class="smallexample">type T is
 record
    F : Integer;
 end record;
</pre></div>

</dd>
<dt><b>Case indentation</b></dt>
<dd><a name="index-case-indentation"></a>
<p>Whether GPS should indent case statements with an extra level, as used in the
Ada Reference Manual, e.g:
</p>
<a name="index-example-8"></a>
<div class="smallexample">
<pre class="smallexample">case Value is
   when others =&gt;
      null;
end case;
</pre></div>

<p>If this preference is set to <code>Non_Rm_Style</code>, this would be indented as:
</p>
<a name="index-example-9"></a>
<div class="smallexample">
<pre class="smallexample">case Value is
when others =&gt;
   null;
end case;
</pre></div>

<p>By default (<code>Automatic</code>), GPS will choose to indent with an extra
level or not based on the first <code>when</code> construct: if the first
<code>when</code> is indented by an extra level, the whole case statement will
be indented following the RM style.
</p>
</dd>
<dt><b>Casing policy</b></dt>
<dd><p>The way the editor will handle the case settings below.
<code>Disabled</code> no auto-casing will be done;
<code>End_Of_Line</code> auto-casing will be done when hitting <tt class="key">Enter</tt> key;
<code>End_Of_Word</code> auto-casing will be done word-by-word while typing;
<code>On_The_Fly</code> auto-casing will be done character-by-character while typing.
For the <code>End_Of_Line</code>, <code>End_Of_Word</code> and <code>On_The_Fly</code> policies
it is always possible to force the casing of the current line by pressing the
indentation key (<tt class="key">Ctrl-Tab</tt> by default).
</p>
<p>It is also possible to disable the casing for a single character
(action <code>No Casing/indentation on Next Key</code>, default <tt class="key">Ctrl-Q</tt>) or
temporarily (action <code>Toggle Auto Casing/indentation</code>,
default <tt class="key">Alt-Q</tt>).
</p>
</dd>
<dt><b>Reserved word casing</b></dt>
<dd><p>How the editor should handle reserved words casing.
<code>Unchanged</code> will keep the casing as-is;
<code>Upper</code> will change the casing of all reserved words to upper case;
<code>Lower</code> will change the casing to lower case;
<code>Mixed</code> will change the casing to mixed case (all characters to
lower case except first character and characters after an underscore
which are set to upper case);
<code>Smart_Mixed</code> As above but do not force upper case characters to
lower case.
</p>
</dd>
<dt><b>Identifier casing</b></dt>
<dd><p>How the editor should handle identifiers casing.
The values are the same as for the <i>Reserved word casing</i> preference.
</p>
</dd>
<dt><b>Format operators/delimiters</b></dt>
<dd><p>Whether the editor should add extra spaces around operators and delimiters
if needed.
If enabled, an extra space will be added when needed in the following cases:
before an opening parenthesis;
after a closing parenthesis, comma, semicolon;
around all Ada operators (e.g. <code>&lt;=</code>, <code>:=</code>, <code>=&gt;</code>, &hellip;)
</p>
</dd>
<dt><b>Align colons in declarations</b></dt>
<dd><p>Whether the editor should automatically align colons in declarations and
parameter lists. Note that the alignment is computed by taking into account
the current buffer up to the current line (or end of the current selection),
so if declarations continue after the current line, you can select
the declarations lines and hit the reformat key.
</p>
</dd>
<dt><b>Align associations on arrows</b></dt>
<dd><p>Whether the editor should automatically align arrows in associations
(e.g. aggregates or function calls). See also previous preference.
</p>
</dd>
<dt><b>Align declarations after colon</b></dt>
<dd><p>Whether the editor should align continuation lines in variable declarations
based on the colon character.
</p>
<p>Consider the following code:
</p>
<a name="index-example-10"></a>
<div class="smallexample">
<pre class="smallexample">Variable : constant String :=
  &quot;a string&quot;;
</pre></div>

<p>If this preference is enabled, it will be indented as follows:
</p>
<a name="index-example-11"></a>
<div class="smallexample">
<pre class="smallexample">Variable : constant String :=
             &quot;a string&quot;;
</pre></div>

</dd>
<dt><b>Indent comments</b></dt>
<dd><p>Whether to indent lines containing only comments and blanks, or to keep
these lines unchanged.
</p>
</dd>
<dt><b>Align comments on keywords</b></dt>
<dd><p>Whether to align comment lines following <code>record</code> and
<code>is</code> keywords immediately with no extra space.
</p>
<p>When enabled, the following code will be indented as:
</p>
<a name="index-example-12"></a>
<div class="smallexample">
<pre class="smallexample">package P is
--  Comment

   [...]
end P;
</pre></div>

<p>When disabled, the indentation will be:
</p>
<a name="index-example-13"></a>
<div class="smallexample">
<pre class="smallexample">package P is
   --  Comment

   [...]
end P;
</pre></div>

</dd>
</dl>

</dd>
<dt><i>C &amp; C++</i></dt>
<dd><a name="index-C-6"></a>
<a name="index-C_002b_002b-5"></a>

<dl compact="compact">
<dt><b>Auto indentation</b></dt>
<dd><a name="index-indentation-2"></a>
<p>How the editor should indent C/C++ sources.
None means no indentation; Simple means that indentation from the previous
line is used for the next line; Extended means that a language specific
parser is used for indenting sources.
</p>
</dd>
<dt><b>Use tabulations</b></dt>
<dd><a name="index-tabulation-1"></a>
<p>Whether the editor should use tabulations when indenting. If True,
the editor will replace each occurrence of eight characters by a tabulation
character.
</p>
</dd>
<dt><b>Default indentation</b></dt>
<dd><a name="index-indentation-3"></a>
<p>The number of spaces for the default indentation.
</p>
</dd>
<dt><b>Indent comments</b></dt>
<dd><p>Whether to indent lines containing only comments and blanks, or to keep
these lines unchanged.
</p>
</dd>
</dl>

</dd>
</dl>

</li><li> <b>Debugger</b>
<a name="index-debugger-6"></a>
<dl compact="compact">
<dt><i>Preserve State on Exit</i></dt>
<dd><a name="index-breakpoint-4"></a>
<p>If this preference is enabled, the debugger will automatically save breakpoints
when it exists, and restore them the next time the same executable is debugged.
This is a convenient way to work on an executable, where the typical usage
looks like compile, debug, compile, debug, &hellip;
</p>
<p>When the preference is enabled, the debugger will also preserve the contents
of the data window whenever it is closed. Reopening the window either during
the same debugger session, or automatically when a new debugger is started
on the same executable, will recreate the same boxes within the data window.
</p>
</dd>
<dt><i>Debugger Windows</i></dt>
<dd><a name="index-debugger-windows"></a>
<p>This preference controls what happens to debugger-related windows, like the
call stack, the data window, the tasks view,..., when the debugger is
terminated. There are three possible behavior:
</p><ul>
<li> Close Windows

<p>In this case, all these windows are closed. This saves memory and space on
the screen, but you will need to explicitly reopen them and put them in the
right location on the desktop the next time you start a debugger session.
</p>
</li><li> Keep Windows

<p>In this case, the windows are cleared, but kept on the desktop. When you
start a new debugger session, the windows will be automatically reused. This
ensures that you won&rsquo;t have to reopen and reposition them, but takes space
on your screen
</p>
</li><li> Hide Windows

<p>The windows are cleared, and hidden. When you start a new debugger session,
they are automatically made visible again and reused. This also ensures you
will not have to reopen and reposition them, but requires a bit of memory.
If you move some windows around while these windows are hidden, they might
reappear in unexpected location the next time, although you then just have
to move them.
</p>
</li></ul>

</dd>
<dt><i>Break on exceptions</i></dt>
<dd><a name="index-breakpoint-5"></a>
<a name="index-exception"></a>
<p>Specifies whether a breakpoint on all exceptions should be set by
default when loading a program. This setup is only taken into account
when a new debugger is initialized, and will not modify a running
debugger (use the breakpoint editor for running debuggers).
</p>
</dd>
<dt><i>Execution window</i></dt>
<dd><a name="index-execution-2"></a>
<a name="index-tty"></a>
<p>Specifies whether the debugger should create a separate execution
window for the program being debugged.
</p>
<p>Note that this preference cannot be taken into account for the current
debug session: you need to terminate the current debug session and restart
a new one.
</p>
<p>If true, a separate console will be created. Under Unix systems, this
console is another window in the bottom part of the main window; under
Windows, this is a separate window created by the underlying gdb, since
Windows does not have the notion of separate terminals (aka ttys).
</p>
<p>Note that in this mode under Windows, the <code>Debug-&gt;Interrupt</code> menu
will only interrupt the debugged program with recent versions of gdb.
If you are using older versions of gdb, you need to hit
<tt class="key">Ctrl-C</tt> in the separate execution window to interrupt it while it is
running. Note also that this separate execution window uses the default
system-wide console properties (the size of the window, the
colors...). It is possible to change those properties using e.g. the
default console menu (top-left of the console) on Windows XP.
</p>
<p>If false, no execution window will be created. The debugger assumes that the
program being debugged does not require input, or that if it does, input
is handled outside GPS. For example, when you attach to a running process,
this process already has a separate associated terminal.
</p>
</dd>
<dt><i>Show lines with code</i></dt>
<dd><p>Specifies whether the source editor should display blue dots for lines
that contain code. If set to <i>False</i>, gray dots will be displayed instead
on each line, allowing breakpoint on any line. Disabling this option provides
a faster feedback, since GPS does not need to query the debugger about which
lines contain code.
</p>
</dd>
<dt><i>Detect aliases</i></dt>
<dd><a name="index-aliases-1"></a>
<p>If enabled, do not create new items when an item with the same address is
already present on the canvas.
</p>
</dd>
<dt><i>Assembly range size</i></dt>
<dd><a name="index-range-size"></a>
<p>Number of assembly lines to display in the initial display of the assembly
window. If the size is 0, then the whole subprogram is displayed, but this
can take a very long time on slow machines.
</p>
</dd>
<dt><i>Current assembly line</i></dt>
<dd><p>Color used to highlight the assembly code for the current line.
</p>
</dd>
<dt><i>Color highlighting</i></dt>
<dd><a name="index-color-4"></a>
<p>Color used for highlighting in the debugger console.
</p>
</dd>
<dt><i>Clickable item</i></dt>
<dd><p>Indicates color to be used for the items that are click-able (e.g pointers).
</p>
</dd>
<dt><i>Changed data</i></dt>
<dd><p>Indicates color to be used to highlight fields in the data window that have
changed since the last update.
</p>
</dd>
<dt><i>Memory color</i></dt>
<dd><p>Color used by default in the memory view window.
</p>
</dd>
<dt><i>Memory highlighting</i></dt>
<dd><p>Color used for highlighted items in the memory view.
</p>
</dd>
<dt><i>Memory selection</i></dt>
<dd><p>Color used for selected items in the memory view.
</p>
</dd>
<dt><i>Item name</i></dt>
<dd><p>Indicates the font to be used for the name of the item in the data window.
</p>
</dd>
<dt><i>Item type</i></dt>
<dd><p>Indicates font to be used to display the type of the item in the data window.
</p>
</dd>
<dt><i>Max item width</i></dt>
<dd><p>The maximum width an item can have.
</p>
</dd>
<dt><i>Max item height</i></dt>
<dd><p>The maximum height an item can have.
</p>
</dd>
</dl>

</li><li> <b>External Commands</b>
<a name="index-helper"></a>
<a name="index-external-commands"></a>
<dl compact="compact">
<dt><i>List processes</i></dt>
<dd><p>Command used to list processes running on the machine.
</p>
</dd>
<dt><i>Remote shell</i></dt>
<dd><a name="index-remote-shell"></a>
<p>Program used to run a process on a remote machine. You can specify arguments,
e.g. <code>rsh -l user</code>
</p>
</dd>
<dt><i>Remote copy</i></dt>
<dd><a name="index-remote-copy"></a>
<p>Program used to copy a file from a remote machine. You can specify arguments,
e.g. <code>rcp -l user</code>
</p>
</dd>
<dt><i>Execute command</i></dt>
<dd><a name="index-execution-3"></a>
<p>Program used to execute commands externally.
</p>
</dd>
<dt><i>HTML Browser</i></dt>
<dd><a name="index-html"></a>
<p>Only used under Unix, not relevant under Windows where the default HTML
browser is used.
Program used to execute view HTML files, for instance the documentation.
Empty by default, which means that GPS will try to find a suitable HTML
browser automatically. Only change the value if GPS cannot find a HTML
browser, or if the browser found is not your preferred one.
</p>
</dd>
<dt><i>Print command</i></dt>
<dd><a name="index-print-2"></a>
<a name="index-a2ps"></a>
<a name="index-PrintFile"></a>
<a name="Print-Command"></a><p>External program used to print files.
</p>
<p>This program is required under Unix systems in order to print, and is set to
<code>a2ps</code> by default.
If <code>a2ps</code> is not installed on your system, you can download it
from <a href="ftp://ftp.enst.fr/pub/unix/a2ps/">ftp://ftp.enst.fr/pub/unix/a2ps/</a>, although other printing programs
such as <code>lp</code> can be specified instead.
</p>
<p>Under Windows systems, this program is optional and is empty by default, since
a built-in printing is provided. An external tool will be used if specified,
such as the PrintFile freeware utility available from
<a href="http://www.lerup.com/printfile/descr.html">http://www.lerup.com/printfile/descr.html</a>
</p>
</dd>
</dl>

</li><li> <b>Search</b>
<a name="index-search-4"></a>
<dl compact="compact">
<dt><b>Confirmation for &quot;Replace all&quot;</b></dt>
<dd><a name="index-replace-2"></a>
<p>Enable or disable the confirmation popup for the replace all action.
</p>
</dd>
<dt><b>Close on Match</b></dt>
<dd><a name="index-search-5"></a>
<p>If this option is enabled, the search window will be closed when a match is
found.
</p>
</dd>
<dt><b>Select on Match</b></dt>
<dd><a name="index-search-6"></a>
<p>If this option is enabled, the focus will be given to the editor when a match
is found.
</p>
</dd>
<dt><b>Preserve Search Context</b></dt>
<dd><a name="index-search-7"></a>
<p>If this option is enabled, the contents of the &quot;Look in:&quot; field will be
preserved between consecutive searches in files.
</p></dd>
</dl>

</li><li> <b>Browsers</b>
<a name="index-browsers-2"></a>
<dl compact="compact">
<dt><i>General</i></dt>
<dd>
<dl compact="compact">
<dt><b>Selected item color</b></dt>
<dd><a name="index-color-5"></a>
<p>Color to use to draw the selected item.
</p>
</dd>
<dt><b>Background color</b></dt>
<dd><a name="index-color-6"></a>
<p>Color used to draw the background of the browsers.
</p>
</dd>
<dt><b>Hyper link color</b></dt>
<dd><a name="index-color-7"></a>
<p>Color used to draw the hyper links in the items.
</p>
</dd>
<dt><b>Selected link color</b></dt>
<dd><a name="index-color-8"></a>
<p>Color to use for links between selected items.
</p>
</dd>
<dt><b>Default link color</b></dt>
<dd><a name="index-color-9"></a>
<p>Color used to draw the links between unselected items.
</p>
</dd>
<dt><b>Ancestor items color</b></dt>
<dd><a name="index-color-10"></a>
<p>Color to use for the background of the items linked to the selected item.
</p>
</dd>
<dt><b>Offspring items color</b></dt>
<dd><a name="index-color-11"></a>
<p>Color to use for the background of the items linked from the selected item.
</p>
</dd>
<dt><b>Vertical layout</b></dt>
<dd><a name="index-vertical-layout"></a>
<p>Whether the layout of the graph should be vertical (<i>True</i>) or
horizontal (<i>False</i>). This setting applies to most browsers (call graph
for instance), but does not apply to the entities browsers.
</p>
</dd>
</dl>

</dd>
<dt><i>File Dependencies</i></dt>
<dd>
<dl compact="compact">
<dt><b>Show system files</b></dt>
<dd><a name="index-Ada-7"></a>
<a name="index-C-7"></a>
<p>Whether the system files (Ada runtime or standard C include files) should be
visible in the browser.
</p>
</dd>
<dt><b>Show implicit dependencies</b></dt>
<dd><a name="index-implicit-dependency"></a>
<a name="index-dependency"></a>
<p>If False, then only the explicit dependencies are shown in the browser.
Otherwise, all dependencies, even implicit, are displayed.
</p>
</dd>
</dl>

</dd>
</dl>

</li><li> <b>VCS</b>
<a name="index-vcs"></a>

<dl compact="compact">
<dt><i>Implicit status</i></dt>
<dd><a name="index-Implicit-status"></a>
<p>Whether a status action can be launched as part of another action. For
example to get the revision numbers of new files after an update
command. If the network connection with the repository is slow
disabling this command can speed-up the VCS actions.
</p>
</dd>
<dt><i>ClearCase module</i></dt>
<dd><a name="index-ClearCase-module"></a>
<p>Whether the built-in ClearCase (see <a href="Version-Control-System.html#Version-Control-System">Version Control System</a>)
module is activated or disabled.
</p>
</dd>
<dt><i>Default VCS</i></dt>
<dd><a name="index-Default-VCS"></a>
<p>The default VCS to use when the project does not define a VCS.
</p>
</dd>
</dl>

</li><li> <b>Visual diff</b>
<a name="index-visual-diff-2"></a>
<a name="index-file-comparison"></a>

<p>Note that in order to perform visual comparison between files, GPS
needs to call external tool (not distributed with GPS) such as <code>diff</code>
or <code>patch</code>. These tools are usually found on most unix systems, and
may not be available by default on other OSes. Under Windows, you can
download them from one of the unix toolsets
available, such as msys (<a href="http://www.mingw.org">http://www.mingw.org</a>) or
cygwin (<a href="http://www.cygwin.com">http://www.cygwin.com</a>).
</p>
<dl compact="compact">
<dt><i>mode</i></dt>
<dd><a name="index-diff"></a>
<p>How GPS displays visual diffs between two files:
</p>
<dl compact="compact">
<dt><b>Side_By_Side</b></dt>
<dd><p>Editors are displayed side-by-side; new editors are created as needed
</p>
</dd>
<dt><b>Unified</b></dt>
<dd><p>No new editor is created, and changes are displayed directly in the reference
editor.
</p>
</dd>
</dl>

</dd>
<dt><i>Diff command</i></dt>
<dd><a name="index-_002du"></a>
<a name="index-_002dc"></a>
<p>Command used to compute differences between two files.
Arguments can also be specified. The visual diff expects a standard diff
output with no context (that is, no <code>-c</code> nor <code>-u</code> switch).
Arguments of interest may include (this will depend on the version of diff
used):
</p>
<dl compact="compact">
<dt><b>-b</b></dt>
<dd><p>Ignore changes in amount of white space.
</p>
</dd>
<dt><b>-B</b></dt>
<dd><p>Ignore changes that just insert or delete blank lines.
</p>
</dd>
<dt><b>-i</b></dt>
<dd><p>Ignore changes in case; consider upper and lower case letters equivalent.
</p>
</dd>
<dt><b>-w</b></dt>
<dd><p>Ignore white space when comparing lines.
</p>
</dd>
</dl>

</dd>
<dt><i>Patch command</i></dt>
<dd><a name="index-patch"></a>
<p>Command used to apply a patch. Arguments can also be specified.
This command is used internally by GPS to perform the visual comparison on
versioned files (e.g. when performing a comparison with a version control
system).
</p>
<p>This command should be compatible with the <code>GNU patch</code> utility.
</p>
</dd>
<dt><i>Use old diff</i></dt>
<dd><a name="index-old-diff"></a>
<p>Use the old version of the visual comparison.
</p>
</dd>
<dt><i>Diff3 command</i></dt>
<dd><a name="index-diff3"></a>
<p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
Command used to query a 3-way diff. See <i>Diff command</i> for a description
of the parameters.
</p>
</dd>
<dt><i>Default color</i></dt>
<dd><p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
The color used to indicate lines on which there is a difference, in the
&quot;reference&quot; editor.
</p>
</dd>
<dt><i>Old color</i></dt>
<dd><p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
The color used to indicate spaces used by lines not present in one of the
editors in a 3-way diff and present in the other editors.
</p>
</dd>
<dt><i>Append color</i></dt>
<dd><p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
The color used to display the lines that are present in an editor but not in the
reference editor.
</p>
</dd>
<dt><i>Remove color</i></dt>
<dd><p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
The color used to display the lines that are present in the reference editor
but not in other editors.
</p>
</dd>
<dt><i>Change color</i></dt>
<dd><p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
The color used to display the lines that have changed between the reference
editor and the other editors.
</p>
</dd>
<dt><i>Fine change color</i></dt>
<dd><p>This item is only displayed if the preference <i>Use old diff</i> is disabled.
The color used to highlight fine differences within a modified line.
</p>
</dd>
<dt><i>Context length</i></dt>
<dd><a name="index-context-length"></a>
<p>This item is only displayed if the preference <i>Use old diff</i> is enabled.
The number of lines displayed before and after each chunk of differences.
Specifying -1 will display the whole file.
</p>
</dd>
</dl>

</li><li> <b>Messages</b>
<a name="index-messages-3"></a>
<dl compact="compact">
<dt><i>Color highlighting</i></dt>
<dd><a name="index-color-12"></a>
<p>Color used to highlight text in the messages window.
</p>
</dd>
<dt><i>Color highlighting</i></dt>
<dd><a name="index-errors-1"></a>
<p>Color used to highlight lines causing compilation errors/warnings in the
source editors. When this color is set to white, the errors/warnings are
not highlighted. (<a href="Compilation_002fBuild.html#Compilation_002fBuild">Compilation/Build</a>)
</p>
</dd>
<dt><i>File pattern</i></dt>
<dd><a name="index-file-pattern"></a>
<a name="index-location-4"></a>
<p>Pattern used to detect file locations and the type of the output from the
messages window.
This is particularly useful when using an external tool such as a compiler
or a search tool, so that GPS will highlight and allow navigation through source
locations. This is a standard system V regular expression containing from two
to five parenthesized subexpressions corresponding to the file, line, column,
warnings or style error patterns.
</p>
</dd>
<dt><i>File index</i></dt>
<dd><a name="index-file-index"></a>
<p>Index of filename in the file pattern.
</p>
</dd>
<dt><i>Line index</i></dt>
<dd><a name="index-line-index"></a>
<p>Index of the line number in the file pattern.
</p>
</dd>
<dt><i>Column index</i></dt>
<dd><a name="index-column-index"></a>
<p>Index of the column number in the file pattern.
</p>
</dd>
<dt><i>Warning index</i></dt>
<dd><a name="index-warning-index"></a>
<p>Index of the warning identifier in the file pattern.
</p>
</dd>
<dt><i>Style index</i></dt>
<dd><a name="index-column-index-1"></a>
<p>Index of the style error identifier in the file pattern.
</p>
</dd>
</dl>

</li><li> <b>Project</b>
<dl compact="compact">
<dt><i>Relative project paths</i></dt>
<dd><a name="index-relative-project-path"></a>
<p>Whether paths should be absolute or relative when the projects are modified.
</p>
</dd>
<dt><i>Fast Project Loading</i></dt>
<dd><a name="index-fast-project-loading"></a>
<p>If the project respects a number of restrictions, activating the preference
will provide major speed up when GPS parses the project. This is especially
noticeable if the source files are on a network drive.
</p>
<p>GPS assumes that the following restricitions are true when the preference
is activated. If this isn&rsquo;t the case, no error is reported, and only minor
drawacks will be visible in GPS (no detection that two files are the same
if one of them is a symbolic link for instance, although GPS will still
warn you if you are trying to overwrite a file modified on the disk).
</p>
<p>The restrictions are the following:
</p><ul class="no-bullet">
<li>- Symbolic links shouldn&rsquo;t be used in the project.
  More precisely, you can only have symbolic links that point to files
  outside of the project, but not to another file in the project

</li><li>- Directories can&rsquo;t have source names.
  No directory name should match the naming scheme defined in the
  project. For instance, if you are using the default GNAT naming scheme,
  you cannot have directories with names ending with &quot;.ads&quot; or &quot;.adb&quot;

</li></ul>

</dd>
<dt><i>Load Xref info on project load</i></dt>
<dd><a name="index-load-xref-info-on-project-load"></a>
<p>Whether the Xref information should be automatically loaded into memory when
a new project is loaded. See <a href="Support-for-Cross_002dReferences.html#Support-for-Cross_002dReferences">Support for Cross-References</a>.
</p>
</dd>
<dt><i>Hidden directories pattern</i></dt>
<dd><a name="index-hidden-directories-pattern"></a>
<p>A regular expression used to match hidden directories. Such directories
are not displayed by default in the project view, and are not taken into
account for VCS operations working on directories.
</p>
</dd>
</dl>

</li><li> <b>Outline</b>
<a name="Outline-Preferences"></a>
<dl compact="compact">
<dt><i>Font</i></dt>
<dd>
<p>You can choose a specific font for the outline view. Typically, this will
be used to use a slightly smaller font than in the editor, so that you can
see more entities at once on the screen.
</p>
</dd>
<dt><i>Show Profiles</i></dt>
<dd>
<p>For some of the languages, in particular Ada, GPS can display the profile
(list of parameters) for the subprograms. This can be used to differentiate
between overloaded entities (ie entities with the same name). Disabling
this preference will only show the entity name.
</p>
</dd>
<dt><i>Sort alphabetically</i></dt>
<dd>
<p>If this preference is activated, the entities will be sorted alphabetically
in the outline view. If disabled, they will be displayed in the order they are
found in the source file.
</p>
</dd>
<dt><i>Link with Editor</i></dt>
<dd>
<p>If this option is set, the current subprogram will be selected in the outline
view every time the cursor position changes in the current editor. This
option requires some computation for GPS, and you might want to avoid the
slow down by disabling it.
</p>
</dd>
<dt><i>Show file name</i></dt>
<dd>
<p>If this option is set, the outline view will show the name of the file on its
first line, and indent slightly all following lines. If this option is unset,
this will save some screen real estate, but you will have to look at the
current editor to see what file is descrived in the Outline View.
</p>
</dd>
</dl>

</li><li> <b>Documentation</b>
<a name="Documention-Preferences"></a>
<p>This section specifies preferences that apply to the
<i>Documentation Generator</i>. <a href="Documentation-Generation.html#Documentation-Generation">Documentation Generation</a> for more
information.
</p>
<dl compact="compact">
<dt><i>Process body files</i></dt>
<dd>
<p>If this preference is enabled, implementation files will be processed.
Otherwise, only the specification files will.
</p>
</dd>
<dt><i>Show private entities</i></dt>
<dd>
<p>By default, no documentation is generated for private entities.
Enabling this preference will change this behavior.
</p>
</dd>
<dt><i>Call graph</i></dt>
<dd>
<p>If enabled, the documentation tool will compute and take advantage of source
references to e.g generate call graph information.
Activating this option will slow down the documentation generation process.
</p>
</dd>
<dt><i>Up-to-date files only</i></dt>
<dd>
<p>If enabled, only files having up-to-date cross references information will be
documented.
</p>
</dd>
<dt><i>Comments filter regexp</i></dt>
<dd>
<p>A regular expression used to filter to comments found in the source code before
using them for generating documentation. For example &quot;^!.*&quot; will remove all
comments starting with &rsquo;!&rsquo;.
</p>
</dd>
<dt><i>Spawn a browser</i></dt>
<dd>
<p>If enabled, a browser is spawned after each documentation generation to view
the generated files. This browser is not spawned if disabled.
</p>
</dd>
<dt><i>Find xrefs in comments</i></dt>
<dd>
<p>If enabled, GPS will try to find references to entities in comments, and
 generate links to them when generating the documentation.
</p>
</dd>
</dl>

</li><li> <b>Coverage Analysis</b>
<a name="Coverage-Analysis-Preferences"></a>
<dl compact="compact">
<dt><i>Coverage toolchain</i></dt>
<dd>
<p>Select which coverage toolchain (<code>gcov</code> or <code>xcov</code>) to use from
the <code>Tools-&gt;Coverage</code> menu.
</p>
</dd>
</dl>

</li></ul>

<hr>
<div class="header">
<p>
Next: <a href="GPS-Themes.html#GPS-Themes" accesskey="n" rel="next">GPS Themes</a>, Up: <a href="Customizing-and-Extending-GPS.html#Customizing-and-Extending-GPS" accesskey="u" rel="up">Customizing and Extending GPS</a> &nbsp; [<a href="Index-table.html#Index-table" title="Index" rel="index">Index</a>]</p>
</div>



</body>
</html>
gnat-gps-doc 5.0-16 / usr / share / doc / gnat-gps / html / The-Preferences-Dialog.html
