From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15837 invoked by alias); 30 Nov 2014 19:24:22 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33825 Received: (qmail 20206 invoked from network); 30 Nov 2014 19:24:19 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=F/vgrRlI c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=5y4faFyK3SkA:10 a=fbbdovFUm706MWakCN8A:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141130112401.ZM28710@torch.brasslantern.com> Date: Sun, 30 Nov 2014 11:24:01 -0800 In-reply-to: <547A719F.6000400@eastlink.ca> Comments: In reply to Ray Andrews "Re: PATCH: overwrite mode shouldn't replace newlines" (Nov 29, 5:23pm) References: <13244.1417305861@thecus.kiddle.eu> <547A719F.6000400@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Ray Andrews , zsh-workers@zsh.org Subject: Re: PATCH: overwrite mode shouldn't replace newlines MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Nov 29, 5:23pm, Ray Andrews wrote: } Subject: Re: PATCH: overwrite mode shouldn't replace newlines } } On 11/29/2014 04:04 PM, Oliver Kiddle wrote: } > In overwrite mode, either emacs style or vi-replace, on reaching the end } > of the line new characters should be inserted rather than the newline be } > replaced. } > } Sorry for ranting, just ignore this, but how is it possible that a } mistake in something so basic could have survived until now? Input editing of this sort isn't even the shell's "basic" job. (E.g. bash uses readline which is an entirely separate project tested and maintained independently.) There are plenty of "basic" things to rant about, but this doesn't qualify. } Are things so complicated that they can no longer be maintained? Since this bug has probably existed since the beginning of time (in zsh terms), it has little to do with complication that has crept in since. Like most open-source projects dating from the late 80s, zsh relied on users to test and report bugs. There has never been enough volunteer manpower for a dedicated all-code-paths testing regimen, so a bug that a real user never encounters will only rarely be fixed. That a patch showed up would argue against "no longer maintained."