{ "mode": "info", "parameter": "uudecode", "section": "", "url": "https://www.chedong.com/phpMan.php/info/uudecode/json", "generated": "2026-07-31T21:05:41Z", "sections": { "File: sharutils.info, Node: uudecode Invocation, Prev: uuencode Invocation, Up: Basic": { "content": "", "subsections": [ { "name": "2.4 Invoking uudecode", "content": "If no `file'(s) are provided, then standard input is decoded.\n`uudecode' transforms uuencoded files into their original form.\n\nThe encoded file(s) may be specified on the command line, or one may\nbe read from standard input. The output file name is specified in the\nencoded file, but may be overridden with the `-o' option. It will have\nthe mode of the original file, except that setuid and execute bits are\nnot retained. If the output file is specified to be `/dev/stdout' or\n`-', the result will be written to standard output. If there are\nmultiple input files and the second or subsquent file specifies\nstandard output, the decoded data will be written to the same file as\nthe previous output. Don't do that.\n\n`uudecode' ignores any leading and trailing lines. It looks for a\nline that starts with \"`begin'\" and proceeds until the end-of-encoding\nmarker is found. The program determines from the header line of the\nencoded file which of the two supported encoding schemes was used and\nwhether or not the output file name has been encoded with base64\nencoding. See `uuencode(5)'.\n\nThis section was generated by *AutoGen*, using the `agtexi-cmd'\ntemplate and the option descriptions for the `uudecode' program. This\nsoftware is released under the GNU General Public License, version 3 or\nlater.\n\n* Menu:\n\n* uudecode usage:: uudecode help/usage (`--help')\n* uudecode output-file:: output-file option (-o)\n* uudecode ignore-chmod:: ignore-chmod option (-c)\n* uudecode config:: presetting/configuring uudecode\n* uudecode exit status:: exit status\n* uudecode Bugs:: Bugs\n* uudecode Standards:: Standards\n* uudecode See Also:: See Also\n" } ] }, "File: sharutils.info, Node: uudecode usage, Next: uudecode output-file, Up: uudecode Invocation": { "content": "This is the automatically generated usage text for uudecode.\n\nThe text printed is the same whether selected with the `help' option\n(`--help') or the `more-help' option (`--more-help'). `more-help' will\nprint the usage text by passing it through a pager program.\n`more-help' is disabled on platforms without a working `fork(2)'\nfunction. The `PAGER' environment variable is used to select the\nprogram, defaulting to `more'. Both will exit with a status code of 0.\n\nuudecode (GNU sharutils) - decode an encoded file\nUsage: uudecode [ - [] | --[{=| }] ]... [...]\n\n-o, --output-file=str direct output to file\n-c, --ignore-chmod ignore fchmod(3P) errors\n-v, --version[=MODE] output version information and exit\n-h, --help display extended usage information and exit\n-!, --more-help extended usage information passed thru pager\n-R, --save-opts[=FILE] save the option state to a config file FILE\n-r, --load-opts=FILE load options from the config file FILE\n- disabled with '--no-load-opts'\n- may appear multiple times\n", "subsections": [] }, "Options are specified by doubled hyphens and their name or by a single": { "content": "hyphen and the flag character.\nIf no 'file'(s) are provided, then standard input is decoded.\n\nThe following option preset mechanisms are supported:\n- reading file $HOME/.sharrc\n\n'uudecode' transforms uuencoded files into their original form.\n", "subsections": [] }, "The encoded file(s) may be specified on the command line, or one may be": { "content": "read from standard input. The output file name is specified in the encoded\nfile, but may be overridden with the '-o' option. It will have the mode of\nthe original file, except that setuid and execute bits are not retained. If\nthe output file is specified to be '/dev/stdout' or '-', the result will be\nwritten to standard output. If there are multiple input files and the\nsecond or subsquent file specifies standard output, the decoded data will\nbe written to the same file as the previous output. Don't do that.\n\n'uudecode' ignores any leading and trailing lines. It looks for a line\nthat starts with \"'begin'\" and proceeds until the end-of-encoding marker is\nfound. The program determines from the header line of the encoded file\nwhich of the two supported encoding schemes was used and whether or not the\noutput file name has been encoded with base64 encoding. See 'uuencode(5)'.\n\nPlease send bug reports to: \n", "subsections": [] }, "File: sharutils.info, Node: uudecode output-file, Next: uudecode ignore-chmod, Prev: uudecode usage, Up: uudecode Invocation": { "content": "This is the \"direct output to `file'\" option. This option takes a\nstring argument `file'. If specified, decoded data are written to this\nfile. When multiple inputs are specified on the command line, this\noption cannot be specified. All decoded data must be written to the\nfile name encoded in the data.\n", "subsections": [] }, "File: sharutils.info, Node: uudecode ignore-chmod, Next: uudecode config, Prev: uudecode output-file, Up: uudecode Invocation": { "content": "This is the \"ignore `fchmod(3p)' errors\" option. By default, if the\noutput file permissions cannot be changed to the permissions specified\nin the encoded data, the file will not be written out and execution\nstops. This option will cause that error to be ignored. The resulting\nfile will have all the data, but the incorrect mode settings.\n\n`fchmod()' errors are also ignored if `POSIXLYCORRECT' is set in\nthe environment. RE: \n\nA warning is always emitted when `fchmod()' fails.\n", "subsections": [] }, "File: sharutils.info, Node: uudecode config, Next: uudecode exit status, Prev: uudecode ignore-chmod, Up: uudecode Invocation": { "content": "", "subsections": [] }, "Any option that is not marked as not presettable may be preset by": { "content": "loading values from configuration (\"rc\" or \"ini\") files.\n\n`libopts' will search in `$HOME' for configuration (option) data. The\nenvironment variable `HOME, ' is expanded and replaced when the program\nruns If this is a plain file, it is simply processed. If it is a\ndirectory, then a file named `.sharrc' is searched for within that\ndirectory.\n\nConfiguration files may be in a wide variety of formats. The basic\nformat is an option name followed by a value (argument) on the same\nline. Values may be separated from the option name with a colon, equal\nsign or simply white space. Values may be continued across multiple\nlines by escaping the newline with a backslash.\n\nMultiple programs may also share the same initialization file.", "subsections": [] }, "Common options are collected at the top, followed by program specific": { "content": "segments. The segments are separated by lines like:\n[UUDECODE]\nor by\n\nDo not mix these styles within one configuration file.\n\nCompound values and carefully constructed string values may also be\nspecified using XML syntax:\n\n...<...>...\n\nyielding an `option-name.sub-opt' string value of\n\"...<...>...\"\n`AutoOpts' does not track suboptions. You simply note that it is a\nhierarchicly valued option. `AutoOpts' does provide a means for\nsearching the associated name/value pair list (see: optionFindValue).\n\nThe command line options relating to configuration and/or usage help\nare:\n\nversion (-v)\n............\n", "subsections": [] }, "Print the program version to standard out, optionally with licensing": { "content": "information, then exit 0. The optional argument specifies how much\nlicensing detail to provide. The default is to print the license name\nwith the version. The licensing infomation may be selected with an\noption argument. Only the first letter of the argument is examined:\n\n`version'\nOnly print the version.\n\n`copyright'\nName the copyright usage licensing terms. This is the default.\n\n`verbose'\nPrint the full copyright usage licensing terms.\n", "subsections": [] }, "File: sharutils.info, Node: uudecode exit status, Next: uudecode Bugs, Prev: uudecode config, Up: uudecode Invocation": { "content": "One of the following exit values will be returned:\n`0 (EXITSUCCESS)'\nSuccessful program execution.\n\n`1 (EXITOPTIONERROR)'\nThe command options were misconfigured.\n\n`2 (EXITINVALID)'\n(warning) One or more input files contained no valid data\n\n`4 (EXITNOINPUT)'\n(warning) The specified input file was not found\n\n`8 (EXITNOOUTPUT)'\nThe specified output file could not be created (error); or else\none of the output files could not be written or its access mode\ncould not be changed (warnings). The accompanying message(s) will\ndistinguish.\n\n`9 (EXITNOMEM)'\nNo process memory available\n\n`66 (EXNOINPUT)'\nA specified configuration file could not be loaded.\n\n`70 (EXSOFTWARE)'\nlibopts had an internal operational error. Please report it to\nautogen-users@lists.sourceforge.net. Thank you.\n", "subsections": [] }, "File: sharutils.info, Node: uudecode Bugs, Next: uudecode Standards, Prev: uudecode exit status, Up: uudecode Invocation": { "content": "Please put `sharutils' in the subject line for emailed bug reports. It\nhelps to spot the message.\n\nIf more than one `name' in the encoded files are the same, or if the\nsecond or following input files specifies standard output for the\noutput file, then the result is probably not what is expected.", "subsections": [] }, "Specifically, standard output will be appended to and named output": { "content": "files will be replaced.\n", "subsections": [] }, "File: sharutils.info, Node: uudecode Standards, Next: uudecode See Also, Prev: uudecode Bugs, Up: uudecode Invocation": { "content": "This implementation is compliant with P1003.2b/D11.\n", "subsections": [] }, "File: sharutils.info, Node: uudecode See Also, Prev: uudecode Standards, Up: uudecode Invocation": { "content": "uuencode(1), uuencode(5)\n", "subsections": [] } }, "flags": [], "examples": [], "see_also": [] }