From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
plan9port-dev@googlegroups.com
Subject: [9fans] acme Edit bug
Date: Tue, 2 Oct 2012 16:45:00 -0600 [thread overview]
Message-ID: <CAK4xykWkPuDxHLW1wFEC8mYKhaLTb8101Bx39g_02fSBi7GzPw@mail.gmail.com> (raw)
Edit (or something in its chain) appears to be broken on buffer
boundary in p9p and in plan9. To test:
$ perl -e '{print "A"x1023;}' > t.txt # for plan9 acme replace 1023 with 8191
$ echo [any multibyte utf rune, for example Щ] >> t.txt
$ acme t.txt
[ in acme, middle-swipe "Edit , |cat" without the quotes ]
this happens with any binary on the other side of the pipe (originally
discovered with gofmt). it happens on multiples of that size too,
1024, 2048, etc for p9p. it does not occur if just the pipe is used,
only when going through Edit.
next reply other threads:[~2012-10-02 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 22:45 andrey mirtchovski [this message]
2012-10-02 23:52 ` Rob Pike
2012-10-03 1:45 ` erik quanstrom
2012-10-03 2:31 ` andrey mirtchovski
2012-10-07 12:08 ` erik quanstrom
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=CAK4xykWkPuDxHLW1wFEC8mYKhaLTb8101Bx39g_02fSBi7GzPw@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@9fans.net \
--cc=plan9port-dev@googlegroups.com \
/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).