Path: csiph.com!aioe.org!news.glorb.com!usenet.stanford.edu!not-for-mail From: Eduardo =?utf-8?Q?A=2E_Bustamante_L=C3=B3pez?= Newsgroups: gnu.bash.bug Subject: Re: reverse-i-search, multibyte backspace problem Date: Sat, 18 Jul 2015 22:16:54 -0500 Lines: 22 Approved: bug-bash@gnu.org Message-ID: References: <274381437250999@web18h.yandex.ru> <20150719015352.GA32433@ma.sdf.org> <176381437272716@web13m.yandex.ru> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1437275822 11525 208.118.235.17 (19 Jul 2015 03:17:02 GMT) X-Complaints-To: action@cs.stanford.edu Cc: "bug-bash@gnu.org" To: e est Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=YYWIZJbuwE2EE79aKozLlY2iaA5MuASNmXzcBe/jMEM=; b=W5PunAC3jrVIMlQmiJTrj99am0aDyOath7Xa2W1K4LGrM+4WkHsttLVFVFiELRQ94X 1/TSXmYNgT16h5zwycARnz7Lf7LNSn70P0CS8xgrNHh7boeWx3qTyzgrq6/p5ysZOGew oKV8vCGoC8Tixi2ob12hVKCNMIKilcQYMO8l+UuDSLQGAE/MNKDKqd2sttkCSA9JcVCV Kdm9Tvi6CXYAuTPJKmCmjY7GGDkWy45O3P9dFh1UbrMR3B4w+T0ayqbr0OkZz/NeIW2+ XRs10/aBSR+OieDZPP/hBiqPm7On8TvV4M2vyJ1SRmrV6nZeq4LNKqM6p9v7lEQb5MA0 VqoA== X-Received: by 10.66.122.207 with SMTP id lu15mr2208953pab.146.1437275815889; Sat, 18 Jul 2015 20:16:55 -0700 (PDT) Mail-Followup-To: e est , "bug-bash@gnu.org" Content-Disposition: inline In-Reply-To: <176381437272716@web13m.yandex.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::230 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:11238 On Sun, Jul 19, 2015 at 04:25:16AM +0200, e est wrote: > Hello, > > Thanks for pointing out the fix. I've tried the "devel" branch, and couldn't reproduce the bug there. > > Sorry for the disturbance, I should have checked whether the master branch really represents the bleeding edge of development. Do not worry. It's better to be safe than sorry! Thank you for taking your time to reproduce the bug in multiple versions and operating systems. Bash's git repository has two main branches: - master, which is the 'stable' version of bash, which is the one distributed in most toolsets and it has a slower "release cycle" - devel, which is the 'development' version of bash, which consists of snapshots of Chet's current work, just published for your amusement, since it might be broken. -- Eduardo Bustamante https://dualbus.me/