From owner-freebsd-questions@freebsd.org Wed Apr 25 14:26:09 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98252FA7521 for ; Wed, 25 Apr 2018 14:26:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4184F72B47 for ; Wed, 25 Apr 2018 14:26:08 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7726121C2E for ; Wed, 25 Apr 2018 10:26:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 25 Apr 2018 10:26:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=l1tBdHNp/m5FIXEFEVP37NHL39Hy8hVIzlpwuCMjqGY=; b=Oos31oGi lETV/mTkTokoybiqNvGxv8xMT74pZIy3sGRpCQnaRJ6QIt5Pnj/h2YRh+2qCm7ac lB0KJiiEOozjkvUjxDqSrdghJP4QhONQeDW5GNuAnQZLwh9PG+ajxThT6pStSTuu iGSix+wJlKl4p36nhawU5fSaIY8lmrx0SU0vQlR2FngpbZAvZSgnUIoVCfNMHV6l LBuj6C7eissIEz7xGqQ3HNP8d4zn2yuEVDsP0SNgA3kFSrcZGX7p5zTXOvtpT1yT erZYm6NZ7U7g4bFEmyq6xuKWcmpgDp7+B54/gYdChcauQUX8w4jUutK3XdOS3ulm BxK02buNNwTKtg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=l1tBdHNp/m5FIXEFEVP37NHL39Hy8 hVIzlpwuCMjqGY=; b=PoVFkwZWmxCUd/K+Zssdna+4rYJSKYtKOcxuoSLT60e66 o3njzVpdubK6IVpLMajpOF+nTQ5zfbpsL4ryMb/IIJr08CCu/XIrprUNjrijN6iF wB2IIJZ2UyDmCE00V28hddw20/iFIZDUDvnJSepvWw6A2ikBtKCUl6GFMGLAm1Au vBQsxraPJkYymJozX0kqxOMu/7y8PQ4DMtkG9mj9lxTMlyUABLdLk/PanFDLpNlV NLmi6y1qHvUNV5FfMWHX1BqnHLuX8V0cbdC2TeqxCYvND7TsyL4crIXzaumC7VZd XIsoA/pxeraxLs/eeAkpBkP3gG1LTrTJ6Al6XMTUg== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id DD680E49E9 for ; Wed, 25 Apr 2018 10:26:07 -0400 (EDT) Date: Wed, 25 Apr 2018 15:26:06 +0100 From: tech-lists@zyxst.net To: freebsd-questions@freebsd.org Subject: bash history buffer output mangled after repeated up-arrow Message-ID: <20180425142605.GA39933@desktop.local> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Apr 2018 14:26:09 -0000 hi, I've noticed now, for a while (like maybe over a year) that if you're in bash shell, hitting up-arrow (which usually loads history -1) multiple times will result in part of history becoming the prompt. I use csh as login shell now because csh doesn't have this problem. I can re-create the issue by logging in then doing the following: % bash $ . .profile hit uparrow a few times (in this case, 15 times), it gets to this in its history: bzcat /var/log/messages.1.bz2 |less prompt is now: [john@desktop ~]$ bzcat /var<--cursor is here waiting for input [keep hitting up arrow] now it's [john@desktop ~]$ ls -lah .g[history] where [history] is=20 find /usr/src/sys/sys/param.h -mtime; echo backspacing to (in this case) [john@desktop ~]$ ls -lah .g (which is as far as one can backspace on that line) and hitting return, restored the=20 normal prompt position. Repeatedly hitting up-arrow mangles bash history. it doesn't happen in csh. Not tried other shells. It only happens on freebsd boxes (11-stable and later). I've not seen it happen on linuxen=20 (raspabian, mint, ubuntu, centos). It doesn't matter if bash is built from= =20 source or installed via pkg. Doesn't matter if fdescfs is mounted or not. It still happens if I create a fresh freebsd-11-stable VM, log into it, install bash. Any ideas? thanks, --=20 J.