From: Matthias Meulien <orontee@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58228@debbugs.gnu.org, Jose A Ortega Ruiz <jao@gnu.org>
Subject: bug#58228: 29.0.50; ansi-term display garbled
Date: Sat, 01 Oct 2022 22:18:13 +0200 [thread overview]
Message-ID: <874jwn9u2i.fsf@gmail.com> (raw)
In-Reply-To: <8735c7til0.fsf@gmail.com> (Matthias Meulien's message of "Sat, 01 Oct 2022 22:06:03 +0200")
Matthias Meulien <orontee@gmail.com> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Jose A Ortega Ruiz <jao@gnu.org> writes:
>>
>>> - M-x ansi-term (accept default /bin/bash)
>>>
>>> - type anything in the bash prompt that produces output, a simple ls
>>> will suffice: the output is garbled, sometimes non-existent (the
>>> effect is very dramatic for ncurses apps).
>>
>> Perhaps this is related to the recent comint/osc stuff? I've added
>> Matthias to the CCs.
>
> I don't think so. For example running ansi-term after setting
> comint-output-filter-functions to nil leads to the same garbled output.
>
> Bisecting between the parent of (working as expected and not containing
> any of my changes to the OSC stuff):
>
> 7354f4e3e6..: Matthias Meulien 2022-09-18 Extract support of OSC escape
> sequences from comint
>
> and the broken:
>
> cd4208f6d8..: Miha Rihtaršič 2022-09-30 Rename comint-fl-* to
> comint-fontify-input-* and mention it in NEWS
>
> leads to the first bad comit being:
>
> matthias@carbon:~/Sources/emacs ((12a78711c9...) $|BISECTING)
> ↳ git bisect good
> 3553904a90a242b7ee7b48607ac02cf57e2ab753 is the first bad commit
> commit 3553904a90a242b7ee7b48607ac02cf57e2ab753
> Author: Eli Zaretskii <eliz@gnu.org>
> Date: Fri Sep 30 15:38:22 2022 +0300
>
> Fix some issues with vertical-motion in bidi-reordered text
>
> This fixes some uses of vertical-motion when a screen line
> starts withcharacters of directionality that is opposite to
> the current paragraph's base direction.
> * src/xdisp.c (move_it_vertically_backward): Adjust NLINES to
> compensate for its increasing when DY == 0.
>
> src/xdisp.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
But note that current HEAD of master branch is working fine. I guess
the following commit fixed the problem:
3bd9606922..: Eli Zaretskii 2022-10-01 ; Another fix for vertical motion
--
Matthias
next prev parent reply other threads:[~2022-10-01 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 15:07 bug#58228: 29.0.50; ansi-term display garbled Jose A Ortega Ruiz
2022-10-01 15:29 ` Lars Ingebrigtsen
2022-10-01 20:06 ` Matthias Meulien
2022-10-01 20:18 ` Matthias Meulien [this message]
2022-10-02 1:32 ` Jose A Ortega Ruiz
2022-10-02 6:05 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jwn9u2i.fsf@gmail.com \
--to=orontee@gmail.com \
--cc=58228@debbugs.gnu.org \
--cc=jao@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).