From owner-freebsd-hackers Thu Jan 12 16:38:27 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA14963 for hackers-outgoing; Thu, 12 Jan 1995 16:38:27 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id QAA14957 for ; Thu, 12 Jan 1995 16:38:22 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id LAA17920; Fri, 13 Jan 1995 11:37:42 +1100 Date: Fri, 13 Jan 1995 11:37:42 +1100 From: Bruce Evans Message-Id: <199501130037.LAA17920@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.org, wpaul@skynet.ctr.columbia.edu Subject: Re: Small syscons change Sender: hackers-owner@FreeBSD.org Precedence: bulk >This patch backs out the 'cursor wraps at wrong place' fix I had bundled >in with my NOBLINK_CURSOR mods. Apparently this change breaks elvis and >bash (although bash's problems appear to be bash's own fault -- this is >version 1.14.2 we're talking about here). The NOBLINK_CURSOR mods don't >seem to be a problem. (They better not be. :) The change only broke elvis. bash-1.14.2's special handling for the last column is broken. bash-1.14.3 works OK. elvis thinks that the "am" termcap capability means that the cursor automatically wraps to column 0 of the next line when a character is printed in the last column. Is this what "am" means? There is often no problem, but when elvis doesn't need to print anything on the next line, it attempts to go to column 0 of the line after that using \r\n or \n\r, and the change breaks this. Bruce