From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: PATCH: overwrite mode shouldn't replace newlines
Date: Sat, 29 Nov 2014 17:23:43 -0800 [thread overview]
Message-ID: <547A719F.6000400@eastlink.ca> (raw)
In-Reply-To: <13244.1417305861@thecus.kiddle.eu>
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? How can
the best, and the second most used, shell in 'nix have permitted such an
oversight to have existed for (what?) four decades? When folks run into
those things, do they just shrug their shoulders? We see so many things
that are just-plain-bugs, how do they get past testing? It seems that
culturally one should view the shells as sorta like the New York subway
system--it's huge and the trains mostly run on time, but don't bet your
life on it, and if the system breaks down, just stay calm they'll fix it
eventually. Are things so complicated that they can no longer be
maintained? Sheesh, after the kernel, the most bullet proof thing on a
computer should be the shell. Dunno, but it's hard to understand.
next prev parent reply other threads:[~2014-11-30 1:54 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 [this message]
2014-11-30 19:24 ` Bart Schaefer
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=547A719F.6000400@eastlink.ca \
--to=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).