On 2019/01/28 22:23, Valery Ushakov wrote:
Rin Okuyama <rokuy...@rk.phys.keio.ac.jp> 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.
Yeah, <Enter> works. But, why ^J does not, although most other terminal-
based applications treats ^M and ^J equivalently? E.g., ~ after ^J just
works for ssh. If there's no reason not to regard ^J as end-of-line,
I would like to commit the patch in the previous message. (I usually use
^J instead of <Enter>.)
Thanks,
rin
