= 27d567bc2d48d9f40e9ccc20ea370b15)
firstorderpredicate comments on Introducing Familiar, a quantified reasoning assistant (feedback sought!) - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (40)
I've just started playing with it now so these are just initial thoughts:
1) Command Line History would be really nice: Messing up a command (new-prd $var1 (fn ....) and having to retype from scratch is a pain. Although if you get a nice GUI it won't matter;
2) (Never mind; I can't reproduce it now) (After I did (change-time (days -1)); (data ..) nothing was returned from (entered) _ ;
3) Allowing data to be entered via a source file might be nice, but I suppose a script would work ok too. Perhaps I should write a Perl script to convert CSV into Familiar data?
For #1, just use readline/editlne. Don't try to implement your own.
Although personally I'd prefer a nice shell-scripting interface. (Note: I have not actually tried the program or checked if it has one.)
It can take command line arguments and therefore be put into a shell script, if that's what you mean. Here's an example:
It looks like getting editline to talk with my Clojure code would be somewhat non-trivial. Using the Clojure REPL is probably the better alternative for serious use until I get a GUI working.
Reading CSVs is now on the todo list.
Get rlwrap. Wrap the program in a script that runs 'rlwrap program'. All the benefits of readline with no code. You're welcome. ;-)
I'm hesitant to use software licensed under the GPL in my own program, as convenient as that sounds. I'd like to release it under a (even) less restrictive license.