public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "F. Rafael Leon" <teflon@ucdavis.edu>
To: kawa@sourceware.org
Subject: Re: What is the Development Environment of Choice for Kawa?
Date: Thu, 18 Feb 2016 18:53:00 -0000	[thread overview]
Message-ID: <CALPCXwiy=y6Ss1aZYHxTGr9QhkQ01GpH3byF+S=sF4r0dOx6Ew@mail.gmail.com> (raw)

On Thu, Feb 18, 2016 at 11:18 AM, Rafik Naccache [TNTeam]
<rafik@tnteam.rocks> wrote:
> I really would love to take community's pulse on what tool is used by
> Kawa-ians

Rafik,

The correct answer to this is "whatever makes you most comfortable."

In order to vividly illuminate what this means in practice, I will
explain MY own strange workflow so that you can feel comfortable
adopting YOUR own strange workflow:

It starts with emacs.

To emacs, I add the "evil" package which provides vim bindings.
"evil" can be found in the melpa or marmalade repositories.
The standard emacs control-meta-alt-shift s-x-w-y simultaneous chords
give me horrible finger cramps, so I prefer vim. For editing code I
really like the buffer system of emacs.
So, I use emacs with vim bindings.

Theoretically, if I were a better person, I would use paredit instead of evil.

In a separate terminal, NOT in an emacs buffer, I run "rlwrap java
kawa.repl" with an appropriate CLASSPATH for my project.

In emacs, I write some code and save it in "project.scm"

In the rlwrap kawa console, I type (load "project.scm").

I then edit project.scm in emacs and then type the up arrow into the
rlwrap kawa console to repeat the load command and then I hit Enter.

I repeat this process around 1000 times a day.

When doing this for Android, the workflow is identical, except instead
of "rlwrap kawa" I run "rlwrap telnet x.x.x.x 4444" to connect to a
telnet REPL running on the Android device. Also, after each edit and
save in emacs I run "adb push project.scm /sdcard" and then in the
telnet terminal: (load "/sdcard/project.scm").

That's basically it.  I should do a YouTube.

I DON'T run kawa in an emacs buffer because often I like to (display
... ) or (write ... ) lists and look at them.

This dumps thousands of lines of stupidity that I don't want to look
at ever again after I solve the immediate problem.  I don't want
thousands of lines of REPL output saved in an emacs buffer.  As I jump
between emacs buffers, I don't want to glance at a big wasteland of
failed algorithms. It makes me feel like emacs is watching me and
laughing.

If I never made any mistakes and never was unsure about any algorithm,
then a REPL in a buffer would be totally awesome because I could
record and save all my brilliance for all eternity.
Instead, every time I put a REPL in a buffer I just feel embarrassed
when I scroll through it.

      -Rafael

             reply	other threads:[~2016-02-18 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 18:53 F. Rafael Leon [this message]
     [not found] <3go6arm3yvsi6iuungnfyd1o.1455824305674@email.android.com>
2016-02-18 21:18 ` RE : " Per Bothner
2016-02-18 21:22   ` mikel evins
  -- strict thread matches above, loose matches on Subject: below --
2016-02-18 16:18 Rafik
2016-02-18 18:57 ` Per Bothner
2016-02-18 19:39   ` mikel evins
2016-02-18 19:59   ` Dominique Boucher

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='CALPCXwiy=y6Ss1aZYHxTGr9QhkQ01GpH3byF+S=sF4r0dOx6Ew@mail.gmail.com' \
    --to=teflon@ucdavis.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).