Re: [Chicken-users] replacement for rlwrap on MS Windows, MinGW

[Jim Ursetto]

If you're going to go the Emacs route, it's probably even better to use run-scheme from cmuscheme.el, as you may then evaluate Scheme expressions from any buffer in the interpreter of your choice.  I'm pretty sure this works on Windows.  Well, I hope it does.

On Jul 25, 2013, at 10:37 PM, Michael Maul <address@hidden> wrote:

On the emacs front. You don't have to even set up slime, if all you want is csi w/command history.

Just start Emacs, Alt-X shell , type csi and your good to go. Ctrl-Up Arrow to access history.

Setting up Slime is worth the effort, but not necessary.

On Fri, Jul 26, 2013 at 3:04 AM, Claude Marinier <address@hidden> wrote:

Using csi with parley works well on Linux (Debian Wheezy).

On MS Windows, Cygwin and MinGW are stepping on each other's toes. I have to clean-up the mess.

Time to re-visit the choice between Cygwin and MinGW. The concern some people have about the Cygwin DLL and the GPL does not affect me for now. If I publish, I will likely use a three clause BSD license which is compatible, right? The obvious technical reason to choose one over the other is POSIX support. Are there others?

Hum ... maybe I should stick with Linux. :-)

On Thu, Jul 25, 2013 at 7:34 PM, Claude Marinier <address@hidden> wrote:

On Thu, 25 Jul 2013, Christian Kellermann wrote:

* Christian Kellermann <address@hidden> [130725 10:48]:

* Christian Kellermann <address@hidden> [130725 10:29]:

* Peter Bex <address@hidden> [130725 08:59]:

On Wed, Jul 24, 2013 at 06:57:56PM -0400, Claude Marinier wrote:

Just to make sure we are talking about the same thing. The context is
using the REPL on MS Windows. I prefer to use MinGW instead of Cygwin.

Are you saying that csi can be built to use parley to provide better
history and line editing?

That's not neccessary; you can simply build parley and load it into
your csirc startup file and it will take care of the rest.  See the
parley manual page for more info on how to do that.

Can this also be done on MS Windows?

I don't see why it shouldn't work, but it probably hasn't been tested yet.
Just give it a go and see how far you get.

I see that stty needs some patching, I will see what I can do. Alex,
have you got a stty version that's known to work on windows?

Ok, as a quick fix you need to chicken-install -r stty and comment
out three occasions of ECHOPRT. At least parley should work then
as this flag isn't used.

Please tell me how far you get.

I retrieved the stty code, commented out the lines which reference ECHOPRT, and tried to build & install stty. I am not sure how to proceed from there. I expect chicken-install has a switch to build and install from the current directory.

Trying 'chicken-install stty' produced much activity as dependencied were handles, then it died with the following error.

    stty.c:13:21: fatal error: termios.h: No such file or directory
    compilation terminated.

--
Claude Marinier

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users