bug#69914: comint-strip-ctrl-m doesn't function as documentation states

[Eli Zaretskii <eliz@gnu.org>]

Ping! Ping!

> Cc: 69914@debbugs.gnu.org
> Date: Sat, 14 Dec 2024 11:33:04 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> Ping!
> 
> > Cc: 69914@debbugs.gnu.org
> > Date: Sat, 30 Nov 2024 11:47:22 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> > 
> > > Cc: 69914@debbugs.gnu.org
> > > Date: Thu, 14 Nov 2024 10:55:58 +0200
> > > From: Eli Zaretskii <eliz@gnu.org>
> > > 
> > > > Date: Sun, 03 Nov 2024 02:54:14 +0000
> > > > From: Jonathan <public@jds.work>
> > > > Cc: 69914@debbugs.gnu.org
> > > > 
> > > > My apologies. This completely dropped off my radar as a few life events took precedence over the past few months and took me away from this. Things are more settled now though.
> > > > 
> > > > I do agree this appears to be a common trend among the comint filter functions. I will get together a patch including a new version of =comint-strip-ctrl-m= named something different of course, and updating the documentation that I can track down.
> > > > 
> > > > I do just anticipate this to take a little time as this would be my first contribution to the project and I'm still learning my way around. If all this is amenable to you I'll move forward with my solution and get a patch sent in soon. 
> > > 
> > > Yes, please go ahead, and thanks.
> > 
> > Did you have an opportunity to make some progress?
> > 
> > 
> > 
> > 
> 
> 
> 
>