Re: term.el does not handle \n.

[Lute Kamstra]

Lute Kamstra <address@hidden> writes:

> I have the following five line file:
>
> ,----[ test.txt ]
> | Line one.
> | Line two.
> | Line three.
> | Line four.
> | Line five.
> `----
>
> When I do "M-x term" and use `/bin/bash', the following happens:
>
> ,----[ *terminal* ]
> | $ cat test.txt 
> |               Line one.
> |                        Line two.
> |                                 Line three.
> |                                            Line four.
> |                                                      Line five.
> |                                                                $ 
> `----
>
> As you can see, \n is not handled.

I sort of figured out why Emacs 21.3 handles this correctly and CVS
Emacs does not.  With Emacs 21.3 the following string is sent to the
filter function term-emulate-terminal by the shell process:

  "Line one.\r\nLine two.\r\nLine three.\r\nLine four.\r\nLine five.\r\n...

In CVS Emacs the filter function receives this string:

  "Line one.\nLine two.\nLine three.\nLine four.\nLine five.\n...

The absence of \r characters causes the undesired behavior of term.
Was the implementation of asynchronous processes intentionally changed
or is this a bug?

  Lute.