From owner-freebsd-hackers  Tue Sep 19 18:50:19 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA11313
          for hackers-outgoing; Tue, 19 Sep 1995 18:50:19 -0700
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA11308
          for <hackers@FreeBSD.ORG>; Tue, 19 Sep 1995 18:50:16 -0700
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA22543
  (5.67a/IDA-1.5); Tue, 19 Sep 1995 20:33:44 -0500
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id UAA13422; Tue, 19 Sep 1995 20:23:33 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199509200123.UAA13422@bonkers.taronga.com>
Subject: Re: Policy on printf format specifiers?
To: terry@lambert.org (Terry Lambert)
Date: Tue, 19 Sep 1995 20:23:32 -0500 (CDT)
Cc: peter@taronga.com, hackers@FreeBSD.ORG
In-Reply-To: <199509191904.MAA10411@phaeton.artisoft.com> from "Terry Lambert" at Sep 19, 95 12:04:29 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 535       
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> Because you have to redo the string before you redraw or allow the character
> entry in the "fixed length field" and interactive response will suffer
> because of that.

It has been my experience that the minimal resources required for X are
such that even if every character required a callback the slowest component
in the system is still the nut holding the keyboard.

This sort of argument made sense on an 11/70 where you avoided using CBREAK
mode because of the overhead, but nobody's running FreeBSD on an 8086-class
machine.