pilot-read-veo - Man Page

Synchronize your Veo Traveler databases

Section

pilot-link: Userland conduits

Synopsis

pilot-read-veo [-p|--port <port>] [--version] [-?|--help] [--usage] [-q|--quiet] [-n|--name  filename] [-l|--list] [-b|--bias  bias] [-c|--colour] [-t|--type [ppm|png]]

Description

Synchronize your Veo Traveler databases with your desktop machine. Output defaults to ppm.

Options

pilot-read-veo options

                       -n, --name name
                   

Specify output picture by name

                       -l, --list
                   

List Photos on device

                       -b, --bias bias
                   

lighten or darken the image (0..50 darken, 50..100 lighten)

                       -c, --colour
                   

colour correct the output colours

                       -t,
                       --type [ppm|png]
                   

Specify picture output type (ppm or png)

Conduit Options

                       -p, --port port
                   

Use device file port to communicate with the Palm handheld. If this is not specified, pilot-read-veo will look for the $PILOTPORT environment variable. If neither are found or supplied, pilot-read-veo will print the usage information.

                       -q,
                       --quiet
                   

Suppress 'Hit HotSync button' message

                       -v, --version
                   

Display version of pilot-read-veo and exit without connecting.

Help Options

                       -h, --help
                   

Display the help synopsis for pilot-read-veo and exit without connecting.

                       --usage
                   

Display a brief usage message and exit without connecting.

Author

pilot-read-veo was originally written by Angus Ainslie <angusa at deltatee.com>

This manual page was written by Neil Williams <linux@codehelp.co.uk>

Reporting Bugs

We have an online bug tracker. Using this is the only way to ensure that your bugs are recorded and that we can track them until they are resolved or closed. Reporting bugs via email, while easy, is not very useful in terms of accountability. Please point your browser to http://bugs.pilot-link.org: http://bugs.pilot-link.org and report your bugs and issues there.

See Also

pilot-link(7)

Info

Copyright 1996-2007 FSF 0.12.5 PILOT-LINK