From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: [9front] aux/listen1 oddity...
Date: Mon, 27 Sep 2021 13:56:03 -0700 [thread overview]
Message-ID: <CAHwi9bymapOjWB=XjXyMJ5pEGs-HXbT+3ps5+RM6Nk7adgU1Xg@mail.gmail.com> (raw)
hey, no one else seemed to take much notice of my mention of an oddity
in aux/listen1 besides Ben, but I believe I figured out what was
happening and wanted to mention this...
when an aux/listen1 handler is changed between connections, listen1
can reply with undefined behavior... the script can end up running
"commands" at weird places starting in weird locations in the text...
I believe that's all that was happening that I mentioned, if anyone
else had even noticed...
next reply other threads:[~2021-09-27 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 20:56 Eli Cohen [this message]
2021-09-27 21:33 ` Stanley Lieber
2021-09-29 1:25 ` Eli Cohen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHwi9bymapOjWB=XjXyMJ5pEGs-HXbT+3ps5+RM6Nk7adgU1Xg@mail.gmail.com' \
--to=echoline@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).