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
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
On Sun, Jan 25, 2015 at 2:55 PM, Alexej Magura agm2...@gmail.com 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
Magura
On 2015-01-25 23:21, Alexej Magura wrote:
If I have a function that returns a malloc'd pointer, or that needs to
have a buffer malloc'd, is it more idiomatic to (1) malloc and free in
the caller function (which is C's idiom, IIRC), or (2) malloc it in C
and then just return the pointer for
I found the egg manual to cock a bit unhelpful for what it states about the
.setup-file. I'm working on a library where my .setup-file contains two
compile and an install-extension expressions, but the manual now tells me
I have to use setup-shared-extension-module and run-cock. Do I put them
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 agm2...@gmail.com
To: Matt Welland mattrwell...@gmail.com
If I have a function that returns a malloc'd pointer, or that needs to
have a buffer malloc'd, is it more idiomatic to (1) malloc and free in
the caller function (which is C's idiom, IIRC), or (2) malloc it in C
and then just return the pointer for free'ing by Chicken once the caller
function
lulz, you're the first person to reply to this thread. :)
I'll see about implementing a reasonable solution.
On 01/25/2015 08:33 AM, m...@kiatoa.com wrote:
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
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
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 and
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
11 matches
Mail list logo
