From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ur; Wed Jan 11 13:08:23 EST 2017 DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=sciops.net; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=7TVUoQ2waGaFRxxQSHJ8xw0B9OQ=; b=pVcq LITYexWJtDW611AAi0fP7dI5NOzjaf+7/gJbKchQ+qTHbM72biDln/kS8quM DomainKey-Signature: a=rsa-sha1; c=simple; d=sciops.net; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=default; b=H3w8v++xhqJ6FjVg51sRvz17wfyp2q VykeSaxUuLOgO1/i6FysrOiRCj83RAbvrq Received: (qmail 36436 invoked by uid 1001); 11 Jan 2017 18:08:20 -0000 Date: Wed, 11 Jan 2017 10:08:20 -0800 From: Kurt H Maier To: 9front@9front.org Subject: Re: [9front] '\n' equivalent for command input Message-ID: <20170111180820.GA34061@wopr> Mail-Followup-To: 9front@9front.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: TOR cloud property interface 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