|
From: | Alexej Magura |
Subject: | Re: [Chicken-users] readline egg v2.0 feedback |
Date: | Sun, 25 Jan 2015 14:55:21 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
Forgot to send my reply to the
Chicken users mailing list too.
-------- Forwarded Message --------
Actually, after reviewing the source a little, it seems that #4 is already supported, although it probably isn't very well documented. This next release may need to be 3.0 instead of 2.5 if I decide to change the interface again--I hate doing that--which may prove necessary with some of the changes I already want to make to the history-list function for example: presently the underly C code uses a statically allocated buffer, which should be more than big enough for most cases, but I feel like it's awfully wasteful, and would be better served by dynamic memory allocation instead. I'm not familiar with the ,X interface idiom or whatever it is, but it sounds like something worth looking into and using. As for using sqlite, I'd be worried that it would add unnecessary overhead and read/write times to readline; moreover, readline provides no hooks, AFAICT; I'd have to write my own, and I don't see much to gain from using sqlite, sorry. I guess you were hoping that it would make it easier to implement more advanced history features like, super easy history grepping, running the last command over again, and that sort of thing, or something like that? One problem with Readline, which I admittedly have been avoiding, is that the documentation, is lacking, and, I think, this may contribute to the number/degree of users unaware or unsure of how to achieve a desired effect using Readline. On 01/25/2015 02:29 PM, Matt Welland
wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |