From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: acme buglet
Date: Sun, 29 Oct 1995 14:35:04 -0500 [thread overview]
Message-ID: <19951029193504.54bZDUJ79knyTzVgPHBYbKpLw_huRD7eD09Y9Ck9dHs@z> (raw)
Rob sent me a different patch for that bug. Here it is.
fix in util.l:
byte*
runetobyte(Rune *r, int n)
{
byte *s;
> if(n == 0)
> return nil;
s = malloc(n*UTFmax+1);
snprint(s, n*UTFmax+1, "%.*S", n, r);
return s;
}
next reply other threads:[~1995-10-29 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-29 19:35 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-09 12:38 Rob
1995-11-06 15:58 philw
1995-11-04 7:03 Sandy
1995-10-29 10:57 forsyth
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=19951029193504.54bZDUJ79knyTzVgPHBYbKpLw_huRD7eD09Y9Ck9dHs@z \
--to=9fans@9fans.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 NNTP newsgroup(s).