From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] '\n' equivalent for command input
Date: Wed, 11 Jan 2017 10:08:20 -0800 [thread overview]
Message-ID: <20170111180820.GA34061@wopr> (raw)
In-Reply-To: <CALmPRuC6pEJj-ZAzMtViArH6qK-m4SNg4qfMbK8E-c123-r06Q@mail.gmail.com>
On Wed, Jan 11, 2017 at 04:05:02PM -0200, Micael Ramos wrote:
> There is another representation for newline other than '\n' for standard
> input?
>
> When running commands, '\n' is never recognized. Example:
>
> tr '\n' 'newline' < text.txt
Look at the manpage for tr(1). Only octal is recognized. Try
tr '\012' 'o'
for instance.
khm
next prev parent reply other threads:[~2017-01-11 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 18:05 Micael Ramos
2017-01-11 18:08 ` Kurt H Maier [this message]
2017-01-11 18:22 ` [9front] " Micael Ramos
2017-01-11 18:30 ` Antons Suspans
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=20170111180820.GA34061@wopr \
--to=khm@sciops.net \
--cc=9front@9front.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).