|-0||If -n is also specified, separate arguments in the output with ASCII NUL characters (character code 0). This option cannot be used at the same time as -N .|
|Specify a list of args to unquote before executing command.|
|-h||Display a short help message and exit.|
|-N||If -n is also specified, separate arguments in the output with a newline. This option cannot be used at the same time as -0 .|
|-n||Do not actually execute command, just print out its expanded form.|
|-p||Do not search the environment variable PATH for the specified command. If this flag is specified, unquote uses execv(3) instead of execvp(3) to execute the command. In other words, command should be a full path to an executable program; PATH is not searched.|
|-q||Quiet operation; even more quiet when more than one -q flag is specified.|
|-R||Do the exact opposite of normal operation: quote the arguments instead of unquoting them. Useful when one needs to test a program with a long quoted argument.|
|-V||Display version information and exit. When combined with one or more -v switches, unquote also attempts to display information about its build environment.|
|-v||Verbose operation; even more verbose when more than one -v flag is specified.|
The following environment variables affect the execution of unquote:
UNQUOTE_ARGS Specify a list of args to unquote before executing command.
None relevant in the present version.
unquote 1 /bin/echo 54657374
unquote 2 /usr/local/vpopmail/bin/vadduser testuser 255465737424
Add a vpopmail user 'testuser' with a password '%Test$'.
Should command-line fields and -f arguments override UNQUOTE_ARGS ?
.An Peter Pentchev in 2001.
.An Peter Pentchev Aq email@example.com .