.. _invalid-character-carriage-return:

invalid-character-carriage-return / E2511
=========================================

**Message emitted:**

``Invalid unescaped character carriage-return, use "\r" instead.``

**Description:**

*Moves the cursor to the start of line, subsequent characters overwrite the start of the line.*


**Correct code:**

.. literalinclude:: /data/messages/i/invalid-character-carriage-return/good.py
   :language: python


**Additional details:**

This message exists because one of our checkers is very generic, but it's never going to
raise during normal use as it's a ``syntax-error`` that would prevent the python ast
(and thus pylint) from constructing a code representation of the file.

You could encounter it by feeding a properly constructed node directly to the checker.



Created by the `unicode_checker <https://github.com/pylint-dev/pylint/blob/main/pylint/checkers/unicode.py>`__ checker.