From: Byron Rakitzis <byron>
To: rc
Subject: another bug
Date: Mon, 26 Aug 1991 14:14:00 -0500 [thread overview]
Message-ID: <91Aug26.141405cdt.22537@archone.tamu.edu> (raw)
Sigh, it's always once you think you're done that some bugs show up. This one bites
me on the NeXT, but it's not a NeXT-specific bug by any means.
*** glom.c.orig Mon Aug 26 14:09:42 1991
--- glom.c Mon Aug 26 14:06:25 1991
***************
*** 468,470 ****
}
! return append(append(glom(words), last), glom(n->u[1].p));
case BACKQ:
--- 468,471 ----
}
! v = append(glom(words), last); /* force left to right evaluation */
! return append(v, glom(n->u[1].p));
case BACKQ:
reply other threads:[~1991-08-26 19:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=91Aug26.141405cdt.22537@archone.tamu.edu \
--to=rc@hawkwind.utcs.toronto.edu \
/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).