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: DomTerm/Kawa integration - two new features
Date: Tue, 02 Jan 2018 07:09:00 -0000	[thread overview]
Message-ID: <e4e1c40f-3eb8-3c41-cb99-f6744bbcb869@bothner.com> (raw)

The DomTerm terminal emulator (http://domterm.org) has two
new features Kawa users may find valuable.
(These require the latest Kawa from gitlab.)

(1) The Kawa REPL now supports moving the cursor by clicking the mouse
when run under DomTerm.  This works using either the readline front-end
(enabled by the configure flag --enable-kawa-frontend) or when using
the JLine3 input editor.  When editing multi-line commands using
JLine3 you can also move the cursor between lines, not just within a line.

Wrapped lines (longer than the terminal width) works,
as does middle-button paste.

This works by DomTerm calculating the "distance" between the
clicked position and current cursor position, and
sending the corresponding number of arrow-key events.

(2) Error and warning messages from the Kawa Compiler
are now emitted as clickable links with file: URLs.
By default, when you click on the link, it opens an
emacs window pointing at the erroneous position.
However, you can customize this:
http://domterm.org/Tips.html#link-handlers

The line-and-column location is turned into
'#position=LINE:COLUMN' added to the end of the URL.
If the file being loaded or compiled has a relative
file name, the file: URL will include the directory
path, though this won't show in the error message.
(You can see the actual URL by hovering over the link.)
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

                 reply	other threads:[~2018-01-02  7:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e4e1c40f-3eb8-3c41-cb99-f6744bbcb869@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).