Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: db module
- X-seq: zsh-workers 17781
- From: Clint Adams <clint@xxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: db module
- Date: Sun, 6 Oct 2002 13:31:13 -0400
- Cc: Zsh workers <zsh-workers@xxxxxxxxxx>
- In-reply-to: <1021006171435.ZM11988@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <E17w1iC-00012d-00@xxxxxxxxxxxxxxxxxx> <20021006053229.GA14350@xxxxxxxx> <20021006122451.GV24160@xxxxxxxxxxxxxxxxxxxxx> <1021006164658.ZM11928@xxxxxxxxxxxxxxxxxxxxxxx> <20021006170353.GA531@xxxxxxxx> <1021006171435.ZM11988@xxxxxxxxxxxxxxxxxxxxxxx>
> Yes, except that, like e.g. the stat module's -A and -H options, I was
> thinking that the name of the parameter to which to assign would be an
> argument to the db_get function so that the $(...) would not be needed.
Well, that should be the simplest part to implement.
So, if a function with a name ending in .{get,set,unset} is defined,
param.{gets,sets,unsetfn} should be modified accordingly, and restored
upon unfunction. When param.{gets,sets,unsetfn} are invoked,
.sh.{name,subscript} and sometimes .sh.value need to be set to the
appropriate strings.
I don't think I understand how adding more discipline functions via
ksh's builtin builtin works, so I don't know if it would be useful to
keep in mind.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author