Path: csiph.com!aioe.org!news.glorb.com!usenet.stanford.edu!not-for-mail From: e est Newsgroups: gnu.bash.bug Subject: reverse-i-search, multibyte backspace problem Date: Sat, 18 Jul 2015 22:23:19 +0200 Lines: 47 Approved: bug-bash@gnu.org Message-ID: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1437254400 32575 208.118.235.17 (18 Jul 2015 21:20:00 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437251000; bh=xQLOU6X+LOk+y7M1DDyH56FEF9gTWWSXJ/x3FfCGyzM=; h=From:To:Subject:Date; b=lSPJBu28KJ1zDTpScoUbVVKSZdOk9X49ncd/Ozqug9omtVTZ1mi+C4ZrAlh7+GcyM HPfmK9rWTo1KkOj+YOQUy8jhrQAOe/L+BwgCqsun/ML+sNAyFoKVTM1Bq/LQV9beBu ubr/fTUXPCoserXrRntJHiUbQGpQMGZVQ3hKr028= X-Mailer: Yamail [ http://yandex.ru ] 5.0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 87.250.230.161 X-Mailman-Approved-At: Sat, 18 Jul 2015 17:19:59 -0400 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: aioe.org gnu.bash.bug:11235 Hello, I've noticed a bug with terminal usage of bash. Steps to reproduce: 1. Press control-r to get in reverse-i-search mode 2. Enter a key outside of the ASCII character set, like the french =C3=A9= or the german =C3=A4. 3. Press backspace. What to expect: The key gets removed. What happens: Instead of the whole key getting removed, you can see a weird character (= like =EF=BF=BD or =C3=83) appear. The most likely theory: Instead of adhering to the utf-8 multibyte specification, and removing th= e whole multibyte codepoint encoding sequence (or perhaps the whole seque= nce representing the "abstract character"? [1]), it just removes the last= byte. Note that the bug is dependent on the terminal. I've originally discovere= d the bug on konsole, but it has been confirmed by other users on the fre= enode #bash channel to exist on xterm, st and rxvt, but one user couldn't= reproduce it with st. Affected versions: I've tested 4.3.30(1)-release (my distro's packaged one) and 4.3.39(2)-re= lease, the latter coming straight from the development git repository's m= aster branch, compiled with ./configure && make -j 4. The operating system I use is Kubuntu, but it has been confirmed to exist= on Gentoo and arch linux too.=20 Thanks for answers. Greetings Est31. [1]: Quoting the Unicode standard, version 7, Section 3.4, Characters an= d Encoding: "A single abstract character may also be represented by a sequence of cod= e points=E2=80=94for example, "latin capital letter g with acute" may be = represented by the sequence , rather than being mapped to a single code point."