Gramps 5.2 Wiki Manual - Command Line
Previous | Index | Next |
Languages: |
English • Deutsch • español • suomi • français • עברית • македонски • Nederlands • русский • shqip • slovenčina • Türkçe |
This appendix provides the reference to the command line capabilities available when launching Gramps from the terminal.
Contents
- 1 Start Gramps through the Command Line
- 2 Python options
- 3 Available Gramps options
- 4 Operation
- 5 Examples
- 6 Environment variables
Start Gramps through the Command Line
Normally Gramps is started through the graphical user interface (GUI) on your platform.
It is also possible to start Gramps using a command line interface (CLI). CLI use can
- produce reports that are not available via the GUI,
- create reports, do conversions etc. without opening a window and
- can provide extra information in the event of problems.
This section of the user manual describes how to start Gramps through the CLI, and the features that are available.
The way you start Gramps through the CLI depends on the operating system you are using.
For simplicity of description, the examples of use below are written from the point of view of running Gramps on Linux. The examples would need to be changed for other platforms.
Linux
Linux platform is the only officially supported platform. (Other platforms are community supported.) This is because Gramps developers design, code, use and test the source code on that platform. So diagnosing and fixing any problems that arise (whether due to upgrades or other causes) is done using Linux tools.
Assuming you have used the standard Package Manager (either through a CLI or a GUI) for your Linux distribution, you start Gramps through the CLI by typing:
gramps
If you have done a "build from source", navigate to where you installed the the application. (That folder will include the Gramps.py
file.) Type:
python3 Gramps.py
MS Windows
MS Windows is a community supported platform. If you install the Windows AIO bundle, then this will place an icon on the desktop as well as a menu item in the 'Start' menu. However, the Gramps installation directory is not added to the system path and to run gramps via CLI, we need to know the path to that directory. To find the installation folder, refer to AIO bundle's installation folder section.
To find the path using a shortcut icon instead,
- Right-click on the
GrampsAIO64 5.2.3-console
application, or the corresponding item in the Start menu. - Note down the file location (its "Start in' directory).
- Select the full path and copy (Ctrl+c) it.
To run Gramps from the command line, you'll need to start a console window:
- From the Start menu, start cmd.exe.
- Change directory to the installation directory you located.
- Type in or paste the path, surrounding it in quotes if there are spaces.
- Press ↵ Enter.
For example, this might be:
cd "C:\Program Files\GrampsAOI64-5.2.3" gramps
You may use any of the command-line options along with this. For example, to get a detailed listing of all of the Family Tree databases in your default Family Tree folder, you would append -L
cd "C:\Program Files\GrampsAOI64-5.2.3" gramps -L
See example usage https://github.com/gramps-project/addons-source/pull/121
macOS
macOS is a community supported platform. If you download the macOS disk image (.dmg), then you simply drag the application to your application folder (or anywhere else you want to store it) and start Gramps by double clicking on the application in the normal way. The Homebrew package manager also allows for installation of the application in the usual Applications folder.
To run from the command line, you'll need to start Terminal, found in the Utilities folder of the main Applications folder (/Applications/Utilities). Once you have a terminal window open, at the prompt type
/path/to/Gramps.app/Contents/MacOS/Gramps
If you installed Gramps in Applications along with most of your other apps, as suggested above, that would be
/Applications/Gramps.app/Contents/MacOS/Gramps
You may use any of the command-line options along with this. For example, to get a detailed listing of all of the Family Tree databases in your default Family Tree folder, you would use
/Applications/Gramps.app/Contents/MacOS/Gramps -L
There are other ways to install Gramps for macOS, but these are much more complicated and are not covered here.
Python options
In the examples of different platforms above, and also in commands in various files you may see some options after the 'python' command, for example '-EO' in
"python3 -EO ..\share\gramps\gramps.py -L
It is important to distinguish between the python options in this case:
-EO
and the Gramps options, in this case
-L
The python options that you may come across are:
-E
Ignore all PYTHON* environment variables, e.g.PYTHONPATH
andPYTHONHOME
, that might be set.-O
Turn on basic optimizations. This changes the filename extension for compiled (bytecode) files from.pyc
to.pyo
. See also PYTHONOPTIMIZE.
The -O
optimise flag has a number of effects in Gramps:
- If it is not turned on, an additional Debug entry appears in the Tools menu.
- If it is not turned on, info logging messages are output.
- If it is not turned on, debug statements may be activated.
- If it is not turned on, additional features are available in the Plugin Manager.
The Gramps options are described below.
Available Gramps options
This section provides the reference list of all command line options available in Gramps. If you want to know more than just a list of options, see next sections: Operation and Examples. The summary below is printed by
gramps -h
or
gramps --help
Usage: gramps.py [OPTION...] --load-modules=MODULE1,MODULE2,... Dynamic modules to load Help options -?, --help Show this help message --usage Display brief usage message Application options -O, --open=FAMILY_TREE Open Family Tree -U, --username=USERNAME Database username -P, --password=PASSWORD Database password -C, --create=FAMILY_TREE Create on open if new Family Tree -i, --import=FILENAME Import file -e, --export=FILENAME Export file -r, --remove=FAMILY_TREE_PATTERN Remove matching Family Tree(s) (use regular expressions) -f, --format=FORMAT Specify Family Tree format -a, --action=ACTION Specify action -p, --options=OPTIONS_STRING Specify options -d, --debug=LOGGER_NAME Enable debug logs -l [FAMILY_TREE_PATTERN...] List Family Trees -L [FAMILY_TREE_PATTERN...] List Family Trees in Detail -t [FAMILY_TREE_PATTERN...] List Family Trees, tab delimited -u, --force-unlock Force unlock of Family Tree -s, --show Show config settings -c, --config=[config.setting[:value]] Set config setting(s) and start Gramps -y, --yes Don't ask to confirm dangerous actions (non-GUI mode only) -q, --quiet Suppress progress indication output (non-GUI mode only) -v, --version Show versions -S, --safe Start Gramps in 'Safe mode' (temporarily use default settings) -D, --default=[APXFE] Reset settings to default; A - addons are cleared P - Preferences to default X - Books are cleared, reports and tool settings to default F - filters are cleared E - Everything is set to default or cleared
The usage message is as follows:
gramps --usage
Example of usage of Gramps command line interface 1. To import four databases (whose formats can be determined from their names) and then check the resulting database for errors, one may type: gramps -i file1.ged -i file2.gpkg -i ~/db3.gramps -i file4.wft -a tool -p name=check. 2. To explicitly specify the formats in the above example, append filenames with appropriate -f options: gramps -i file1.ged -f gedcom -i file2.gpkg -f gramps-pkg -i ~/db3.gramps -f gramps-xml -i file4.wft -f wft -a tool -p name=check. 3. To record the database resulting from all imports, supply -e flag (use -f if the filename does not allow Gramps to guess the format): gramps -i file1.ged -i file2.gpkg -e ~/new-package -f gramps-pkg 4. To save any error messages of the above example into files outfile and errfile, run: gramps -i file1.ged -i file2.dpkg -e ~/new-package -f gramps-pkg >outfile 2>errfile 5. To import three databases and start interactive Gramps session with the result: gramps -i file1.ged -i file2.gpkg -i ~/db3.gramps 6. To open a database and, based on that data, generate timeline report in PDF format putting the output into the my_timeline.pdf file: gramps -O 'Family Tree 1' -a report -p name=timeline,off=pdf,of=my_timeline.pdf 7. To generate a summary of a database: gramps -O 'Family Tree 1' -a report -p name=summary 8. Listing report options Use the name=timeline,show=all to find out about all available options for the timeline report. To find out details of a particular option, use show=option_name , e.g. name=timeline,show=off string. To learn about available report names, use name=show string. 9. To convert a Family Tree on the fly to a .gramps xml file: gramps -O 'Family Tree 1' -e output.gramps -f gramps-xml 10. To generate a web site into an other locale (in German): LANGUAGE=de_DE; LANG=de_DE.UTF-8 gramps -O 'Family Tree 1' -a report -p name=navwebpage,target=/../de 11. Finally, to start normal interactive session type: gramps Note: These examples are for bash shell. Syntax may be different for other shells and for Windows.
List options
Print a list of known family trees:
- Sparse
-l, List Family Trees
gramps -l
List of known Family Trees in your database path /home/<~username>/.gramps/grampsdb/5a46c1c3 with name "Example Family Tree"
- Detailed
-L, List Family Trees in Detail
gramps -L
Gramps Family Trees: Family Tree "Example Family Tree": Database: SQLite Database module location: /usr/lib/python3.6/sqlite3/__init__.py Database module version: 2.6.0 Database version: 3.21.0 Last accessed: 30/12/17 09:29:37 Locked?: False Number of citations: 2854 Number of events: 3432 Number of families: 762 Number of media: 7 Number of notes: 19 Number of people: 2157 Number of places: 1294 Number of repositories: 3 Number of sources: 4 Number of tags: 2 Path: /home/<~username>/.gramps/grampsdb/5a46c1c3 Schema version: 18.0.0
Note that dates are shown in the default LOCALE format. You change that at the system level. For example, on POSIX-based systems you could use: LC_TIME=en_AU.UTF-8 gramps -L |
Version options
-v or --version prints version of Gramps and dependencies, information about environment settings and python and system paths
gramps -v
Gramps Settings: ---------------- python : 3.7.5 gramps : 5.2.1 gtk++ : 3.24.12 pygobject : 3.34.0 pango : 1.42.3 cairo : 1.16.0 pycairo : 1.16.2 osmgpsmap : 1.0 GExiv2 : 0.10 ICU : 63.1 PyICU : 2.2 o.s. : linux kernel : 5.3.0-24-generic Environment settings: --------------------- LANG : en_GB.UTF-8 LANGUAGE : en_GB:en GRAMPSI18N: not set GRAMPSHOME: not set GRAMPSDIR : not set PYTHONPATH: /usr/lib/python3/dist-packages/gramps /usr/bin /usr/lib/python37.zip /usr/lib/python3.7 /usr/lib/python3.7/lib-dynload /usr/local/lib/python3.7/dist-packages /usr/lib/python3/dist-packages Non-python dependencies: ------------------------ Graphviz : 2.40 Ghostscr. : 9.27 System PATH env variable: ------------------------- /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin /usr/games /usr/local/games /snap/bin Databases: ------------------------- bsddb : version : 6.2.6 db version : 5.3.28 location : /usr/lib/python3/dist-packages/bsddb3/__init__.py sqlite3 : version : 3.29.0 py version : 2.6.0 location : /usr/lib/python3.7/sqlite3/__init__.py
Format options
The format of any file destined for opening, importing, or exporting can be specified with the
-f format
option. The acceptable format values are listed below.
Full family tree support
These formats contain all your data that is present in a family tree.
- gramps - Gramps XML format: This format is available for import, and export. When not specified, it can be guessed if the filename ends with .gramps
- gpkg - Gramps package XML format: This format is available for import and export. When not specified, it can be guessed if the filename ends with .gpkg. This creates a zip package with your data as xml, and all your media files included
- grdb - pre Gramps 3.x database: This format is available for import to support the old file format of Gramps. Everything in the grdb file is imported. When not specified, it can be guessed if the filename ends with .grdb
- burn - GNOME iso burning: export, only available on GNOME where burn protocol exists
Reduced family tree support
These formats contain most, but not all data that can be created in Gramps
- ged - GEDCOM format: This format is available for import, and export. When not specified, it can be guessed if the filename ends with .ged
- gw - GeneWeb file: This format is available for import and export. When not specified, it can be guessed if the filename ends with .gw
Subset of your data
These formats contain a specific subset of your data
- csv - Comma Separated Value: This format is available for import and export. Be careful however, import must be as values created by the export function. Only a part of your data is contained in the output.
- vcf - VCard 3.0 format: import and export
- vcs - VCalendar format: export
- def - old Pro-Gen format: import
- wft - Web Family Tree: This format is available for export only. When not specified, it can be guessed if the filename ends with .wft
Opening options
You can open a family tree, or you can open a file by importing it in an empty family tree.
To let Gramps handle this automatically, just supply the family tree or filename you want to open:
python gramps.py 'My Fam Tree' python gramps.py JohnDoe.ged
The first opens a family tree, the second imports a GEDCOM into an empty family tree.
Additionally, you can pass Gramps the name of the family tree to be opened:
- use this option :
-O famtree
or--open=famtree
-O
, Open of a family tree. This can be done also by just typing the name (name or database dir)
Examples:
python gramps.py 'Family Tree 1' python gramps.py /home/cristina/.gramps/grampsdb/47320f3d python gramps.py -O 'Family Tree 1' python gramps.py -O /home/cristina/.gramps/grampsdb/47320f3d
Tip If no option is given, just a name, Gramps will ignore the rest of the command line arguments. Use the |
Tip Only family trees can be opened directly. For other formats, you will need to use the import option which will set up the empty database and then import data into it. |
Tip Only a single family tree can be opened. If you need to combine data from several sources, you will need to use the import option. |
Import options
The files destined for import can be specified with the -i filename
or --import=filename
option. The format can be specified with the -f format
or --format=format
option, immediately following the filename . If not specified, the guess will be attempted based on the filename.
Example:
python gramps.py -i 'Family Tree 1' -i 'Family Tree 2' python gramps.py -i test.grdb -i data.gramps
Tip More than one file can be imported in one command. If this is the case, Gramps will incorporate the data from the next file into the database available at the moment. |
When more than one input file is given, each has to be preceded by -i
flag. The files are imported in the specified order, i.e. -i file1 -i file2
and -i file2 -i file1
might produce different Gramps IDs in the resulting database.
Export options
The files destined for export can be specified with the -e filename
or --export=filename
option. The format can be specified with the -f
option immediately following the filename . If not specified, the guess will be attempted based on the filename . For iso format, the filename is actually the name of directory the Gramps database will be written into. For gramps-xml, gpkg, gedcom, wft, geneweb, and gramps-pkg, the filename is the name of the resulting file.
-e, export a family tree in required format. It is not possible to export to a family tree.
Example:
python gramps.py -i 'Family Tree 1' -i test.grdb -f grdb -e mergedDB.gramps
Note that above does not change 'Family Tree 1' as everything happens via a temporary database, whereas:
python gramps.py -O 'Family Tree 1' -i test.grdb -f grdb -e mergedDB.gramps
will import test.grdb into Family Tree 1, and then export to a file !
Exporting more files More than one file can be exported in one command. If this is the case, Gramps will attempt to write several files using the data from the database available at the moment. |
When more than one output file is given, each has to be preceded by -e
flag. The files are written one by one, in the specified order.
Action options
The action to perform on the imported data can be specified with the -a action
or --action=action
option. This is done after all imports are successfully completed.
The following actions remain the same:
- report: This action allows producing reports from the command line.
- tool: This action allows to run a tool from the command line.
Reports and tools generally have many options of their own, so these actions should be followed by the report/tool option string. The string is given using the -p option_string
or --options=option_string
option.
The actions available in older versions of Gramps which were relocated in Gramps 3.3 are:
- summary: This action was the same as Reports ->View ->Summary. In Gramps 3.3 it was replaced by (or renamed to) -a report -p name=summary.
- check: This action was the same as Tools ->Database Processing ->Check and Repair. In Gramps 3.3 it was replaced by (or renamed to) -a tool -p name=check.
report action option
You can generate most reports from the command line using the report action.
An example:
gramps -O "Family Tree 1" -a report -p "name=family_group,style=default,off=html,of=test.html"
You can provide the css style to use here with the css option:
gramps -O "Family Tree 1" -a report -p "name=family_group,style=default,off=html,of=test.html,css=Web_Nebraska.css"
or without css in the html output:
gramps -O "Family Tree 1" -a report -p "name=family_group,style=default,off=html,of=test.html,css="
Most of the report options are specific for every report. However, there are some common options.
name=report_name
: This mandatory option determines which report will be generated.
of=
: output filename and optional destination folder/directory eg:of="C:\Users\<username>\Desktop\FamilyTree.odt"
off=
: output format. These are the extension an output format makes available, eg, pdf, html, doc, ...style=
: for text reports, the stylesheet to use. Defaults to 'default'.show=all
: This will produce the list of names for all options available for a given report.show=option_name
: This will print the description of the functionality supplied by the option_name, as well as what are the acceptable types and values for this option.
So, to learn to use a report, do for example:
gramps -O "Family Tree 1" -a report -p "name=family_group,show=all"
When more than one output action is given, each has to be preceded by -a
flag. The actions are performed one by one, in the specified order.
On the command line such lists must always start with a left square bracket [
and must always end with a right square bracket ]
but since such square brackets are usually "special" to the "shell" (they mean something to the command interpreter
you are typing the command to), you must "escape" them so that they are ignored by your shell.
The details vary with each shell but (in linux/UNIX) usually you can precede such a square bracket with a backslash \
or put quotation marks around the square bracket, usually either "single" or "double" ones.
The Hourglass Graph report allows you to put a "note" at the top of the report and such a "note" is an example of a "list" option. Here is an example:
gramps -O "Family Tree 1" -a report -p name=hourglass_graph,note='[line one,line two]'
which shows that inside such a list different lines are separated by commas, and that spaces are acceptable since the quotation marks are already there for the square brackets.
But if you want to have a comma inside your report you have to somehow tell Gramps that comma is not one which separates lines. You do that by enclosing the line with the comma in quotation marks (either single or double).
But if you are already using a set of quotation marks (to enclose your square brackets) you have to use the other type to enclose the line with your comma. Here is an example:
gramps -O "Family Tree 1" -a report -p name=hourglass_graph,note="['line one, also line one','line two, also line two']"
It is possible to include any character in a list but the details are beyond the scope of this command-line introduction to Gramps.
You will need to know the precise methods available in your particular command shell interpreter to include a character which is "special" to your shell or "special" to Gramps (like the comma in the example above) but in general you will have to "escape" it twice, once to your shell and once again to Gramps, since you don't want your shell to think it is some instruction it should pay attention to and you don't want Gramps to think that either.
tool action option
You can run most tools from the command line using the 'tool' action. To see which ones, say:
gramps -O "Family Tree 1" -a tool -p show=all
To see a tool's available options, for instance the "verify" tool:
gramps -O "Family Tree 1" -a tool -p name=verify,show=all
To run a tool, for instance the "verify" tool:
gramps -O "Family Tree 1" -a tool -p name=verify
book action option
New feature Added in Gramps 5.0 |
You can run books from the command line using the 'book' action. To see which ones, say:
gramps -O "Family Tree 1" -a book
To see a book's available options, for instance a book called "mybook":
gramps -O "Family Tree 1" -a book -p name=mybook,show=all
To run a book, for instance a book called "mybook":
gramps -O "Family Tree 1" -a book -p name=mybook
Force unlock option
-u
: you can extend the-O
flag with-u
to force a locked family to be unlocked. This allows you to recover from a crash that leaves the family tree (database) locked, from the command line.
An example (to unlock the "Family Tree 1" database):
gramps -O "Family Tree 1" -a report -u > /dev/null
Note It is not possible to open family trees that need repair from the command line. |
See also:
Configuration (config) option
When all configuration variable(s) are set Gramps will start with these new values.
These options can takes three forms:
Note Except for examples 1 and 3.2, All the following examples, use |
- 1) See all config values
-s
or--show
For example:
gramps --show
Gramps config settings from /home/<~username>/.gramps/gramps50/gramps.ini: export.proxy-order=[['privacy', 0], ['living', 0], ['person', 0], ['note', 0], ['reference', 0]] database.compress-backup=True database.backend='bsddb' database.backup-path='/home/<~username>' database.port='' database.autobackup=0 database.path='/home/<~username>/.gramps/grampsdb' database.host='' database.backup-on-exit=True geography.lock=False ....
- 2) See a single config value
--config=database.path
or-c database.path
For example:
gramps --config=database.path
Current Gramps config setting: database.path:'/home/<~username>/.gramps/grampsdb'
3) Set a value: --config=behavior.database-path:'/media/mydb'
or -c behavior.database-path:'/media/mydb'
For example:
3.1) Set a value to its default: --config=behavior.database-path:DEFAULT
or -c behavior.database-path:DEFAULT
For example:
3.2) Set more than one value: --config=behavior.use-tips:False --config=behavior.autoload:True
or -c behavior.use-tips:False -c behavior.autoload:True
For example:
Safe mode
gramps -S
or gramps --safe
This CLI command starts Gramps as if it had never been installed before. In this mode, any previous family trees can still be loaded, as long as they were stored in the default folder. All other settings, filters, books, addons etc. are either cleared or returned to their default values. Other CLI commands can be used, or, if none, Gramps will start the GUI. Nothing except the actual family tree data is saved.
Note that this is typically used to see if Gramps behaves better when it is running as if with a totally 'clean' install. It is NOT permanent (if you want that see Defaults below), if you start Gramps normally after using this command all of your previous settings etc. are still there.
This actually works by setting the folder that Gramps uses to store its user data (except for family trees) to a temporary directory, which is deleted when Gramps closes.
Defaults
gramps -D E
or gramps --default=E
This CLI command causes Gramps to clear out or return to defaults the desired settings. The family tree databases are NOT cleared out or removed. The sub-commands (replace the 'E' from the example command line above with one or more of the subcommand characters) are:
A
Addons are cleared. Any installed addons are removed, along with their settings.F
Filters are cleared. Any custom filters are removed.P
Preferences are returned to their default values.X
Books are cleared, Reports and Tools settings are returned to their default values.Z
Old '.zip' files from family tree version upgrades are deleted.E
Everything except the actual family tree data is returned to default settings. This does all of the above as well as a few more items; deletes thumbnails, maps, and the user CSS (used in web reports).
For example:
gramps -D AP
will cause Gramps to remove all the Addons and to reset Preferences to their default values.
Operation
If the first argument on the command line does not start with a dash (i.e. no flag), Gramps will attempt to open the file with the name given by the first argument and start an interactive session, ignoring the rest of the command line arguments.
If the -O
flag is given, then Gramps will try opening the supplied file name and then work with that data, as instructed by the further command line parameters.
Note Only one file can be opened in a single invocation of Gramps. If you need to get data from multiple sources, use the importing options by using |
With or without the -O
flag, there could be multiple imports, exports, and actions specified further on the command line by using -i
, -e
, and -a
flags.
The order of -i
, -e
, or -a
options with respect to each does not matter. The actual execution order always is: all imports (if any) -> all exports (if any) -> all actions (if any).
Note But opening must always be first! |
If no -O
or -i
option is given, Gramps will launch its main window and start the usual interactive session with the empty database, since there is no data to process, anyway. (Unless you have already expressed a "preference" that it start with the last database it used.)
If no -e
or -a
options are given, Gramps will launch its main window and start the usual interactive session with the database resulted from opening and all imports (if any). This database resides in a directory under the ~/.gramps/grampsdb/
directory.
Any errors encountered during import, export, or action, will be either dumped to stdout (if these are exceptions handled by Gramps) or to stderr (if these are not handled). Use usual shell redirections of stdout and stderr to save messages and errors in files.
Examples
- To import four databases (whose formats can be determined from their names) and then check the resulting database for errors, one may type:
gramps -i file1.ged -i file2.gpkg -i ~/db3.gramps -i file4.wft -a check
- To explicitly specify the formats in the above example, append filenames with appropriate -f options:
gramps -i file1.ged -f gedcom -i file2.gpkg -f gramps-pkg -i ~/db3.gramps -f gramps-xml -i file4.wft -f wft -a check
- To record the database resulting from all imports, supply -e flag (use -f if the filename does not allow Gramps to guess the format):
gramps -i file1.ged -i file2.gpkg -e ~/new-package -f gramps-pkg
- To save any error messages of the above example into files outfile and errfile, run:
gramps -i file1.ged -i file2.dpkg -e ~/new-package -f gramps-pkg >outfile 2>errfile
- To import three databases and start interactive Gramps session with the result:
gramps -i file1.ged -i file2.gpkg -i ~/db3.gramps
- To open a database and, based on that data, generate timeline report in PDF format putting the output into the my_timeline.pdf file:
gramps -O 'Family Tree 1' -a report -p name=timeline,off=pdf,of=my_timeline.pdf
- To convert the bsddb database on the fly to a .gramps xml file:
gramps -O 'Family Tree 1' -e output.gramps -f gramps-xml
- To generate a web site into an other locale (in German):
LANGUAGE=de_DE; LANG=de_DE.UTF-8 gramps -O 'Family Tree 1' -a report -p name=navwebpage,target=/../de
- Finally, to start normal interactive session type:
gramps
Environment variables
Warning Gramps can take advantage of the following environment variables |
GRAMPSHOME
- GRAMPSHOME - if set, override default path to profile allowing user to use an external network drive to store data and all settings. For technically advanced users who run multiple versions of Gramps, setting a different $GRAMPSHOME is a way to avoid interference between the different versions in the Gramps User Directory. It can also be used to configure Gramps to run from a portable drive or to prepare for a manual installation. The path can also be used to configure the path to a separate test Tree or development Tree.
For example
GRAMPSHOME=$HOME/familytrees/paternal
LANG, LANGUAGE, LC_MESSAGE, LC_TIME
- LANG, LANGUAGE, LC_MESSAGES, and LC_TIME - are used by Gramps to determine which language file(s) should be loaded. See locale(1) for a general discussion of LANG, LC_MESSAGES, and LC_TIME. Note that in addition to setting date formats (which are overridden in Gramps with Preferences settings) LC_TIME also sets the language used for words in dates like month and day names and in the context of dates words like about, between, and before. LANGUAGE is a comma-separated list of language codes (not locales, though certain languages like pt_BR or cn_TW are regional variants) that sets a preference-ordered list of desired translations. It will override LANG but not LC_MESSAGES or LC_TIME.
macOS Because of the way launching with Finder works, the environment variables for the Gramps.app bundle are hard-coded in |
GRAMPSI18N
- $GRAMPSI18N (for your locale) - The LANG assumes the Gramps translations are installed globally. If this is not the case, you need to give Gramps the directory where the translations will be found. This can be used to temporarily change the language for Reports being generated.
A translation is called gramps.mo
, you can find it in Linux with the locate command. For example, if you have Swedish in directory /home/me/gramps/mo/sv/gramps.mo
, you can direct Gramps there using:
GRAMPSI18N=/home/me/gramps/mo LC_ALL=C.UTF-8 LANG="sv" python3 gramps
GRAMPSDIR
- The environment variable GRAMPSDIR is the path to your Gramps directory.
GRAMPS_RESOURCES
- The environment variable GRAMPS_RESOURCES is the path to Gramps built-in resources files. You should only change this if you are using Gramps from source code or a custom environment. An indicator that you need to set this variable is if you receive one of the following errors:
- Encoding error while parsing resource path
- Failed to open resource file
- Resource Path {invalid/path/to/resources} is invalid
- Unable to determine resource path
Example usage:
GRAMPS_RESOURCES=/home/username/gramps/branches/maintenance/gramps52/build/t PYTHONPATH=$GRAMPS_RESOURCES:$PYTHONPATH ./gramps
Previous | Index | Next |
Languages: |
English • Deutsch • español • suomi • français • עברית • македонски • Nederlands • русский • shqip • slovenčina • Türkçe |
Special copyright notice: All edits to this page need to be under two different copyright licenses:
These licenses allow the Gramps project to maximally use this wiki manual as free content in future Gramps versions. If you do not agree with this dual license, then do not edit this page. You may only link to other pages within the wiki which fall only under the GFDL license via external links (using the syntax: [https://www.gramps-project.org/...]), not via internal links. |