The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <>
To: Noel Chiappa <>,
Subject: Re: [TUHS] svr2 delete behavior
Date: Mon, 27 Dec 2021 08:56:12 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On 12/27/21 8:37 AM, Noel Chiappa wrote:
>      > From: Will Senn
>      > 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
> I use ASCII 'backspace' (^H) on my V6, and it 'sort of' works; it doesn't
> erase the deleted character on the screen, but if one then types corrected
> characters, they overlay the deleted ones, leaving the corrected input.  That
> should work on everything later than V6.
> The MIT PWB1 tty handler (link in a prior message) not only supported a 'kill
> line' (we generally used '^U') which actually visibly deleted the old line
> contents (on screen terminals, of course; on printing terminals you're
> stuck), it also had suppport for '^R' (re-type line) and some other stuff.
> 	Noel
Hi Noel, that's interesting.

I hadn't tried it in v6 in a while. I'd pretty much resigned myself to # 
and @. But I see the effect in v6, even without changing stty and it 
'works', but in svr2, if I type lsa and then hit ^H it backs up a place, 
but then when I press enter the shell says something along the lines of 
- lsa^H: not found. But by adding stty erase ^H, it then 'works' the 
same as in v6. Seth's steer regarding setting erase and echoe 'fixed' 
things, once I figured out that having DEL doubling as intr wasn't ideal.

Oh, the mysteries of terminal interaction. Add the fact that I'm using 
Mac OS's Terminal, and no telling what could happen. I generally turn on 
Option as Meta magic but I don't remap ^H as DEL :).


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

  reply	other threads:[~2021-12-27 14:56 UTC|newest]

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

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:

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

  git send-email \ \ \ \ \

* 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).