Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Re: Compsys and KSH_AUTOLOAD
- X-seq: zsh-workers 19793
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: Re: Compsys and KSH_AUTOLOAD
- Date: Mon, 19 Apr 2004 00:14:34 +0000
- In-reply-to: <11049.1082231519@athlon>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <1040410174430.ZM10891@xxxxxxxxxxxxxxxxxxxxxxx> <1170.1081778412@athlon> <040412085942.ZM19035@xxxxxxxxxxxxxxxxxxxxxxx> <3571.1081806187@athlon> <1040413053826.ZM20012@xxxxxxxxxxxxxxxxxxxxxxx> <18035.1081870188@xxxxxxxxxxxxxxxxxxxxx> <1040413175111.ZM21011@xxxxxxxxxxxxxxxxxxxxxxx> <13987.1082134179@xxxxxxxxxxxxxxxxxxxxx> <1040416173016.ZM1145@xxxxxxxxxxxxxxxxxxxxxxx> <11049.1082231519@athlon>
On Apr 17, 9:51pm, Oliver Kiddle wrote:
} Subject: Re: PATCH: Re: Compsys and KSH_AUTOLOAD
}
} > Test Test/B02typeset.ztst failed: bad status 0, expected 1 from: declare +m
}
} That's this test:
}
} declare +m
} 1:Differences of declare and typeset
} ?(eval):1: bad option: -m
}
} I noticed the missing `m' in the list of declare options when checking
} the completion function was consistent with the code. I assumed that
} was an oversight.
At the very top of that Test/B02typeset.ztst there is:
# Equivalences:
# declare typeset but declare does not accept -m
(etc.)
"cvs annotate" says I committed the firet-ever revision of this, which
included that test, but I'm afraid I don't remember why "declare" does
not support -m unless it's "just in case" bash's declare later starts
taking a -m option and we wanted to reserve it for future compatibility.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author