Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: 4.1.0: `builtin' with disabled builtin.
- X-seq: zsh-workers 14942
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Peter Stephenson <pws@xxxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx (Zsh hackers list)
- Subject: Re: PATCH: 4.1.0: `builtin' with disabled builtin.
- Date: Sat, 16 Jun 2001 04:35:09 +0000
- In-reply-to: <20010615230613.D5F131428B@xxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20010615230613.D5F131428B@xxxxxxxxxxxxxxxxxxxxxxxx>
On Jun 16, 12:06am, Peter Stephenson wrote:
} Subject: PATCH: 4.1.0: `builtin' with disabled builtin.
}
} It used to be possible to get round the fact that a builtin was disabled by
} putting `builtin' in front of it, which somehow disappeared when I wasn't
} looking.
That's been gone since sometime in 2.5 or 2.6, whenever it was that real
hash tables replaced linked lists for command lookup. I don't think it
has ever worked in any 3.x version.
} I think the old behaviour is useful and harmless.
Unless one is trying to use disable to create a restricted shell. Then
one has to disable builtin as well, which might not be desirable for
other reasons.
} Does anyone have any worries about this?
I don't feel strongly one way or the other; I have a slight preference
for the v >= 3.0 behavior rather than the v <= 2.4 behavior, but not so
much as to carry on a lengthy disagreement about it.
--
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author