Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gpbs(1) [debian man page]

GPBS(1) 						       GNUstep System Manual							   GPBS(1)

NAME
gpbs - GNUstep PasteBoard Server SYNOPSIS
gpbs DESCRIPTION
The gpbs daemon serves as a clipboard/pasteboard for GNUstep programs, handling the copying, cutting and pasting of objects as well as drag and drop operations between applications. Every user needs to have his own instance of gpbs running. While gpbs will be started automatically as soon as it is needed, it is recommend to start gpbs in a personal login script like ~/.bashrc or ~/.cshrc. Alternatively you can launch gpbs when your windowing system or the window manager is started. For example, on sys- tems with X11 you can launch gpbs from your .xinitrc script or alternatively - if you are running Window Maker - put it in Window Maker's autostart script. See the GNUstep Build Guide for a sample startup script. OPTIONS
-NSHost <hostname> attaches gpbs to a remote session. --GSStartupNotification sends a notification through the NSDistributedNotificationCenter (i.e. gdnc) so that apps know that it has started up. This is only relevant if the application itself tries to startup gpbs (which means gpbs was not started at session login). --daemon starts gpbs as a daemon - mostly this means that all output gets sent to syslog rather than the terminal. --no-fork does not fork a separate process --verbose makes bs his logging more verbose DIAGNOSTICS
gdomap -L GNUstepGSPasteboardServer will lookup instances of gpbs. Alternatively, gdomap -N will list all registered names on the local host. BUGS
Versions of gpbs up to (including) 1.7.2 have problems with copy and paste of mulit-lingual text, as it used the atom XA_STRING alone to exchange string data between X clients (and thus GNUstep clients). This means gpbs is inherently unable to do cut-and-paste with charac- ters other than ISO Latin1 ones, TAB, and NEWLINE. SEE ALSO
gdnc(1), gdomap(8), GNUstep(7) xinit(1) wmaker(1) The GNUstep Build Guide example startup script: <http://gnustep.made-it.com/BuildGuide/index.html#GNUSTEP.SERVICES> HISTORY
Work on gdnc started August 1997. This manual page first appeared in gnustep-back 0.8.8 (July 2003). AUTHORS
gpbs was written by Richard Frith-McDonald <rfm@gnu.org> This man page was written by Martin Brecher <martin@mb-itconsulting.com> with contributions from Kazunobu Kuriyama <kazunobu.kuriyama@nifty.com>. This man page was updated September 2006 by Dennis Leeuw (dleeuw@made-it.com) with notes by Adam Fedor (fedor@doc.com). GNUstep September 2006 GPBS(1)

Check Out this Related Man Page

openapp(1)						       GNUstep System Manual							openapp(1)

NAME
openapp - launch applications from the command line SYNOPSIS
openapp [--find] [--debug [--gdb= debuger]] [ --library-combo=library-combo ] application [arguments...] DESCRIPTION
The openapp command allows you to launch graphical GNUstep applications from the command line. application is the complete or relative name of the application program with or without the .app extension, like Ink.app. arguments are the arguments passed to the application. openapp first checks whether the application is in the current working directory. If not then searches the GNUstep domains' Applications folders in the following order: User (i.e. ~/GNUstep/Applications), Local, Network, System. First match wins. OPTIONS
--find application will print out the full path of the application executable which would be executed, without actually executing it. It will also list all paths that are attempted. --debug application starts the application in the debugger. By default gdb, but this can be changed with the --gdb= argument or through the GDB shell variable. --library-combo=library-combo Starts the application with the specified library combo. This is a rarely used option in a non-flattened setup. See the library- combo(7) man-page for more information about the different library combinations. --help print above usage description. EXAMPLES
Start Ink.app without additional parameters: openapp Ink.app Launch Ink.app and pass it the --debug argument: openapp --debug Ink.app To determine which executable is launched by openapp, type: openapp --find Ink.app The output of the above command might be something like: /usr/GNUstep/Local/Applications/Ink.app/Ink ENVIRONMENT
GNUSTEP_CONFIG_FILE is used to determine where the GNUstep.sh configuration file is located. If the variable is not set openapp tries to locate it in the folder where openapp was started, then in the user domain, and as a last resort in the system domain (or actually the place you configured (--with-config-file=) during building). GDB Sets the debugger to use when --debug is used. SEE ALSO
debugapp(1), GNUstep(7), gopen(1), library-combo(7), opentool(1) HISTORY
Work on openapp started October 1997. openapp was originally written by Ovidiu Predescu <ovidiu@net-community.com> and is now maintained by Nicola Pero <nicola.pero@meta-innova- tion.com> AUTHORS
This manual page was first written July 2003 by Martin Brecher <martin@mb-itconsulting.com>. Updated with notes from Hubert Chathi <uhoreg@debian.org> and Dennis Leeuw <dleeuw@made-it.com>, December 2007 by Dennis Leeuw. gnustep-make 12/12/2007 openapp(1)
Man Page