Last updated: 31 August 1998
To date, the GIMP runs only on a variety of UNIX and UNIX-like systems. So the GIMP is always started via a command line (although this can be hidden by a window manager or desktop).
gimpshould start the GIMP. However, several options are available.
|-h or --help||Output help.|
|-v or --version||Output version info.|
|-b or --batch <commands>||Run in batch mode.|
|-n or --no-interface||Run without a user interface.|
|--no-data||Do not load patterns, gradients, palettes, brushes.|
|--verbose||Show the startup messages.|
|--no-splash||Do not show the startup window.|
|--no-splash-image||Do not add an image to the startup window.|
|--no-shm||Do not use shared memory between GIMP and its plugins.|
|--no-xshm||Do not use the X Shared Memory extension.|
|--console-messages||Display warnings to console instead of a dialog box.|
|--display <display>||Use the designated X display.|
|--sync||Send X commands synchronously.|
|--show-events||Show GDK events.|
|--no-show-events||Don't show GDK events.|
|--debug-level <level>||Provide debug output at designated level.|
|--debug-handlers||Enable debugging signal handlers.|
Usage: gimp [option ...] [files ...] Valid options are: -h --help Output this help. -v --version Output version info. -b --batch <commands> Run in batch mode. -n --no-interface Run without a user interface. --no-data Do not load patterns, gradients, palettes, brushes --no-shm Do not use shared memory between GIMP and its plugins. --no-xshm Do not use the X Shared Memory extension --display <display> Use the designated X display. Valid debugging options are: --sync Send X commands synchronously. --show-events Show GDK events. --no-show-events Don't show GDK events. --debug-level <level> Provide debug output at designated level.
GIMP version 0.99.10To get the latest version of the GIMP, check http://www.gimp.org/ .
If this parameter is '-' (a minus sign), the commands will be taken from the standard input stream (stdin). If the parameter starts with a parenthesis, it is assumed to be the actual commands. Otherwise, the GIMP tries to open a file using the parameter as a filename. If this fails, the GIMP will complain:
unable to open batch file: <commands>When the parameter is the actual command[s] to run, you may need to enclose the command[s] in quotes (single or double) to pass escape various characters that would otherwise be interpreted by your shell (such as quotes and parentheses). You will need to escape any quotes that appear within the command by prepending them with a backslash (\), as in the example below.
gimp -b '((gimp-palette-set-background \'(255 0 0)) ... (gimp-displays-flush))'
With the C shell and its variants (csh, tcsh, etc.) you cannot use a single quote inside single quotes. In this case, you need to end the quote, add an escaped quote, and resume the quoted string, as shown below.
gimp -b '((gimp-...ound '\''(255 0 0)) ... ))'
This must be the last option on the command line, because everything after it is interpreted as a batch command.
Unless you have something generating commands on the fly, or are testing something simple, you probably don't want to use this option.
File -> Dialogs -> Brushes... (or Patterns...)and clicking on the [Refresh] button. There is currently no equivalent method to load palettes and gradients after starting. Presumably this will change.
There may still be a couple of UNIX vendors whose X servers do not support this extension. In some cases, you have to explicitly tell your X server to use the extension. Check the X(1) and Xserver(1) man pages for more information if you suspect this is the case.
gimp -display volcano.tb.org:0If you need further information, check the X(1) man pages.
How you do this depends on the shell you are using. In any of the Bourne-derived shells (sh, bsh, rsh, ksh, or bash):
gimp > error_file 2>&1In any of the csh-derived shells (csh, tcsh):
gimp >& error_file
This option indicates that requests to the X server should be sent synchronously, instead of asynchronously. Since Xlib normally buffers requests to the server, errors do not necessarily get reported immediately after they occur. This option turns off the buffering so that the appli- cation can be debugged. It should never be used with a working program.
parsing "/home/meo/.gimp/gtkrc" parsing "/usr/local/share/gimp/0.99.10/gimprc" parsing "/home/meo/.gimp/pluginrc" Starting extensions: extension_script_fuI'm not sure whether these will still occur in 1.0 . If the GIMP is started from a window manager or desktop manager menu, you will probably never see these.
The only other messages at this time are debugging messages. The most common have to do with tile reference counts, which you may safely ignore (unless you are debugging, of course!) and complaints from scheme when a Script-Fu script fails. See the FAQs for the most common of these.
Now you should learn the basics of using the GIMP.
Copyright 1997, 1998 Miles O'Neal, Austin, TX. All rights reserved.