From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: bug#33403: Data length limit in Guile/Geiser/Scheme evaluation Date: Sat, 17 Nov 2018 02:31:17 -0500 Message-ID: <87tvkgw467.fsf@netris.org> References: <87sh021kw2.fsf@ossau.homelinux.net> <878t1ugyf9.fsf@nicolasgoaziou.fr> <87h8gi1g5g.fsf@ossau.homelinux.net> <871s7mz357.fsf@imladris> <87bm6q1c33.fsf@ossau.homelinux.net> <87o9aq55tl.fsf@ossau.homelinux.net> <87d0r5349t.fsf@netris.org> <87y39t1olc.fsf@netris.org> <878t1t1ety.fsf@ossau.homelinux.net> <875zwx1dcn.fsf@ossau.homelinux.net> <87va4wwra7.fsf@imladris> <87zhu8w55u.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87zhu8w55u.fsf-StlzRsPvAncdnm+yROfE0A@public.gmane.org> (Mark H. Weaver's message of "Sat, 17 Nov 2018 02:09:54 -0500") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: geiser-users-bounces+glsg-geiser-users=m.gmane.org-qX2TKyscuCcdnm+yROfE0A@public.gmane.org Sender: "geiser-users" To: "Jose A. Ortega Ruiz" Cc: geiser-users-qX2TKyscuCcdnm+yROfE0A@public.gmane.org, emacs-orgmode-mXXj517/zsQ@public.gmane.org, 33403-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org List-Id: emacs-orgmode.gnu.org A few more notes: I wrote earlier: > However, before doing this, some warnings are in order: > > When in noncanonical mode, the normal processing of ERASE (usually DEL > or Ctrl-H) and KILL (usually Ctrl-U) characters are disabled, Also the handling of Ctrl-D appears to be disabled in noncanonical mode on my system, although this wasn't clear to me from the docs. > At least in the case of the Guile REPL, one notable side effect of > running in noncanonical mode is that when a list is entered at the REPL, > the 'read' returns as soon as the final close parenthesis is entered. > Nothing after that is read, not even the usual newline. There's an additional wrinkle here: after 'read' returns, Guile tries to read optional whitespace followed by a newline, but only if it's immediately available. See 'flush-to-newline' at the end of module/system/repl/repl.scm in Guile. So, unfortunately there's a race condition here, but typically if you send the newline immediately after the final character of input, it is likely that the newline will be consumed by the REPL reader and not by the code that is subsequently run. Finally, I should note that I consider this race condition suboptimal, and will likely change how Guile behaves in the future, so please don't rely on the behavior I have described above. I will likely change Guile's REPL reader to wait for the final newline in all cases. Mark