GNU bug report logs - #78043
Cursor gets stuck after inline code input in comint buffer when using markdown-mode, bypassing prompt lines starting with '>'

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Kang Tu <tninja <at> gmail.com>
Cc: 78043 <at> debbugs.gnu.org
Subject: bug#78043: Cursor gets stuck after inline code input in comint buffer when using markdown-mode, bypassing prompt lines starting with '>'
Date: Fri, 25 Apr 2025 18:52:26 +0300

> From: Kang Tu <tninja <at> gmail.com>
> Date: Fri, 25 Apr 2025 06:56:56 -0700
> Cc: 78043 <at> debbugs.gnu.org
> 
> Actually we are wondering if it is a comint-mode bug. This line suppose to suppress markdown-mode
> rendering on comint input line (start with > character):
> https://github.com/tninja/aider.el/blob/main/aider-core.el#L67, However it doesn't work as expected.
> 
> We are discussed in this github issue, and font-lock-defaults seems to be right:
> https://github.com/tninja/aider.el/issues/126#issuecomment-2816839141, so we suspect it is a comint-mode
> bug, for not being able to override on comint input line.
> 
> Would you mind help take a look at this?

I would, if you could provide a recipe for reproduction that starts
from "emacs -Q" and preferably doesn't need to load markdown-mode.  If
this is a comint issue, then there should be a way of reproducing the
problem without markdown-mode.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.