Re: [racket-dev] Line editing in the default REPL

2014-11-24 Thread Sam Tobin-Hochstadt
My understanding of the licensing issues is that if the code works with both "libeditline" and "libreadline" then it isn't a derived work of readline, and therefore could be licensed under the LGPL, like the rest of Racket. Furthermore, turning use of "libeditline" on by default wouldn't be linking

[racket-dev] Line editing in the default REPL

2014-11-24 Thread Leif Andersen
Hello, When a user first starts the racket repl, it doesn't do line editing due to licensing issues. For example, it would be nice if the default editor would give the previous line if you hit up arrow, rather than writing "^[[A". I have now pointed out xrepl to several users, and every time they

Re: [racket-dev] DrRacket PF1 Search Bug?

2014-11-24 Thread Robby Findler
I've pushed a fix for the mac os x problem using materialize-user-docs because it seems to me to reduce rather than enlarge the number of different configurations are users are in. It may not actually turn out to be the conservative change and we can always revisit it when we have more concrete dat

Re: [racket-dev] DrRacket PF1 Search Bug?

2014-11-24 Thread Eli Barzilay
On Sun, Nov 23, 2014 at 9:01 AM, Matthew Flatt wrote: > At Sat, 22 Nov 2014 14:16:32 -0500, Eli Barzilay wrote: >> >> Oh, *that*'s the other solution? That sounds pretty bad not only >> because it complicates file installation which is already very >> complex, but also because it's a significant