From: Neil Jerram <neil@ossau.homelinux.net>
To: Mark H Weaver <mhw@netris.org>
Cc: geiser-users@nongnu.org, 33403@debbugs.gnu.org
Subject: bug#33403: [Geiser-users] Data length limit in Guile/Geiser/Scheme evaluation
Date: Fri, 16 Nov 2018 10:44:57 +0000 [thread overview]
Message-ID: <878t1t1ety.fsf@ossau.homelinux.net> (raw)
In-Reply-To: <87y39t1olc.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> This is a documented limitation in Linux's terminal handling when in
> canonical mode. See the termios(3) man page, which includes this text:
>
> Canonical and noncanonical mode
>
> The setting of the ICANON canon flag in c_lflag determines
> whether the terminal is operating in canonical mode (ICANON set)
> or noncanonical mode (ICANON unset). By default, ICANON is set.
[...]
> * The maximum line length is 4096 chars (including the
> terminating newline character); lines longer than 4096 chars
> are truncated. After 4095 characters, input processing (e.g.,
> ISIG and ECHO* processing) continues, but any input data after
> 4095 characters up to (but not including) any terminating
> newline is discarded. This ensures that the terminal can
> always receive more input until at least one line can be read.
>
> Note that last item above.
Awesome; thank you Mark.
So possibly this limit can be removed, in my Org/Geiser context, by
evaluating (system* "stty" "-icanon") when initializing the Geiser-Guile
connection. I'll try that. Will the terminal that that 'stty' sees be
the same as Guile's stdin?
Jao, if that works, I wonder if it should be the default for Geiser? It
appears to me that Geiser shouldn't ever need the features of canonical
mode. Is that right?
Anyway, I'll see first if the stty call is effective.
Neil
next prev parent reply other threads:[~2018-11-16 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sh021kw2.fsf@ossau.homelinux.net>
[not found] ` <878t1ugyf9.fsf@nicolasgoaziou.fr>
[not found] ` <87h8gi1g5g.fsf@ossau.homelinux.net>
[not found] ` <871s7mz357.fsf@imladris>
[not found] ` <87bm6q1c33.fsf@ossau.homelinux.net>
[not found] ` <87bm6q1c33.fsf-mq78CtbEgnGjF4gvJNWmbtHuzzzSOjJt@public.gmane.org>
2018-11-15 22:33 ` Data length limit in Guile/Geiser/Scheme evaluation Neil Jerram
2018-11-16 6:49 ` bug#33403: [Geiser-users] " Mark H Weaver
2018-11-16 7:13 ` Mark H Weaver
2018-11-16 10:44 ` Neil Jerram [this message]
2018-11-16 11:16 ` Neil Jerram
2018-11-16 22:40 ` bug#33403: [Geiser-users] bug#33403: " Jose A. Ortega Ruiz
[not found] ` <875zwx1dcn.fsf@ossau.homelinux.net>
2018-11-16 23:12 ` Jose A. Ortega Ruiz
[not found] ` <87va4wwra7.fsf@imladris>
2018-11-17 7:09 ` Mark H Weaver
[not found] ` <87zhu8w55u.fsf@netris.org>
2018-11-17 7:31 ` Mark H Weaver
2018-11-17 14:59 ` Jose A. Ortega Ruiz
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=878t1t1ety.fsf@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=33403@debbugs.gnu.org \
--cc=geiser-users@nongnu.org \
--cc=mhw@netris.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).