Re: Inconsistent Multiline String Handling in Lua REPL (Direct Input vs. History Recall)
mathieu stumpf-guntz <[email protected]> Thu, 30 Jul 2026 06:44:09 -0700 (PDT)
| Newsgroups | gmane.comp.lang.lua.general |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_103402_2043789276.1785419049637
Content-Type: multipart/alternative;
boundary="----=_Part_103403_65747935.1785419049637"
------=_Part_103403_65747935.1785419049637
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello Sainan, thanks for your quick reply.
Do you mean that the bug should rather be addressed to readline=20
maintainers? I have doubt about it, as in, even if the history facility use=
=20
libreadline, it looks to me more like the nub of the issue lies on the=20
direct input version which fails to interpret this multiline string.=20
I just tested in `irb` which for what I know also use readline, and=20
something like `%q{\ntest\n}` don=E2=80=99t cause any issue of interpretati=
on.
I did try to feed the LLM session I used to formulate the initial report=20
with additional contextual information, but nothing substantial came out of=
=20
it, just suggestion to test even more interpreters. I did with Python, but=
=20
didn=E2=80=99t went with the full extensive list it was proposing.
On Thursday, July 30, 2026 at 12:22:14=E2=80=AFPM UTC Sainan wrote:
> Maybe add some context to your AI agent that Lua uses libreadline for=20
> 'history recall'. :^)
>
> -- Sainan
>
--=20
You received this message because you are subscribed to the Google Groups "=
lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/lua-l/c82b1=
230-13b0-4ce8-8334-693263a63e60n%40googlegroups.com.
------=_Part_103403_65747935.1785419049637
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello Sainan, thanks for your quick reply.<br /><br />Do you mean that the =
bug should rather be addressed to readline maintainers? I have doubt about =
it, as in, even if the history facility use libreadline, it looks to me mor=
e like the nub of the issue lies on the direct input version which fails to=
interpret this multiline string.=C2=A0<br /><div><br /></div><div>I just t=
ested in `irb` which for what I know also use readline, and something like =
`%q{\ntest\n}` don=E2=80=99t cause any issue of interpretation.</div><div><=
br /></div><div>I did try to feed the=C2=A0LLM session I used to formulate =
the initial report with additional contextual information, but nothing subs=
tantial came out of it, just suggestion to test even more interpreters. I d=
id with Python, but didn=E2=80=99t went with the full extensive list it was=
proposing.</div><div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmai=
l_attr">On Thursday, July 30, 2026 at 12:22:14=E2=80=AFPM UTC Sainan wrote:=
<br/></div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; =
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Maybe add so=
me context to your AI agent that Lua uses libreadline for 'history reca=
ll'. :^)
<br>
<br>--=C2=A0Sainan
<br></blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;lua-l" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">lua-l+unsubsc=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
lua-l/c82b1230-13b0-4ce8-8334-693263a63e60n%40googlegroups.com?utm_medium=
=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/lua-l/c82b1=
230-13b0-4ce8-8334-693263a63e60n%40googlegroups.com</a>.<br />
------=_Part_103403_65747935.1785419049637--
------=_Part_103402_2043789276.1785419049637--