From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: Re: Compsys and KSH_AUTOLOAD
Date: Mon, 19 Apr 2004 00:14:34 +0000 [thread overview]
Message-ID: <1040419001434.ZM9151@candle.brasslantern.com> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2004-04-19 0:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 17:44 Bart Schaefer
2004-04-12 14:00 ` Oliver Kiddle
2004-04-12 15:59 ` Bart Schaefer
2004-04-12 21:43 ` Oliver Kiddle
2004-04-13 5:32 ` While we're on the subject of zcompile Bart Schaefer
2004-04-17 21:08 ` Oliver Kiddle
2004-04-13 5:38 ` Compsys and KSH_AUTOLOAD Bart Schaefer
2004-04-13 15:29 ` PATCH: " Oliver Kiddle
2004-04-13 17:51 ` Bart Schaefer
2004-04-16 16:49 ` Oliver Kiddle
2004-04-16 17:25 ` Bart Schaefer
2004-04-18 13:46 ` Oliver Kiddle
2004-04-16 17:30 ` Bart Schaefer
2004-04-17 19:51 ` Oliver Kiddle
2004-04-19 0:14 ` Bart Schaefer [this message]
2004-04-19 10:18 ` Oliver Kiddle
2004-04-20 4:11 ` Bart Schaefer
2004-04-20 10:08 ` Oliver Kiddle
2004-04-14 5:04 ` Bart Schaefer
2004-04-14 19:55 ` Peter Stephenson
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=1040419001434.ZM9151@candle.brasslantern.com \
--to=schaefer@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).