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

On 2019/01/28 22:23, Valery Ushakov wrote: Rin Okuyama 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)

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

Rin Okuyama 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, s

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

Hi, 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? I would like to commit the patch below, if there's no objections. T