Reference

guimb(1)

apply a scheme function to each message in mailboxes

NAME

guimb - apply a scheme function to each message in mailboxes

SYNOPSIS

guimb [OPTIONS] [MAILBOX [MAILBOX...]]

DESCRIPTION

guimb -- apply a scheme function to each message in mailboxes

The following options stop argument processing, and pass the remaining arguments to the guimb-getopt function, if it is defined in the module:

-c, --code=EXPR

execute given Scheme expression

-s, --source=MODNAME

load Scheme module MODNAME

The following options have the same effect, but do not affect further options parsing:

-e, --expression=EXPR

execute given Scheme expression

-f, --file=MODNAME

load Scheme module MODNAME

The module to be loaded is normally defined in a file named MODNAME.scm somewhere in your %load-path.

Other options:

-M, --mailbox=NAME

set output mailbox name

-u, --user[=NAME]

direct output to the system mailbox of the user NAME (default - current user)

-r, --read-only

open mailbox in read-only mode

Script arguments:

-g, --guile-arg=ARG

append ARG to the command line passed to script

-{ args... -}

append args to the command line passed to script

--lparen args... --rparen

likewise

-L, --load-path=PATH

append PATH to the beginning of the %load-path

-?, --help

give this help list

--usage

give a short usage message

-V, --version

print program version

Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options.

REPORTING BUGS

Report bugs to <[email protected]>.

SEE ALSO

The complete GNU mailutils documentation is maintained as a Texinfo manual. If the mailutils-doc package is installed, the command

info mailutils

should give you access to the complete manual.
You can also find this manual online in the GNU mailutils webpage:
https://www.gnu.org/software/mailutils/manual/index.html.
Please note this manpage was automatically generated by the Debian mailutils packagers. Do not file bugs for its content to the GNU Mailutils upstream authors.

History

--code since Debian 3.1 (Sarge); --expression since Debian 3.1 (Sarge); --file since Debian 3.1 (Sarge); --guile-arg since Debian 3.1 (Sarge); --help since Debian 3.1 (Sarge); --load-path since Debian 13 (Trixie); --lparen since Debian 13 (Trixie); --mailbox since Debian 3.1 (Sarge); --read-only since Debian 13 (Trixie); --rparen since Debian 13 (Trixie); --source since Debian 3.1 (Sarge); --usage since Debian 3.1 (Sarge); --user since Debian 3.1 (Sarge); --version since Debian 3.1 (Sarge); -? since Debian 3.1 (Sarge); -L since Debian 13 (Trixie); -M since Debian 3.1 (Sarge); -V since Debian 3.1 (Sarge); -c since Debian 3.1 (Sarge); -e since Debian 3.1 (Sarge); -f since Debian 3.1 (Sarge); -g since Debian 3.1 (Sarge); -r since Debian 13 (Trixie); -s since Debian 3.1 (Sarge); -u since Debian 3.1 (Sarge); -{ since Debian 13 (Trixie); -} since Debian 13 (Trixie).

--config-file until Debian 6.0 (Squeeze); --config-help until Debian 6.0 (Squeeze); --config-lint until Debian 6.0 (Squeeze); --config-verbose until Debian 6.0 (Squeeze); --debug until Debian 6.0 (Squeeze); --debug-level until Debian 6.0 (Squeeze); --debug-line-info until Debian 6.0 (Squeeze); --license until Debian 6.0 (Squeeze); --lock-expire-timeout until Debian 5.0 (Lenny); --lock-flags until Debian 5.0 (Lenny); --lock-retry-count until Debian 5.0 (Lenny); --lock-retry-timeout until Debian 5.0 (Lenny); --mail-spool until Debian 5.0 (Lenny); --mailbox-type until Debian 5.0 (Lenny); --no-site-config until Debian 6.0 (Squeeze); --no-site-rcfile until Debian 6.0 (Squeeze); --no-user-config until Debian 6.0 (Squeeze); --no-user-rcfile until Debian 6.0 (Squeeze); --rcfile until Debian 6.0 (Squeeze); --rcfile-lint until Debian 6.0 (Squeeze); --rcfile-verbose until Debian 6.0 (Squeeze); --show-config-options until Debian 6.0 (Squeeze); -d until Debian 6.0 (Squeeze); -m until Debian 5.0 (Lenny).