The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] svr2 delete behavior
Date: Sun, 26 Dec 2021 18:31:38 -0600	[thread overview]
Message-ID: <509bcd30-d0cb-2d39-3101-5c32ea3a058f@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

Did svr2 have anything similar to modern behavior when handling the 
delete/backspace key where the character is deleted from the input and 
rubbed out? The default, like in v6/v7 for erase and kill is # and @. I 
can live with this, if I can't get it to do the rubout, because at least 
you can see the # in the input, but if I can figure out how to get it to 
rubout the last character, I'd map erase to DEL, which I believe to be 
^U (but since it's invisible, it's confusing when it doesn't rubout).

Will

[-- Attachment #2: Type: text/html, Size: 761 bytes --]

             reply	other threads:[~2021-12-27  0:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27  0:31 Will Senn [this message]
2021-12-27  1:24 ` Seth Morabito
2021-12-27 14:39   ` Will Senn
2021-12-27 14:37 Noel Chiappa
2021-12-27 14:56 ` Will Senn
2021-12-27 23:52   ` John Cowan

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=509bcd30-d0cb-2d39-3101-5c32ea3a058f@gmail.com \
    --to=will.senn@gmail.com \
    --cc=tuhs@minnie.tuhs.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.
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).