zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>, zsh-workers@zsh.org
Subject: Re: PATCH: overwrite mode shouldn't replace newlines
Date: Sun, 30 Nov 2014 11:24:01 -0800	[thread overview]
Message-ID: <141130112401.ZM28710@torch.brasslantern.com> (raw)
In-Reply-To: <547A719F.6000400@eastlink.ca>

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."


  reply	other threads:[~2014-11-30 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30  0:04 Oliver Kiddle
2014-11-30  1:23 ` Ray Andrews
2014-11-30 19:24   ` Bart Schaefer [this message]
2014-11-30 19:55     ` Ray Andrews
2014-11-30 21:42       ` Jan Larres

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=141130112401.ZM28710@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=rayandrews@eastlink.ca \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).