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.
*
On Tue, Jan 27, 2015 at 09:10:31AM +0100, Shawn Rutledge wrote:
On 26 January 2015 at 00:02, Matt Welland mattrwell...@gmail.com 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
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
On 26 January 2015 at 00:02, Matt Welland mattrwell...@gmail.com 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
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
-users] readline egg v2.0 feedback
Date: Sun, 25 Jan 2015 14:54:09 -0700
From: Alexej Magura agm2...@gmail.com mailto:agm2...@gmail.com
To: Matt Welland mattrwell...@gmail.com
mailto:mattrwell...@gmail.com
Actually, after reviewing the source a little, it seems
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
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
Message
From: Alexej Magura agm2...@gmail.com
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 hacks
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
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
Alexej Magura agm2...@gmail.com writes:
So apparently running csi with rlwrap was messing with the readline
support, lulz. Commenting out the following alias in my ~/.zshrc
fixed the problem: alias csi='rlwrap csi'
Oh, *duh*! Have fun with CHICKEN! Don't hesitate to ask for help again
next
Hi Alexej,
* Alexej Magura agm2...@gmail.com [141211 01:37]:
Is the readline egg's history feature broken? It only seems to work the
first time I start _csi_ up after creating a new history file. Here's the
code that I'm using:
(current-input-port (make-gnu-readline-port)
While perusing through readline's source code, I went ahead and added a
couple of functions that expose more of the API(? if that's the right term).
Specifically, they expose the where_history(), current_history(),
previous_history(), next_history(), history_search(), and
Alexej Magura agm2...@gmail.com writes:
While perusing through readline's source code, I went ahead and added
a couple of functions that expose more of the API(? if that's the
right term).
Specifically, they expose the where_history(), current_history(),
previous_history(), next_history(),
On 12/11/2014 01:43 AM, Christian Kellermann wrote:
So it looks to me, like it is working fine. Does this help?
Yeah, I loaded up my shell without my rcfile and the problem went away,
so something in my .zshrc/.zshenv is causing the problem.
Note that you indeed need to create the file
On 12/11/2014 02:31 AM, Alexej Magura wrote:
Yeah, I loaded up my shell without my rcfile and the problem went
away, so something in my .zshrc/.zshenv is causing the problem.
So apparently running csi with rlwrap was messing with the readline
support, lulz. Commenting out the following
Is the readline egg's history feature broken? It only seems to work the
first time I start _csi_ up after creating a new history file. Here's
the code that I'm using:
(current-input-port (make-gnu-readline-port)
(gnu-history-install-file-manager
(string-append (or (get-environment-variable
On Wed, Jan 26, 2011 at 18:33, Jim Ursetto zbignie...@gmail.com wrote:
The readline egg build system (which determines which libraries to use
for readline) has been rewritten around 9,996 times and I think a
recent change broke it, deleting the code which honored CSC_OPTIONS.
I have checked
Jim,
I'll try to get to this in a bit... a little busy right now.
-Dave
On Wed, Jan 26, 2011 at 7:33 PM, Jim Ursetto zbignie...@gmail.com wrote:
David,
The readline egg build system (which determines which libraries to use
for readline) has been rewritten around 9,996 times and I think a
Using Macports, I had to do the following in order to get the readline
egg to install:
$ sudo ln -s /opt/local/lib/libreadline.dylib /usr/local/lib/
$ sudo ln -s /opt/local/include/readline/ /usr/local/include/readline
The procedure on the wiki didn't work.
* David Dreisigmeyer dwdreisigme...@gmail.com [110126 12:03]:
Using Macports, I had to do the following in order to get the readline
egg to install:
$ sudo ln -s /opt/local/lib/libreadline.dylib /usr/local/lib/
$ sudo ln -s /opt/local/include/readline/ /usr/local/include/readline
The
This version of Chicken is not from Macports, but readline is. I had
tried various CSC_OPTIONS in my .profile, e.g.:
export CSC_OPTIONS=-L/opt/local/lib -I/opt/local/include
export CSC_OPTIONS=-L/opt/local/lib -I/opt/local/include/readline
and also using the -rpath flag after your suggestion.
On Wed, Jan 26, 2011 at 06:02:12AM -0500, David Dreisigmeyer wrote:
Using Macports, I had to do the following in order to get the readline
egg to install:
$ sudo ln -s /opt/local/lib/libreadline.dylib /usr/local/lib/
$ sudo ln -s /opt/local/include/readline/ /usr/local/include/readline
On Wed, Jan 26, 2011 at 8:59 AM, David Dreisigmeyer
dwdreisigme...@gmail.com wrote:
This version of Chicken is not from Macports, but readline is. I had
tried various CSC_OPTIONS in my .profile, e.g.:
export CSC_OPTIONS=-L/opt/local/lib -I/opt/local/include
export
That doesn't work either. If you made a symbolic link with homebrew
is that the same as doing:
$ sudo ln -s /opt/local/lib/libreadline.dylib /usr/local/lib/
$ sudo ln -s /opt/local/include/readline/ /usr/local/include/readline
On Wed, Jan 26, 2011 at 10:01 AM, Stephen Eilert spedr...@gmail.com
David,
The readline egg build system (which determines which libraries to use
for readline) has been rewritten around 9,996 times and I think a
recent change broke it, deleting the code which honored CSC_OPTIONS.
I have checked in a fix (again...) to trunk. If you have access, can
you try it
2009/12/25 Derrell Piper d...@electric-loft.org:
Fortunately, the readline in MacPorts works with the readline egg; it's
just a matter of getting chicken-install to compile and link against
/opt/local. To do that, I hacked readline.setup.
Actually all you should have to do is set
The readline egg does not install on OS X 10.6 (Snow Leopard) due to a
mismatch between the readline library that ships with the base OS X
system (under /usr) and what the egg's expecting. I suspect, but have
not verified, that OS X is shipping a much older version of readline.
Fortunately, the
For saved history, create an empty .csi.history. It won't create the
file if it doesn't exist. I don't know if that behavior is intentional.
I certainly found it surprising.
On Fri, 2009-12-25 at 13:02 -0500, Derrell Piper wrote:
The readline egg does not install on OS X 10.6 (Snow Leopard)
On Sat, Sep 12, 2009 at 10:39 PM, David N Murray dmur...@jsbsystems.com wrote:
d...@kili:~/tr/scheme$ cat ~/.csirc
(require 'readline)
(current-input-port (make-gnu-readline-port))
(gnu-history-install-file-manager (string-append (or (getenv HOME) .)
/.csi.history))
Hi,
Just change require
On Sep 13, Jim Ursetto scribed:
On Sat, Sep 12, 2009 at 10:39 PM, David N Murray dmur...@jsbsystems.com
wrote:
d...@kili:~/tr/scheme$ cat ~/.csirc
(require 'readline)
(current-input-port (make-gnu-readline-port))
(gnu-history-install-file-manager (string-append (or (getenv HOME) .)
On Sun, Sep 13, 2009 at 11:28 AM, David N Murray dmur...@jsbsystems.com wrote:
Thanks Jim. That fixed it. I tried to update the Wiki
(http://chicken.wiki.br/readline#Examples) since that's where I got the
code from, but it tells me the page doesn't exist.
Thanks. The wiki is confused. Looks
Sometimes I think it's just me:
d...@kili:~/tr/scheme$ cat ~/.csirc
(require 'readline)
(current-input-port (make-gnu-readline-port))
(gnu-history-install-file-manager (string-append (or (getenv HOME) .)
/.csi.history))
d...@kili:~/tr/scheme$ csi
CHICKEN
(c)2008-2009 The Chicken Team
On Sun, Aug 9, 2009 at 10:19 PM, Sam Varnersnick-a-...@comcast.net wrote:
Installing the readline egg with chicken-install fails:
My guess is it is probably a special case of
http://www.irp.oist.jp/trac/chicken/ticket/69, in which
chicken-install does not stop on error. Just so you know we are
On Thu, Nov 13, 2008 at 5:52 AM, Mark Fredrickson
[EMAIL PROTECTED] wrote:
Hello,
Does the readline egg have an active maintainer?
I'm trying to add file globbing to the completions, and I have a very
basic patch. I'm thinking of creating a little completion callback API
and I'd like to
Do I need to updated repo perms? I tried to check into the readline
directory and got denied (probably a good thing). My username is
mfredrickson
Thanks in advance!
-Mark
On Thu, Nov 13, 2008 at 6:28 AM, felix winkelmann [EMAIL PROTECTED] wrote:
On Thu, Nov 13, 2008 at 5:52 AM, Mark Fredrickson
Hi Mark
On Thu, 13 Nov 2008 15:43:03 -0600 Mark Fredrickson [EMAIL PROTECTED] wrote:
Do I need to updated repo perms? I tried to check into the readline
directory and got denied (probably a good thing). My username is
mfredrickson
I've added rw permissions to the readline repo for you.
Best
Hello,
Does the readline egg have an active maintainer?
I'm trying to add file globbing to the completions, and I have a very
basic patch. I'm thinking of creating a little completion callback API
and I'd like to coordinate with the maintainer.
Cheers,
-Mark
On Wed, Mar 5, 2008 at 11:50 PM, Shawn Rutledge
[EMAIL PROTECTED] wrote:
So they're using Unix sockets. It's already non-blocking, so F_SETFL
doesn't change the behavior.
But I guess I'm being stupid... readline (or the terminal? as you say)
is blocking, not dbus. But it's good to know
um... repl will always block threads. as the docs state, read is blocking
except for certain network ports.
-elf
On Tue, 4 Mar 2008, Shawn Rutledge wrote:
If you do
(use readline)
(current-input-port (make-gnu-readline-port csi ))
(thread-start! (lambda () (let loop () (printf loop~%)
On Tue, 4 Mar 2008, Shawn Rutledge wrote:
On Tue, Mar 4, 2008 at 12:05 PM, Elf [EMAIL PROTECTED] wrote:
um... repl will always block threads. as the docs state, read is blocking
except for certain network ports.
If you try the example threaded loop without readline, it works.
and then
Unit SRFI-18:
Blocking I/O will block all threads, except for some socket operations (see the
section about the tcp unit). An exception is the read-eval-print loop on UNIX
platforms: waiting for input will not block other threads, provided the current
input port reads input from a console.
On
(unless (eq? (build-platform) 'msvc)
(set! ##sys#read-prompt-hook
(let ([old ##sys#read-prompt-hook]
[thread-yield! thread-yield!] )
(lambda ()
(when (or (##sys#fudge 12) (##sys#tty-port? ##sys#standard-input))
(old)
(##sys#thread-block-for-i/o!
On Tue, Mar 4, 2008 at 12:36 PM, Elf [EMAIL PROTECTED] wrote:
try putting a (thread-yield!) and it works in readline.
Yeah you're right.
csi (use srfi-18)
; loading library srfi-18 ...
csi (thread-start! (lambda () (let loop () (printf loop~%)
(thread-yield!) (loop
#thread: thread0
csi
sigh.
thread-quantum-set! is your friend. ill see about trying to get readline
to do what you want, but it will lose some functionality, probably.
-elf
On Tue, 4 Mar 2008, Shawn Rutledge wrote:
On Tue, Mar 4, 2008 at 12:36 PM, Elf [EMAIL PROTECTED] wrote:
try putting a (thread-yield!)
Shawn:
Did you try using rlwrap? It works fine here.
$ rlwrap csi
#;1 (use srfi-18)
#;2 (thread-start! (lambda () (let loop () (printf loop~%) (thread-sleep! 1)
(loop
#thread: thread0
#;3 loop
loop
loop
loop
On 3/4/08, Shawn Rutledge [EMAIL PROTECTED] wrote:
If you do
(use readline)
On Tue, Mar 4, 2008 at 2:45 PM, Jim Ursetto [EMAIL PROTECTED] wrote:
Did you try using rlwrap? It works fine here.
$ rlwrap csi
#;1 (use srfi-18)
#;2 (thread-start! (lambda () (let loop () (printf loop~%) (thread-sleep!
1)
(loop
#thread: thread0
#;3 loop
loop
loop
loop
On Tue, Mar 4, 2008 at 3:47 PM, Elf [EMAIL PROTECTED] wrote:
there is a way to do this. its just very painful. im working on a
readline-ng
egg with the changes, as the existing readline wont work.
OK. I hope I'm not causing too much pain.
___
On Tue, Mar 4, 2008 at 5:50 PM, Shawn Rutledge
[EMAIL PROTECTED] wrote:
On Tue, Mar 4, 2008 at 3:47 PM, Elf [EMAIL PROTECTED] wrote:
there is a way to do this. its just very painful. im working on a
readline-ng
egg with the changes, as the existing readline wont work.
OK. I hope
felix fixed it already, it appears. :)
-elf
On Mon, 11 Feb 2008, Elf wrote:
my fault. it should include the posix egg. ill fix it straightaway. i
added
signal handling to readline so that control-c and control-d were handled
properly.
-elf
On Sat, 9 Feb 2008, Andre Kuehne wrote:
my fault. it should include the posix egg. ill fix it straightaway. i added
signal handling to readline so that control-c and control-d were handled
properly.
-elf
On Sat, 9 Feb 2008, Andre Kuehne wrote:
hey guys
can someone help me with this readline problem?
csi -n
CHICKEN
hey guys
can someone help me with this readline problem?
csi -n
CHICKEN
Version 3.0.0 - linux-unix-gnu-x86 [ manyargs dload ptables applyhook ]
(c)2000-2008 Felix L. Winkelmanncompiled 2008-02-09 on disko (Linux)
#;1 (require 'readline)
; loading
From: Andre Kuehne [EMAIL PROTECTED]
Subject: [Chicken-users] readline Error: unbound variable: set-signal-handler!
Date: Sat, 09 Feb 2008 21:46:42 +0100
hey guys
can someone help me with this readline problem?
csi -n
CHICKEN
Version 3.0.0 - linux-unix-gnu-x86 [ manyargs dload
: chicken-users@nongnu.org
Sent: Wednesday, October 25, 2006 9:12:31 AM
Subject: Re: [Chicken-users] readline not savinf one-char commands to history
On 10/25/06, Dan [EMAIL PROTECTED] wrote:
That's right, the latest readline egg doesn't save things like x, f, or + (on
a line by themselves
On 10/25/06, Dan [EMAIL PROTECTED] wrote:
That's right, the latest readline egg doesn't save things like x, f, or + (on a
line by themselves) to the history. Once you type at least two chars the
command is safe though. Is this a feature or (more likely) a bug?
Works fine on my system
-users@nongnu.org
Sent: Wednesday, October 25, 2006 9:12:31 AM
Subject: Re: [Chicken-users] readline not savinf one-char commands to history
On 10/25/06, Dan [EMAIL PROTECTED] wrote:
That's right, the latest readline egg doesn't save things like x, f, or + (on
a line by themselves) to the history
Hi Dan,On 10/24/06, Dan [EMAIL PROTECTED]
wrote:
That's right, the latest readline egg doesn't save things like x, f, or + (on a line by themselves) to the history. Once you type at least two chars the command is safe though. Is this a feature or (more likely) a bug?
I can't reproduce this
Thanks, Toby. Egg is updated.
cheers,
felix
On 10/22/06, Toby Butzon [EMAIL PROTECTED] wrote:
Hi,
On 10/20/06, Dan [EMAIL PROTECTED] wrote:
Another useful thing would be not to save duplicate lines, but it
requires marginally more work than just writing this message.
I think this
On 10/20/06, Dan [EMAIL PROTECTED] wrote:
Someone please patch the readline egg:
335c335
if (gnu_readline_buf != NULL)
---
if (gnu_readline_buf != NULL *gnu_readline_buf != '\0')
Done. Thanks.
cheers,
felix
--
http://galinha.ucpel.tche.br:8081/blog/blog.ssp
Someone please patch the readline egg:
335c335
if (gnu_readline_buf != NULL)
---
if (gnu_readline_buf != NULL *gnu_readline_buf != '\0')
to avoid blank lines being saved to history. Is anyone using the readline egg?
Another useful thing would be not to save duplicate lines, but
Hello Dan,
On Thu, 19 Oct 2006 23:55:22 -0700 (PDT) Dan [EMAIL PROTECTED] wrote:
Is anyone using the readline egg?
I use it quite frequently when I want to quickly test something
simple.
Another useful thing would be not to save duplicate lines, but it
requires marginally more work than
Another useful thing would be not to save duplicate lines, but it
requires marginally more work than just writing this message.
I think this could be a configuration option like, if I remember
correctly, it is in shells like GNU Bash.
Right, but
(i) this feature needs to be programmed into
67 matches
Mail list logo
