public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Kawa mailing list <kawa@sourceware.org>
Subject: kawa binary snapshot
Date: Mon, 06 Jun 2016 16:04:00 -0000	[thread overview]
Message-ID: <0f5f97f6-e993-f6e0-d20d-8305c33bb542@bothner.com> (raw)

I'm switching to a new "more complete" style of binary releases for Kawa.
Please check out:
     ftp://ftp.gnu.org/pub/gnu/kawa/kawa-2.1.9-20160605.zip

Later, we could perhaps set up automatically-generated binary snapshots.

This bundles not only the kawa .jar file, but also a shell script
(bin/kawa) or Windows batch file (bin/kawa.bat), along with version 3
of the jline input library.  This should be fairly portable.
The jline input editing doesn't seem to work on Windows (I need to
research how to fix this), but it works fine on Fedora and probably
most GNU/Linux distributions. Reports on how it works on *BSD and MacOS
would be helpful.

Using jline3 has a number of advantages:  In contrast to GNU readline,
it doesn't require compiling a C program, which makes it easier to
distribute binaries.  It supports command completion.   (Well, so does GNU
readline, but it's more complicated to write, especially if we want to
avoid subjecting Kawa to the GPL.)

The multi-line input editing is neat: While writing a continuation line,
you can go back and edit an earlier line in the multi-line command.
A continuation line is when you hit enter when more input is required
(such as inside parenthesis), or if you explicitly type Esc Enter or Ctrl-Q Ctrl-J.
Multi-line commands are stored as a single entry in the history.

More REPL improvements are planned.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

             reply	other threads:[~2016-06-06 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 16:04 Per Bothner [this message]
2016-06-06 20:44 ` Jamison Hope
2016-06-18 17:26   ` Per Bothner
2016-06-18 16:29 ` kawa binary snapshot with domterm-based console Per Bothner

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=0f5f97f6-e993-f6e0-d20d-8305c33bb542@bothner.com \
    --to=per@bothner.com \
    --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).