Re: [Chicken-users] readline egg v2.0 feedback

2015-02-02 Thread Alexej Magura
Just pushed 3.0 out the door. Please let me know if it isn't regnoized as the latest version and I'll bump it up to 3.1. And let me know if yall come across any bugs. It introduces the following toplevel commands: * ,rl-!! o Similar to Bash's /!!/, it evaluates the previous line. * ,r

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-27 Thread Evan Hanson
Hi Alexej, My tuppence: On 2015-01-27 4:01, Alexej Magura wrote: > I don't think I'll use the toplevel-command stuff after all: I can't promise > that the toplevel symbols readline exports won't get overwritten, and I'm > not entirely sure readline has any business providing private toplevel > s

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-27 Thread Alexej Magura
I don't think I'll use the toplevel-command stuff after all: I can't promise that the toplevel symbols readline exports won't get overwritten, and I'm not entirely sure readline has any business providing private toplevel symbols that are only applicable to it. It might confuse less-experienced

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-27 Thread Peter Bex
On Tue, Jan 27, 2015 at 09:10:31AM +0100, Shawn Rutledge wrote: > On 26 January 2015 at 00:02, Matt Welland wrote: > > From http://wiki.call-cc.org/man/4/Using%20the%20interpreter the > ,commands are called "toplevel commands" and you can define them with: > > > > (toplevel-command SYMBOL PROC [HE

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-27 Thread Shawn Rutledge
On 26 January 2015 at 00:02, Matt Welland wrote: > From http://wiki.call-cc.org/man/4/Using%20the%20interpreter the ,commands are called "toplevel commands" and you can define them with: > > (toplevel-command SYMBOL PROC [HELPSTRING]) Where does this tradition come from? Is it related somehow to

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-26 Thread Alexej Magura
promise that it'll use sqlite, though. On 01/25/2015 04:02 PM, Matt Welland wrote: On Sun, Jan 25, 2015 at 2:55 PM, Alexej Magura <mailto:agm2...@gmail.com>> wrote: Forgot to send my reply to the Chicken users mailing list too. Forwarded Message ----

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread Matt Welland
On Sun, Jan 25, 2015 at 2:55 PM, Alexej Magura wrote: > > Forgot to send my reply to the Chicken users mailing list too. > > Forwarded Message Subject: Re: [Chicken-users] > readline egg v2.0 feedback Date: Sun, 25 Jan 2015 14:54:09 -0700 From: > Alexej &g

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread Alexej Magura
Forgot to send my reply to the Chicken users mailing list too. Forwarded Message Subject:Re: [Chicken-users] readline egg v2.0 feedback Date: Sun, 25 Jan 2015 14:54:09 -0700 From: Alexej Magura To: Matt Welland Actually, after reviewing the source a little

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread Alexej Magura
A paranoid function seems unnecessarily complicated to me. I think it'd be better to provide users with simple tools with which they can build bigger/better tools that suit their needs better than any megalathon-tool that I can provide. On 01/25/2015 01:48 PM, Matt Welland wrote: I'm not sure

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread Alexej Magura
I think that a reasonable solution would be to (1) create the history file if it does not already exist, (2) allow users to explicitly disable/enable history keeping at any time, (3) simplify history file installation to include only about a line of code, (4) add an option to either wipe the hi

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread Matt Welland
I'm not sure I understand the concern. The user had to take explicit action to enable command logging in their .csirc, something like the following: (gnu-history-install-file-manager (string-append (or (getenv "HOME") ".") "/.csi.history" Presumably if they did the research to find this an

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread Alexej Magura
Original Message From: Alexej Magura Sent: Monday, December 15, 2014 04:00 AM To: chicken-users@nongnu.org Subject: [Chicken-users] readline egg v2.0 feedback Hi, so as the new maintainer for the readline egg I wanted to reach out to the community and see if anybody had any h

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread John Cowan
m...@kiatoa.com scripsit: > As a daily user of csi with readline I look forward to using your > enhancements. If it makes sense to do I would like to see the > behavior change for a new install, currently the user has to touch > the ~/.csi-history (?) file before history will be kept. I'd like it

Re: [Chicken-users] readline egg v2.0 feedback

2015-01-25 Thread m...@kiatoa.com
Hi Alexej, As a daily user of csi with readline I look forward to using your enhancements. If it makes sense to do I would like to see the behavior change for a new install, currently the user has to touch the ~/.csi-history (?) file before history will be kept. I'd like it if that became unne

[Chicken-users] readline egg v2.0 feedback

2014-12-15 Thread Alexej Magura
Hi, so as the new maintainer for the readline egg I wanted to reach out to the community and see if anybody had any hacks that they'd like to see included in the egg or if any old maintainers have uncommitted code? Also if you'd like to see a feature get implemented/added to the egg, please le