tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: cu(1) / tip(1) : recognize newline as end-of-line

To: tech-userlevel%netbsd.org@localhost
Subject: Re: cu(1) / tip(1) : recognize newline as end-of-line
From: uwe%stderr.spb.ru@localhost (Valery Ushakov)
Date: Mon, 28 Jan 2019 13:23:40 -0000 (UTC)

Rin Okuyama <rokuyama%rk.phys.keio.ac.jp@localhost> wrote:

> Currently, cu(1) and tip(1) do not recognize a newline as end-of-line.
> This means that an escape character (~) does not work after ^J (dislike ^M).
> 
> It seems like a bug for me. But, are there some reasons for this behavior?

tip(1) clears ICRNL from terminal settings, so the <Enter> key sends
^M, not ^J.

-uwe

Follow-Ups:
- Re: cu(1) / tip(1) : recognize newline as end-of-line
  - From: Rin Okuyama

References:
- cu(1) / tip(1) : recognize newline as end-of-line
  - From: Rin Okuyama

Prev by Date: cu(1) / tip(1) : recognize newline as end-of-line
Next by Date: Re: cu(1) / tip(1) : recognize newline as end-of-line
Previous by Thread: cu(1) / tip(1) : recognize newline as end-of-line
Next by Thread: Re: cu(1) / tip(1) : recognize newline as end-of-line
Indexes:

Home | Main Index | Thread Index | Old Index