NetBSD/bin/sh/options.c

647 lines
14 KiB
C
Raw Normal View History

/* $NetBSD: options.c,v 1.56 2021/10/26 00:05:38 kre Exp $ */
1995-03-21 12:01:59 +03:00
1993-03-21 12:45:37 +03:00
/*-
1994-05-11 21:09:42 +04:00
* Copyright (c) 1991, 1993
* The Regents of the University of California. All rights reserved.
1993-03-21 12:45:37 +03:00
*
* This code is derived from software contributed to Berkeley by
* Kenneth Almquist.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. Neither the name of the University nor the names of its contributors
1993-03-21 12:45:37 +03:00
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/
1997-07-05 01:01:48 +04:00
#include <sys/cdefs.h>
1993-03-21 12:45:37 +03:00
#ifndef lint
1995-03-21 12:01:59 +03:00
#if 0
static char sccsid[] = "@(#)options.c 8.2 (Berkeley) 5/4/95";
1995-03-21 12:01:59 +03:00
#else
__RCSID("$NetBSD: options.c,v 1.56 2021/10/26 00:05:38 kre Exp $");
1995-03-21 12:01:59 +03:00
#endif
1993-03-21 12:45:37 +03:00
#endif /* not lint */
#include <signal.h>
#include <unistd.h>
#include <stdlib.h>
1993-03-21 12:45:37 +03:00
#include "shell.h"
#define DEFINE_OPTIONS
#include "options.h"
#undef DEFINE_OPTIONS
#include "builtins.h"
1993-03-21 12:45:37 +03:00
#include "nodes.h" /* for other header files */
#include "eval.h"
#include "jobs.h"
#include "input.h"
#include "output.h"
#include "trap.h"
#include "var.h"
#include "memalloc.h"
#include "error.h"
#include "mystring.h"
#include "syntax.h"
1997-03-14 04:42:18 +03:00
#ifndef SMALL
#include "myhistedit.h"
#endif
#include "show.h"
1993-03-21 12:45:37 +03:00
char *arg0; /* value of $0 */
struct shparam shellparam; /* current positional parameters */
char **argptr; /* argument list for builtin commands */
char *optionarg; /* set by nextopt (like getopt) */
1993-03-21 12:45:37 +03:00
char *optptr; /* used by nextopt */
char *minusc; /* argument to -c option */
STATIC void options(int);
STATIC void minus_o(char *, int);
STATIC void setoption(int, int);
STATIC int getopts(char *, char *, char **, char ***, char **);
1993-03-21 12:45:37 +03:00
/*
* Process the shell command line arguments.
*/
void
procargs(int argc, char **argv)
{
2009-01-18 03:24:29 +03:00
size_t i;
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
int psx;
1993-03-21 12:45:37 +03:00
argptr = argv;
if (argc > 0)
argptr++;
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
psx = posix; /* save what we set it to earlier */
/*
* option values are mostly boolean 0:off 1:on
* we use 2 (just in this routine) to mean "unknown yet"
*/
1994-05-11 21:09:42 +04:00
for (i = 0; i < NOPTS; i++)
optlist[i].val = 2;
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
posix = psx; /* restore before processing -o ... */
1993-03-21 12:45:37 +03:00
options(1);
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
1993-03-21 12:45:37 +03:00
if (*argptr == NULL && minusc == NULL)
sflag = 1;
if (iflag == 2 && sflag == 1 && isatty(0) && isatty(2))
1993-03-21 12:45:37 +03:00
iflag = 1;
if (iflag == 1 && sflag == 2)
iflag = 2;
1994-05-11 21:09:42 +04:00
if (mflag == 2)
mflag = iflag;
#ifndef DO_SHAREDVFORK
if (usefork == 2)
usefork = 1;
#endif
#if DEBUG >= 2
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
if (debug == 2)
debug = 1;
#endif
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
/*
* Any options not dealt with as special cases just above,
* and which were not set on the command line, are set to
* their expected default values (mostly "off")
*
* then as each option is initialised, save its setting now
* as its "default" value for future use ("set -o default").
*/
for (i = 0; i < NOPTS; i++) {
if (optlist[i].val == 2)
optlist[i].val = optlist[i].dflt;
optlist[i].dflt = optlist[i].val;
}
1993-03-21 12:45:37 +03:00
arg0 = argv[0];
if (sflag == 0 && minusc == NULL) {
commandname = argv[0];
arg0 = *argptr++;
setinputfile(arg0, 0);
commandname = arg0;
1993-03-21 12:45:37 +03:00
}
/* POSIX 1003.2: first arg after -c cmd is $0, remainder $1... */
if (minusc != NULL) {
if (argptr == NULL || *argptr == NULL)
error("Bad -c option");
minusc = *argptr++;
if (*argptr != 0)
arg0 = *argptr++;
}
1993-03-21 12:45:37 +03:00
shellparam.p = argptr;
shellparam.reset = 1;
1993-03-21 12:45:37 +03:00
/* assert(shellparam.malloc == 0 && shellparam.nparam == 0); */
while (*argptr) {
shellparam.nparam++;
argptr++;
}
1994-05-11 21:09:42 +04:00
optschanged();
1993-03-21 12:45:37 +03:00
}
void
optschanged(void)
{
1994-05-11 21:09:42 +04:00
setinteractive(iflag);
1997-03-14 04:42:18 +03:00
#ifndef SMALL
1994-05-11 21:09:42 +04:00
histedit();
#endif
1994-05-11 21:09:42 +04:00
setjobctl(mflag);
if (privileged && !pflag) {
setuid(getuid());
setgid(getgid());
privileged = 0;
setvarsafe("PSc", (getuid() == 0 ? "#" : "$"), 0);
}
1994-05-11 21:09:42 +04:00
}
1993-03-21 12:45:37 +03:00
/*
* Process shell options. The global variable argptr contains a pointer
* to the argument list; we advance it past the options.
*/
STATIC void
options(int cmdline)
{
2004-10-30 23:29:27 +04:00
static char empty[] = "";
1997-01-11 05:04:27 +03:00
char *p;
1993-03-21 12:45:37 +03:00
int val;
int c;
if (cmdline)
minusc = NULL;
while ((p = *argptr) != NULL) {
argptr++;
if ((c = *p++) == '-') {
val = 1;
if (p[0] == '\0' || (p[0] == '-' && p[1] == '\0')) {
1993-03-21 12:45:37 +03:00
if (!cmdline) {
/* "-" means turn off -x and -v */
if (p[0] == '\0')
xflag = vflag = 0;
/* "--" means reset params */
else if (*argptr == NULL)
setparam(argptr);
1993-03-21 12:45:37 +03:00
}
break; /* "-" or "--" terminates options */
}
} else if (c == '+') {
val = 0;
} else {
argptr--;
break;
}
while ((c = *p++) != '\0') {
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
if (val == 1 && c == 'c' && cmdline) {
2004-10-30 23:29:27 +04:00
/* command is after shell args*/
minusc = empty;
1994-05-11 21:09:42 +04:00
} else if (c == 'o') {
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
if (*p != '\0')
minus_o(p, val + (cmdline ? val : 0));
else if (*argptr)
minus_o(*argptr++,
val + (cmdline ? val : 0));
else if (!cmdline)
minus_o(NULL, val);
else
error("arg for %co missing", "+-"[val]);
break;
#ifdef DEBUG
} else if (c == 'D') {
if (*p) {
set_debug(p, val);
break;
} else if (*argptr)
set_debug(*argptr++, val);
else
set_debug("*$", val);
#endif
1993-03-21 12:45:37 +03:00
} else {
setoption(c, val);
}
}
}
}
static void
2009-01-18 03:24:29 +03:00
set_opt_val(size_t i, int val)
{
2009-01-18 03:24:29 +03:00
size_t j;
int flag;
if (val && (flag = optlist[i].opt_set)) {
/* some options (eg vi/emacs) are mutually exclusive */
for (j = 0; j < NOPTS; j++)
if (optlist[j].opt_set == flag)
optlist[j].val = 0;
}
#ifndef SMALL
if (i == _SH_OPT_Xflag)
xtracefdsetup(val);
#endif
optlist[i].val = val;
#ifdef DEBUG
if (&optlist[i].val == &debug)
opentrace(); /* different "trace" than the -x one... */
#endif
}
1994-05-11 21:09:42 +04:00
STATIC void
minus_o(char *name, int val)
1994-05-11 21:09:42 +04:00
{
2009-01-18 03:24:29 +03:00
size_t i;
const char *sep = ": ";
1994-05-11 21:09:42 +04:00
if (name == NULL) {
if (val) {
out1str("Current option settings");
for (i = 0; i < NOPTS; i++) {
if (optlist[i].name == NULL) {
out1fmt("%s%c%c", sep,
"+-"[optlist[i].val],
optlist[i].letter);
sep = ", ";
}
}
out1c('\n');
for (i = 0; i < NOPTS; i++) {
if (optlist[i].name)
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
out1fmt("%-19s %s\n", optlist[i].name,
optlist[i].val ? "on" : "off");
}
} else {
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
out1str("set -o default");
for (i = 0; i < NOPTS; i++) {
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
if (optlist[i].val == optlist[i].dflt)
continue;
if (optlist[i].name)
out1fmt(" %co %s",
"+-"[optlist[i].val], optlist[i].name);
else
out1fmt(" %c%c", "+-"[optlist[i].val],
optlist[i].letter);
}
out1c('\n');
}
1994-05-11 21:09:42 +04:00
} else {
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
if (val == 1 && equal(name, "default")) { /* special case */
for (i = 0; i < NOPTS; i++)
set_opt_val(i, optlist[i].dflt);
return;
}
if (val)
val = 1;
1994-05-11 21:09:42 +04:00
for (i = 0; i < NOPTS; i++)
if (optlist[i].name && equal(name, optlist[i].name)) {
set_opt_val(i, val);
#ifndef SMALL
if (i == _SH_OPT_Xflag)
set_opt_val(_SH_OPT_xflag, val);
#endif
1994-05-11 21:09:42 +04:00
return;
}
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
error("Illegal option %co %s", "+-"[val], name);
1994-05-11 21:09:42 +04:00
}
}
1993-03-21 12:45:37 +03:00
STATIC void
setoption(int flag, int val)
{
2009-01-18 03:24:29 +03:00
size_t i;
1994-05-11 21:09:42 +04:00
for (i = 0; i < NOPTS; i++)
if (optlist[i].letter == flag) {
set_opt_val(i, val);
#ifndef SMALL
if (i == _SH_OPT_Xflag)
set_opt_val(_SH_OPT_xflag, val);
#endif
1994-05-11 21:09:42 +04:00
return;
}
Command line, and "set" command options processing cleanup. sh +c "command string" no longer works (it must be -c) sh +o and sh -o no longer work (if you could call what they did before working.) nb: this is without an option name. -ooo Opt1 Opt2 Opt3 no longer works (set & cmd line), this should be -o Opt1 -o Opt2 -o Opt3 (same with +ooo of course). -oOpt is now supported - option value (name of option in this case) immediately following -o (or +o). (as with other commands that use std opt parsing) Both set comamnd and command line. In addition, the output from "set +o" has shrunk dramatically, by borrowing a trick from ksh93 (but implemented in a more traditional syntax). "set +o" is required to produce a command (or commands) which when executed later, will return all options to the state they were in when "set +o" was done. Previously that was done by generating a set command, with every option listed (set -o opt +o other-opt ...) to set them all back to their current setings. Now we have a new "magic option" ("default") which sets all options to their default values, so now set +o output need only be "set -o default -o changed-opt ..." (only the options that have been changed from their default values need be explicitly mentioned.) The definition of "default value" for this is the value the shell set the option to, after startup, after processing the command line (with any flags, or -o option type settings), but before beginning processing any user input (incuding startup files, like $ENV etc). Anyone can execute "set -o default" of course, but only from a "set" command (it makes no sense at all as a -o option to sh). This also causes "set +o" to be slightly more useful as a general command, as ignoring the "set -o default" part of the result, it lists just those options that have been altered after sh startup. There is no +o default. There isn't an option called "default" at all... This causes some of the commented out text from sh.1 to become uncommented.
2017-05-18 16:53:18 +03:00
error("Illegal option %c%c", "+-"[val], flag);
/* NOTREACHED */
1993-03-21 12:45:37 +03:00
}
#ifdef mkinit
INCLUDE "options.h"
SHELLPROC {
1994-05-11 21:09:42 +04:00
int i;
for (i = 0; optlist[i].name; i++)
1994-05-11 21:09:42 +04:00
optlist[i].val = 0;
optschanged();
1993-03-21 12:45:37 +03:00
}
#endif
/*
* Set the shell parameters.
*/
void
setparam(char **argv)
{
1993-03-21 12:45:37 +03:00
char **newparam;
char **ap;
int nparam;
2005-03-21 00:38:17 +03:00
for (nparam = 0 ; argv[nparam] ; nparam++)
continue;
1993-03-21 12:45:37 +03:00
ap = newparam = ckmalloc((nparam + 1) * sizeof *ap);
while (*argv) {
*ap++ = savestr(*argv++);
}
*ap = NULL;
freeparam(&shellparam);
shellparam.malloc = 1;
shellparam.nparam = nparam;
shellparam.p = newparam;
shellparam.optnext = NULL;
}
/*
* Free the list of positional parameters.
*/
void
freeparam(volatile struct shparam *param)
{
1993-03-21 12:45:37 +03:00
char **ap;
if (param->malloc) {
for (ap = param->p ; *ap ; ap++)
ckfree(*ap);
ckfree(param->p);
}
}
/*
* The shift builtin command.
*/
int
shiftcmd(int argc, char **argv)
{
1993-03-21 12:45:37 +03:00
int n;
char **ap1, **ap2;
if (argc > 2)
error("Usage: shift [n]");
1993-03-21 12:45:37 +03:00
n = 1;
if (argc > 1)
n = number(argv[1]);
if (n > shellparam.nparam)
1994-05-11 21:09:42 +04:00
error("can't shift that many");
1993-03-21 12:45:37 +03:00
INTOFF;
shellparam.nparam -= n;
for (ap1 = shellparam.p ; --n >= 0 ; ap1++) {
if (shellparam.malloc)
ckfree(*ap1);
}
ap2 = shellparam.p;
while ((*ap2++ = *ap1++) != NULL)
continue;
1993-03-21 12:45:37 +03:00
shellparam.optnext = NULL;
INTON;
return 0;
}
/*
* The set command builtin.
*/
int
setcmd(int argc, char **argv)
{
1993-03-21 12:45:37 +03:00
if (argc == 1)
return showvars(0, 0, 1, 0);
1993-03-21 12:45:37 +03:00
INTOFF;
options(0);
1994-05-11 21:09:42 +04:00
optschanged();
1993-03-21 12:45:37 +03:00
if (*argptr != NULL) {
setparam(argptr);
}
INTON;
return 0;
}
void
2012-03-20 22:42:28 +04:00
getoptsreset(const char *value)
{
/*
* This is just to detect the case where OPTIND=1
* is executed. Any other string assigned to OPTIND
* is OK, but is not a reset. No errors, so cannot use number()
*/
if (is_digit(*value) && strtol(value, NULL, 10) == 1) {
shellparam.optnext = NULL;
shellparam.reset = 1;
}
}
1993-03-21 12:45:37 +03:00
/*
* The getopts builtin. Shellparam.optnext points to the next argument
* to be processed. Shellparam.optptr points to the next character to
* be processed in the current argument. If shellparam.optnext is NULL,
* then it's the first time getopts has been called.
*/
int
getoptscmd(int argc, char **argv)
{
char **optbase;
if (argc < 3)
error("usage: getopts optstring var [arg]");
else if (argc == 3)
optbase = shellparam.p;
else
optbase = &argv[3];
1993-03-21 12:45:37 +03:00
if (shellparam.reset == 1) {
shellparam.optnext = optbase;
1993-03-21 12:45:37 +03:00
shellparam.optptr = NULL;
shellparam.reset = 0;
1993-03-21 12:45:37 +03:00
}
return getopts(argv[1], argv[2], optbase, &shellparam.optnext,
&shellparam.optptr);
}
STATIC int
getopts(char *optstr, char *optvar, char **optfirst, char ***optnext, char **optpptr)
{
1997-01-11 05:04:27 +03:00
char *p, *q;
char c = '?';
int done = 0;
int ind = 0;
int err = 0;
char s[12];
1999-07-09 07:05:49 +04:00
if ((p = *optpptr) == NULL || *p == '\0') {
/* Current word is done, advance */
if (*optnext == NULL)
return 1;
p = **optnext;
1993-03-21 12:45:37 +03:00
if (p == NULL || *p != '-' || *++p == '\0') {
atend:
ind = *optnext - optfirst + 1;
*optnext = NULL;
p = NULL;
done = 1;
goto out;
1993-03-21 12:45:37 +03:00
}
(*optnext)++;
1993-03-21 12:45:37 +03:00
if (p[0] == '-' && p[1] == '\0') /* check for "--" */
goto atend;
}
1993-03-21 12:45:37 +03:00
c = *p++;
for (q = optstr; *q != c; ) {
1993-03-21 12:45:37 +03:00
if (*q == '\0') {
if (optstr[0] == ':') {
s[0] = c;
s[1] = '\0';
err |= setvarsafe("OPTARG", s, 0);
} else {
outfmt(&errout, "Illegal option -%c\n", c);
(void) unsetvar("OPTARG", 0);
}
1993-03-21 12:45:37 +03:00
c = '?';
goto bad;
1993-03-21 12:45:37 +03:00
}
if (*++q == ':')
q++;
}
1993-03-21 12:45:37 +03:00
if (*++q == ':') {
if (*p == '\0' && (p = **optnext) == NULL) {
if (optstr[0] == ':') {
s[0] = c;
s[1] = '\0';
err |= setvarsafe("OPTARG", s, 0);
c = ':';
} else {
outfmt(&errout, "No arg for -%c option\n", c);
(void) unsetvar("OPTARG", 0);
c = '?';
}
goto bad;
1993-03-21 12:45:37 +03:00
}
if (p == **optnext)
(*optnext)++;
err |= setvarsafe("OPTARG", p, 0);
1993-03-21 12:45:37 +03:00
p = NULL;
} else
err |= setvarsafe("OPTARG", "", 0);
ind = *optnext - optfirst + 1;
goto out;
bad:
ind = 1;
*optnext = NULL;
p = NULL;
1993-03-21 12:45:37 +03:00
out:
1999-07-09 07:05:49 +04:00
*optpptr = p;
fmtstr(s, sizeof(s), "%d", ind);
err |= setvarsafe("OPTIND", s, VNOFUNC);
1993-03-21 12:45:37 +03:00
s[0] = c;
s[1] = '\0';
err |= setvarsafe(optvar, s, 0);
if (err) {
*optnext = NULL;
1999-07-09 07:05:49 +04:00
*optpptr = NULL;
flushall();
exraise(EXERROR);
}
return done;
1993-03-21 12:45:37 +03:00
}
/*
1994-05-11 21:09:42 +04:00
* XXX - should get rid of. have all builtins use getopt(3). the
* library getopt must have the BSD extension static variable "optreset"
* otherwise it can't be used within the shell safely.
*
1993-03-21 12:45:37 +03:00
* Standard option processing (a la getopt) for builtin routines. The
* only argument that is passed to nextopt is the option string; the
* other arguments are unnecessary. It return the character, or '\0' on
* end of input. If optstring is NULL, then there are no options, and
* args are allowed to begin with '-', but a single leading "--" will be
* discarded. This is for some POSIX special builtins that require
* -- processing, have no args, and we never did opt processing before
* and need to retain backwards compat.
1993-03-21 12:45:37 +03:00
*/
int
nextopt(const char *optstring)
{
1999-07-09 07:05:49 +04:00
char *p;
const char *q;
1993-03-21 12:45:37 +03:00
char c;
if ((p = optptr) == NULL || *p == '\0') {
p = *argptr;
if (p == NULL || *p != '-' || *++p == '\0')
return '\0';
argptr++;
if (p[0] == '-' && p[1] == '\0') /* check for "--" */
return '\0';
if (optstring == NULL) /* not processing the "option" */
argptr--; /* so make it be an arg again */
1993-03-21 12:45:37 +03:00
}
if (optstring == NULL)
return '\0';
1993-03-21 12:45:37 +03:00
c = *p++;
for (q = optstring ; *q != c ; ) {
if (*q == '\0')
error("Illegal option -%c", c);
if (*++q == ':')
q++;
}
if (*++q == ':') {
if (*p == '\0' && (p = *argptr++) == NULL)
error("No arg for -%c option", c);
optionarg = p;
1993-03-21 12:45:37 +03:00
p = NULL;
}
optptr = p;
return c;
}