Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: autoload +X[zk]
- X-seq: zsh-workers 10301
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: autoload +X[zk]
- Date: Tue, 28 Mar 2000 18:27:38 +0000
- In-reply-to: <200003281152.NAA14996@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <200003281410.QAA20885@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200003281152.NAA14996@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200003281410.QAA20885@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Mar 28, 1:52pm, Sven Wischnowsky wrote:
} Subject: Re: autoload +X[zk]
}
} > Note also the handling of the positional parameters. For the first
} > call (i.e.: when the init code from the file is executed) they are not
} > set. Only for the appended function call are they set up. This is the
} > behaviour the ksh I have here shows.
}
} Damn. That doesn't work, because the printing functions just output
} `foo "$@"' for the not-really-existing call.
And the [[ -o kshautoload ]] || foo "$@" trick doesn't work if we
were to really emulate that ksh behavior, either, does it?
} Hm. What are we supposed to do here? Handle positional parameters
} differently?
For now, I think the answer is: Handle positional parameters like zsh
always has done for kshautoload (as you pointed out in 10298) and fix
the problem of accurately emulating ksh at a later time.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author