[BUG] Text.from_ansi leaves empty lines when input string has CRLF line endings

[kaipons]

• I've checked docs and closed issues for possible solutions.
• I can't find my issue in the FAQ.

Describe the bug

When Text.from_ansi is given an input string with CRLF (\r\n) line endings the result is just empty lines:

Python 3.12.3 (main, Mar  3 2026, 12:15:18) [GCC 13.3.0] on linux                                                                                                                                                                                             
Type "help", "copyright", "credits" or "license" for more information.                                                                                                                                                                                        
>>> from rich.text import Text
>>> Text.from_ansi("Hello\r\nWorld\r\n").plain                  
'\n\n'

when the expected result would be

'Hello\r\nWorld\r\n'

or even

'Hello\nWorld\n'

rich versions <15.0.0 are affected by #3577 but do not result in empty lines.

Platform

• python 3.12.3
• rich 15.0.0

[github-actions]

We found the following entry in the FAQ which you may find helpful:

• Why does content in square brackets disappear?

Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review.

Rich was created by Will McGugan. Consider sponsoring Will's work on Rich.

This is an automated reply, generated by FAQtory

[souhil25]

i have tried it, here what it displays:

>>> from rich.text import Text
>>> Text.from_ansi("Hello\r\nWorld\r\n").plain
'Hello\nWorld'
>>>

[alxgu]

@souhil25 which python and rich version are you using?

I got the same issue :(

❯ python3
Python 3.13.12 (main, Feb  3 2026, 17:53:27) [GCC 12.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from rich.text import Text
>>> Text.from_ansi("Hello\r\nWorld\r\n").plain
'\n\n'
>>>
>>> from importlib.metadata import version
>>> version("rich")
'15.0.0'

[NSPC911]

Can reproduce as well, specifically commit 69cee6e is causing this.