Gimp man pages
There are two Gimp man pages: one for Gimp, and one for a util called gimptool.
Gimp - an image manipulation and paint program.
gimp [-h] [--help] [-v] [--version] [-b] [--batch <commands>] [-n] [--no-interface] [--no-data] [--verbose] [--no-shm] [--no-xshm] [--display display] [--no-splash] [--no-splash-image] [--debug-handlers] [--console-messages]
The gimp is the GNU Image Manipulation Program. It is used to edit and manipulate images. It can load and save a variety of image formats and can be used to convert between formats.
Gimp can also be used as a paint program. It features a set of drawing and painting tools such as airbrush, clone, pencil, and paint brush. Painting and drawing tools can be applied to an image with a variety of paint modes. It also offers an extensive array of selection tools like rectangle, ellipse, fuzzy select, bezier select, intelli- gent scissors, and select by color.
Gimp offers a variety of plugins that perform a variety of image manipulations. Examples include bumpmap, edge detect, gaussian blur, and many others.
In addition, Gimp has several scripting extension which allow for advanced non-interactive processing and creation of images.
The gimp accepts the following options:
-h, --help
Display a list of all commandline options.
-v, --version
Output the version info.
-b, --batch<commands>
Execute the set of <commands> non-interactively. The set of <commands> is typically in the form of a script that can be executed by one of the Gimp scripting extensions.
-n, --no-interfacem
Run without a user interface.
--no-data
Do not load patterns, gradients, palettes, or brushes. Often useful in non-interactive situations where startup time is to be minimized.
--verbose
Show startup messages.
--no-shm
Do not use shared memory between GIMP and its plug-ins. Instead of using shared memory, GIMP will send the data via pipe. This will result in slower performance than using shared memory.
--no-xshm
Do not use the X Shared Memory extension. If GIMP is being displayed on a remote X server, this probably needs to be enabled. Also useful for any X server that doesn't properly support the X shared memory extension. This will result in slower performance than with X shared memory enabled.
--display display
Use the designated X display.
--no-splash
Do not show the splash screen.
--no-splash-image
Do not show the splash screen image as part of the splash screen.
--debug-handlers
Enable debugging signal handlers.
--console-messages
Do not popup dialog boxes on errors or warnings. Print the messages on the console instead.
DISPLAY
to get the default host and display number.
XENVIRONMENT
to get the name of a resource file that overrides the global resources stored in the RESOURCE_MANAGER property.
Most gimp configuration is read in from the users init file, $HOME/.gimp/gimprc. The system wide equivalent is in $PREFIX/share/gimp/gimprc. The system wide file is parsed first and the user gimprc can override the sytem settings. $PREFIX/share/gimp/gimprc_user is the default gimprc placed in users home directories the first time gimp is ran.
$HOME/.gimp/gtkrc - users set of GTK config settings. Options such as widget color and fonts sizes can be set here.
$PREFIX/share/gtkrc - sytem wide default set of GTK config settings.
$HOME/.gimp/menurc - user's set of keybindings.
$PREFIX/share/menurc - system wide set of keybindings.
$HOME/.gimp/plug-ins - location of user installed plugins.
$HOME/.gimp/pluginrc - plugin initialization values are stored here. This file is parsed on startup and regener- ated if need be.
$HOME/.gimp/tmp - default location that gimp uses as tem- porary space.
Gimp's data files are stored in $PREFIX/share/gimp where $PREFIX is set on install, but is typically /usr/local.
$PREFIX/share/gimp/brushes - system wide brush files.
$HOME/.gimp/brushes - user created and installed brush files. This files are in the .gbr (gimp brush) format.
$PREFIX/share/gimp/palettes - the system wide palette files. The files are copied to the user palettes directory when gimp is first ran to allow the user to modify the palettes. This directory is not searched for palettes by default.
$HOME/.gimp/palettes - copies of the system palette files as well as user created and modified palette files.
$PREFIX/share/gimp/patterns - basic set of patterns for use in gimp.
$HOME/.gimp/patterns - user created and installed gimp pattern files. This files are in the .pat format.
$PREFIX/share/gimp/gradients - standard system wide set of gradient files.
$HOME/.gimp/gradients - user created and installed gradi- ent files.
$PREFIX/share/gimp/palettes - system wide palette files.
$HOME/.gimp/palettes - user created and installed palettefiles.
$PREFIX/share/gimp/scripts - system wide directory of scripts used in Script-Fu and other scripting extensions.
$HOME/.gimp/scripts - user created and installed scripts.
$PREFIX/share/gimp/gflares - system wide directory used by the gflare plug-in.
$HOME/.gimp/gflares - user created and installed gflare files.
$PREFIX/share/gimp/gfig - system wide directory used by the gfig plug-in.
$HOME/.gimp/gfig - user created and installed gfig files.
$PREFIX/share/gimp/gimp_splash.ppm - graphic file used for the gimp splash screen.
$PREFIX/share/gimp/gimp_logo.ppm - graphic file used in the gimp about dialog.
$PREFIX/share/gimp/gimp_tips.txt - list of tips displayed in the "Tip of the Day" dialog box.
X(1)
Copyright © 1995 Spencer Kimball and Peter Mattis
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
Any bugs found should be reported to the Gimp Developer mailing list at gimp-developer@scam.dcf.berkeley.edu or you may want to make use of the online bug-tracking system available on the web at http://www.wilberworks.com/bugs.html.
Before reporting bugs, please check to see if the bug is mentioned in the FAQ's or the mailing list archive. See the section on Other Info for locations of these.
When reporting Gimp bugs, it is important to include a reliable way to reproduce the bug, version number of Gimp (and probably GTK), OS name and version, and any relevant hardware specs. It is also very important to include as much info as possible about the Xserver the problem was found on including at least server name, the visual, and the bit depth.
If a bug is causing a crash, it is very useful if a stack trace can be provided. And of course, patches to rectify the bug are even better.
The canonical place to find GIMP info is at http://www.gimp.org. Here you can find links to just about every other gimp site, tutorials, data sets, mailing list archives, and more.
There is also a Gimp User Manual available at http://www.dtek.chalmers.se/~d95olofs/manual/ that goes into much more detail about the interactive use of Gimp.
The latest version of Gimp and the gtk libs is always available at ftp://ftp.gimp.org.
Spencer Kimball and Peter Mattis.
With patches, fixes, plugins, extensions, scripts and more from lots and lots of people including but not limited to Lauri Alanko, Shawn Amundson, John Beale, Zach Beane, Tom Bech, Marc Bless, Edward Blevins, Roberto Boyd, Seth Burgess, Brent Burton, Ed Connel, Andreas Dilger, Larry Ewing, David Forsyth, Jim Geuther, Scott Goehring, Heiko Goller, Michael Hammel, Christoph Hoegl, Jan Hubicka, Simon Janes, Ben Jackson, Tim Janik, Tuomas Kuosmanen, Peter Kirchgessner, Karl LaRocca, Jens Lautenbacher, Laramie Leavitt, Raph Levien, Adrian Likins, Ingo Luetke- bohle, Josh MacDonald, Ed Mackey, Marcelo Malheiros, Ian Main, Torsten Martinsen, Federico Mena, Adam D. Moss, Shuji Narazaki, Sven Neumann, Stephen Robert Norris, Erik Nygren, Miles O'Neal, Jay Painter, Mike Phillips, Raphael Quinet, James Robinson, Mike Schaeffer, Tracy Scott, Man- ish Singh, Nathan Summers, Mike Sweet, Eiichi Takamori, Tristan Tarrant, Owen Taylor, Ian Tester, James Wang, Kris Wehner.
gimptool - script to perform various Gimpy functions
gimptool [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--libs] [--cflags] [--build plug-in.c] [--install plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm]
gimptool is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file.
gimptool can also be used by programs that need to know what libraries and include-paths Gimp was compiled with. This is especially useful in Makefiles.
gimptool accepts the following options:
--version
Print the currently installed version of Gimp on the standard output.
--build plug-in.c
Compile and link plug-in.c into a Gimp plug-in.
--install plug-in.c
Compile, link, and install plug-in.c into the user's personal Gimp plug-in directory ($HOME/.gimp/plug-ins)
--install-admin plug-in.c
Compile, link, and install plug-in.c into the system-wide Gimp plug-in directory ($PREFIX/lib/gimp/1.0/plug-ins)
--install-bin plug-in
Install plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp/plug-ins)
--install-admin-bin plug-in
Install plug-in into the system-wide Gimp plug-in directory ($PREFIX/lib/gimp/1.0/plug-ins)
--install-script script.scm
Install script.scm into the user's personal Gimp script directory ($HOME/.gimp/scripts)
--install-admin-script script.scm
Install script.scm into the system-wide Gimp script directory ($PREFIX/share/gimp/scripts)
--libs
Print the linker flags that are necessary to link a Gimp plug-in.
--cflags
Print the compiler flags that are necessary to compile a Gimp plug-in.
--prefix=PREFIX
If specified, use PREFIX instead of the installation prefix that Gimp was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options.
--exec-prefix=PREFIX
If specified, use PREFIX instead of the installation exec prefix that Gimp was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options.
GTK_CONFIG
to get the location of the gtk-config program.
CC
to get the name of the desired C compiler.
CFLAGS
to get the preferred flags to pass to the C compiler for plug-in building.
gimp(1), gtk-config(1)
Copyright © 1995 Spencer Kimball and Peter Mattis
Permission to use, copy, modify, and distribute this soft- ware and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
The Gimp User Manual
Last modified: 20 May 1998
