From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org
Subject: Re: non-blocking keyboard input inside customized repl
Date: Wed, 29 Jan 2003 14:00:35 -0500 [thread overview]
Message-ID: <m33cnb7pcm.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <3E37325F.8060805@pscomp.com> (Peter Santoro's message of "Tue, 28 Jan 2003 20:46:07 -0500")
Peter Santoro <peter@pscomp.com> wrote:
> I would like to be able use non-blocking keyboard input in my
> customized REPL user interface. Is there a non-blocking read-char
> available in guile, so that the ENTER key doesn't always have to be
> pressed?
It sounds like what you want is raw terminal input. Non-blocking
input is different: it means that (read-char) will return immediately
(possibly throwing an exception) even if there is nothing to read yet.
For raw terminal input, you'd need tcsetattr, which doesn't seem to be
directly available in Guile. But maybe you can use the readline
module to do what you want.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-01-29 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 1:46 non-blocking keyboard input inside customized repl Peter Santoro
2003-01-29 19:00 ` Paul Jarc [this message]
2003-01-29 20:01 ` Peter Santoro
2003-01-30 2:24 ` Peter Santoro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33cnb7pcm.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).