From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org, Jason Hemann <jhemann@iu.edu>
Subject: Re: Error when starting KaShell language
Date: Thu, 05 Dec 2019 19:41:00 -0000 [thread overview]
Message-ID: <302f02b3-c52d-3539-b08f-7fd985119d13@bothner.com> (raw)
In-Reply-To: <CAKp_QW2NSQ6Vg78BJOTSqAv+cu5seKFrYLt2jQVHrWNOEW9jBw@mail.gmail.com>
On 12/5/19 10:14 AM, Jason Hemann wrote:
> Hi all,
>
> I wanted to play with the KaShell language (http://kashell.org/), and I
> believe I followed the instructions to start. However, I see the following
> error message when I try:
>
> ````
> bash-3.2$ kawa --version
> Kawa 3.0 (git describe: 3.0-0-g39797ea94)
> Copyright (C) 2017 Per Bothner
That's pretty old. Try the HEAD version from gitlab.
(I'm working on getting a 3.1 release out. A few minor things to do,
mainly documentation, but no promises when it will get done.)
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2019-12-05 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 18:15 Jason Hemann
2019-12-05 19:41 ` Per Bothner [this message]
2019-12-05 20:50 ` [External] " Jason Hemann
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=302f02b3-c52d-3539-b08f-7fd985119d13@bothner.com \
--to=per@bothner.com \
--cc=jhemann@iu.edu \
--cc=kawa@sourceware.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).