unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Neil Jerram <neil@ossau.homelinux.net>
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 01:49:39 -0500	[thread overview]
Message-ID: <87d0r5349t.fsf@netris.org> (raw)
In-Reply-To: <87o9aq55tl.fsf@ossau.homelinux.net> (Neil Jerram's message of "Thu, 15 Nov 2018 22:33:42 +0000")

Hi Neil,

Neil Jerram <neil@ossau.homelinux.net> writes:

> Hi, this is a report for Guile 2.2:
>
>     neil@henry:~$ guile --version
>     guile (GNU Guile) 2.2.3
>     Packaged by Debian (2.2.3-deb+1-3ubuntu0.1)
>
> I'm seeing something that looks like a line or sexp length limit when
> reading from a terminal.  Sample inputs are in the attached file.
>
>
>
> If I run guile in a terminal (GNOME Terminal 3.28.2), select the first
> block from the file, and use my middle mouse button to paste it into the
> guile prompt, I get the expected answer:
>
>     $4 = 139
>     scheme@(guile-user)> 
>
> If I do the same with the second block, I get no response, and it
> appears that Guile has hung in some way.  I have to type C-c to get a
> new prompt:
>
>     ^C^CWhile reading expression:
>     User interrupt
>     scheme@(guile-user)> 
>
> The max line length for the first block is 4087.  For the second it's
> 4113.  Could there be a 4K buffer or limit involved somewhere?

Indeed, I can reproduce the same issue when pasting into an Emacs shell
buffer.  I've verified that Guile only receives the first 4095 bytes of
the first line.  The following characters from the end of the first line
are lost:

A AAAA" "Aub")))))

So the second and third lines of the input become part of the string
literal whose closing quote was lost, and Guile's reader continues to
wait for a closing quote.

If, after pasting this, you type another close quote, 5 close parens,
and then repaste the last two lines, it will print the garbled input and
return to a prompt.

Anyway, to make a long story short, after some debugging, I found that
precisely the same truncation of the first line happens when using 'cat'
from GNU coreutils.  Simply type 'cat' and paste the same text, and
you'll see that in the output, only the first 4095 bytes of the first
line were retained.

So, I'm not sure where the problem is, but it's not a problem in Guile.

     Regards,
       Mark





  reply	other threads:[~2018-11-16  6:49 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             ` Mark H Weaver [this message]
2018-11-16  7:13               ` bug#33403: [Geiser-users] " Mark H Weaver
2018-11-16 10:44                 ` Neil Jerram
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=87d0r5349t.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=33403@debbugs.gnu.org \
    --cc=geiser-users@nongnu.org \
    --cc=neil@ossau.homelinux.net \
    /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).