"Ilya N. Golubev" <gin(a)mo.msk.ru> wrote:
The bug does not occur if `comint-inhibit-carriage-motion' is
not
`nil'. And this value is not output by `report-emacs-bug'.
The `comint' version is upstream one.
This is a feature, not a bug. As the Emacs NEWS file explains it:
------------------------------------------------------------------------
*** Comint now by default interprets some carriage-control characters.
Comint now removes CRs from CR LF sequences, and treats single CRs and
BSs in the output in a way similar to a terminal (by deleting to the
beginning of the line, or deleting the previous character,
respectively). This is achieved by adding `comint-carriage-motion' to
the `comint-output-filter-functions' hook by default.
------------------------------------------------------------------------
Note also the third line of the comint-carriage-motion docstring (to
which the comint-inhibit-carriage-motion docstring refers):
------------------------------------------------------------------------
Interpret carriage control characters in the region from START to END.
Translate carriage return/linefeed sequences to linefeeds.
Make single carriage returns delete to the beginning of the line.
Make backspaces delete the previous character.
------------------------------------------------------------------------
If you are working on a system that is providing you with bare '\r'
characters, then you definitely want to be sure that
comint-inhibit-carriage-motion is non-nil.
--
Jerry James, Assistant Professor james(a)xemacs.org
Computer Science Department
http://www.cs.usu.edu/~jerry/
Utah State University