From: Eli Zaretskii <eliz@gnu.org>
To: public@jds.work
Cc: 69914@debbugs.gnu.org
Subject: bug#69914: comint-strip-ctrl-m doesn't function as documentation states
Date: Sat, 30 Nov 2024 11:47:22 +0200 [thread overview]
Message-ID: <86a5dh9hp1.fsf@gnu.org> (raw)
In-Reply-To: <86ttcajish.fsf@gnu.org> (message from Eli Zaretskii on Thu, 14 Nov 2024 10:55:58 +0200)
> 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?
next prev parent reply other threads:[~2024-11-30 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 14:15 bug#69914: comint-strip-ctrl-m doesn't function as documentation states Jonathan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-23 7:30 ` Eli Zaretskii
2024-04-06 8:58 ` Eli Zaretskii
2024-04-18 9:01 ` Eli Zaretskii
2024-11-03 2:54 ` Jonathan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 8:55 ` Eli Zaretskii
2024-11-30 9:47 ` Eli Zaretskii [this message]
2024-12-14 9:33 ` 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=86a5dh9hp1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69914@debbugs.gnu.org \
--cc=public@jds.work \
/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).