From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Enable/disable (was Re: Enhanced shell)
Date: Mon, 23 Jul 2001 16:38:50 +0000 [thread overview]
Message-ID: <1010723163850.ZM14004@candle.brasslantern.com> (raw)
In-Reply-To: <20010723150019.A25511@leeor.math.technion.ac.il>
On Jul 23, 3:00pm, Nadav Har'El wrote:
}
} On Mon, Jul 23, 2001, Oliver Kiddle wrote about "Re: Enhanced shell":
} > > ? disable/enable? [bash]
} > not so useful. they are also common as commands to enable/disable
} > printers (on AIX and Solaris at least).
}
} These are useful for restricted-shell mode, when you sometimes want to
} disable builtins (e.g., the "read" builtin allows the restricted user to
} read files that they shouldn't).
As of 4.0.1, `builtin read' will run `read' even after `disable read'.
Maybe we need to rethink that.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-23 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 22:47 Enhanced shell Peter Stephenson
2001-07-23 11:13 ` Oliver Kiddle
2001-07-23 11:38 ` Peter Stephenson
2001-07-23 18:03 ` Bart Schaefer
2001-07-24 13:42 ` Oliver Kiddle
2001-07-23 12:00 ` Nadav Har'El
2001-07-23 16:38 ` Bart Schaefer [this message]
2001-07-23 22:00 ` Enable/disable (was Re: Enhanced shell) Nadav Har'El
2001-07-24 1:12 ` Bart Schaefer
2001-07-24 2:45 ` Here-strings and $functions Bart Schaefer
2001-07-24 6:18 ` Bart Schaefer
2001-07-24 8:12 ` Sven Wischnowsky
2001-07-24 12:16 ` Bart Schaefer
2001-07-24 9:23 ` Enable/disable (was Re: Enhanced shell) Peter Stephenson
2001-07-24 12:10 ` PATCH: Doc errors (Re: Enable/disable (was Re: Enhanced shell)) Bart Schaefer
2001-07-29 9:53 ` Enhanced shell Zefram
2001-07-29 22:07 ` Peter Stephenson
2001-07-30 1:34 ` Bart Schaefer
2001-07-30 2:19 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1010723163850.ZM14004@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).