From owner-freebsd-current Fri Oct 29 10:57:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 381B615483 for ; Fri, 29 Oct 1999 10:57:19 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA05455 for ; Fri, 29 Oct 1999 13:57:18 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18701; Fri, 29 Oct 1999 13:56:48 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id NAA20672; Fri, 29 Oct 1999 13:56:47 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199910291756.NAA20672@dean.pc.sas.com> Subject: emacs / ncurses - problem somewhere To: freebsd-current@freebsd.org Date: Fri, 29 Oct 1999 13:56:47 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Ever since the libtermcap / libncurses consolidation, change emacs has problems positioning the cursor and properly updating the screen for character-only devices like the console. It also affects the display in an xterm in non-X mode, i.e., when DISPLAY is *not* set. This is emacs 20.4, by the way on current as of yesterday. I've tried emacs from packages as well as a freshly built one from the ports and both exhibit the problem. Note that emacs works fine when it brings up is own window due to DISPLAY being set. Has anyone else seen this and already have a fix or know for sure whether this is an emacs bug or a FreeBSD bug? Thanks, -Brian -- Brian Dean brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message