From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: problem with 310
Date: Fri, 20 Feb 2015 20:58:50 -0800 [thread overview]
Message-ID: <54E8108A.40907@eastlink.ca> (raw)
In-Reply-To: <150220203536.ZM12273@torch.brasslantern.com>
On 02/20/2015 08:35 PM, Bart Schaefer wrote:
> On Feb 20, 8:27pm, Ray Andrews wrote:
> }
> } ... all is well. Seems the function directory has moved from ...dev-0
> } to ...dev-1. Why at this juncture?
>
> The version number was changed because some new tokens were added to
> the parser, which affects various things such as testing compatibility
> of files created with the "zcompile" builtin.
>
Ok. 'make install' seemed to update the functions so I figger I'm all good.
prev parent reply other threads:[~2015-02-21 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 2:16 Ray Andrews
2015-02-21 2:47 ` Bart Schaefer
2015-02-21 4:05 ` Ray Andrews
2015-02-21 4:27 ` Ray Andrews
2015-02-21 4:35 ` Bart Schaefer
2015-02-21 4:58 ` Ray Andrews [this message]
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=54E8108A.40907@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-workers@zsh.org \
/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).