From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] Literal character escapes in v7
Date: Tue, 07 Nov 2017 01:08:06 -0700 [thread overview]
Message-ID: <201711070808.vA7886fR006213@freefriends.org> (raw)
In-Reply-To: <1eee3597-4b32-0153-26de-87a973892b07@gmail.com>
Will Senn <will.senn at gmail.com> wrote:
> I wrote a c program to print a string in line with the suggestion to use
> awk and my code worked, but it's still odd that the above didn't work.
The V7 awk was really primitive. Another idea that occurred to me:
stty erase #
and then you can enter a literal backspace on the command line.
HTH,
Arnold
next prev parent reply other threads:[~2017-11-07 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 4:21 Will Senn
2017-11-07 4:34 ` arnold
2017-11-07 4:49 ` Will Senn
2017-11-07 5:00 ` Will Senn
2017-11-07 8:08 ` arnold [this message]
2017-11-07 9:07 ` Dennis Boone
2017-11-07 13:55 ` Will Senn
2017-11-07 11:21 ` Dan Cross
2017-11-07 14:59 ` Will Senn
2017-11-07 15:33 ` Don Hopkins
2017-11-08 16:48 ` Ralph Corderoy
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=201711070808.vA7886fR006213@freefriends.org \
--to=arnold@skeeve.com \
/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).