This dialog, available through the menu Edit->Preferences, allows you to
modify the global preferences of GPS.
To enable the new preferences, you simply need to confirm by pressing
the OK button. To test your changes, you can use the Apply
button. Pressing the Cancel button will undo all your changes.
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.
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.
This page allows you to quickly change the current settings for GPS, including preferences, key bindings, menus...; See GPS Themes for more information on themes. It is only displayed when there are themes registered.
This preference indicates the file system encoding in use. It defaults to
ISO-8859-1, which corresponds to western european characters.
Never,
Always, or when a source file is associated with the current project
(From_Project).
By default, gprbuild will be used. Alternatively, its prototype
gprmake can be selected to help the transition, although we do not
recommend it at this stage.
Finally, if you want to force the use of gnatmake, even for projects
that contain other sources, you can use the gnatmake setting. Note
that Gnatmake will only consider Ada files.
Next Tag and Previous Tag 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.
Edit->Copy and Edit->Cut are saved. This list
is navigated through the menu Edit->Paste and
Edit->Paste Previous, as described earlier in this guide.
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 Tools->Views->Tasks 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.
Always_Remove means that the code will be removed by GPS.
Always_Comment means that the code will always be commented out.
Propose_Both_Choices will propose a menu with both choices.
This section specifies preferences that apply to the Multiple Document Interface described in Multiple Document Interface.
If Never, the title bar is not displayed, to save space on the screen. The tabs of the notebooks will then be highlighted.
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.
{}[]()
Each modified file is saved under a file called .#filename#, which is
removed on the next explicit save operation.
Edit->Refill command.
NeverAutomaticAlwaysxterm -geo 80x50 -exe vi +%l %f
The following substitutions are provided:
%l%c%f%e%p%%#[].
Setting the color to white will set a transparent color.
/Edit/Insert Tab With Spaces key
shortcut which can be mapped (to e.g. <Tab>) via The Key Manager Dialog. Finally, another alternative is to reconfigure the default key
binding for the automatic indentation action: by default, it is mapped to
<Ctrl-Tab>
and can be changed to <Tab> by modifying the /Edit/Format Selection
action from The Key Manager Dialog.
variable1,
variable2,
variable3 : Integer;
For example, when this preference is set to 1 (the default), continuation lines are indented based on the previous parenthesis plus one space:
if (Condition1
and then Condition2)
then
When this preference is set to 3, this gives:
if (Condition1
and then Condition2)
then
record
keyword is on its own line.
For example, when this preference is set to 3 (the default), the following sample will be indented as:
type T is
record
F : Integer;
end record;
When this preference is set to 1, this gives:
type T is
record
F : Integer;
end record;
case Value is
when others =>
null;
end case;
If this preference is set to Non_Rm_Style, this would be indented as:
case Value is
when others =>
null;
end case;
By default (Automatic), GPS will choose to indent with an extra
level or not based on the first when construct: if the first
when is indented by an extra level, the whole case statement will
be indented following the RM style.
Disabled no auto-casing will be done;
End_Of_Line auto-casing will be done when hitting <Enter> key;
End_Of_Word auto-casing will be done word-by-word while typing;
On_The_Fly auto-casing will be done character-by-character while typing.
For the End_Of_Line, End_Of_Word and On_The_Fly policies
it is always possible to force the casing of the current line by pressing the
indentation key (<Ctrl-Tab> by default).
It is also possible to disable the casing for a single character
(action No Casing/indentation on Next Key, default <Ctrl-Q>) or
temporarily (action Toggle Auto Casing/indentation,
default <Alt-Q>).
Unchanged will keep the casing as-is;
Upper will change the casing of all reserved words to upper case;
Lower will change the casing to lower case;
Mixed 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);
Smart_Mixed As above but do not force upper case characters to
lower case.
<=, :=, =>, ...)
Consider the following code:
Variable : constant String :=
"a string";
If this preference is enabled, it will be indented as follows:
Variable : constant String :=
"a string";
record and
is keywords immediately with no extra space.
When enabled, the following code will be indented as:
package P is
-- Comment
[...]
end P;
When disabled, the indentation will be:
package P is
-- Comment
[...]
end P;
if (condition)
{
int x;
}
If disabled, the same code will be indented as:
if (condition)
{
int x;
}
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.
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.
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't have to reopen and reposition them, but takes space on your screen
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.
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.
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).
Note that in this mode under Windows, the Debug->Interrupt menu
will only interrupt the debugged program with recent versions of gdb.
If you are using older versions of gdb, you need to hit
<Ctrl-C> 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.
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.
rsh -l user
rcp -l user
This program is required under Unix systems in order to print, and is set to
a2ps by default.
If a2ps is not installed on your system, you can download it
from ftp://ftp.enst.fr/pub/unix/a2ps/, although other printing programs
such as lp can be specified instead.
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 http://www.lerup.com/printfile/descr.html
-c nor -u switch).
Arguments of interest may include (this will depend on the version of diff
used):
This command should be compatible with the GNU patch utility.
GPS assumes that the following restricitions are true when the preference is activated. If this isn'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).
The restrictions are the following:
gcov or xcov) to use from
the Tools->Coverage menu.