From: Istvan Marko <ebugs@kismala.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 69010@debbugs.gnu.org
Subject: bug#69010: 29.2.50; rcirc-process-regexp doesn't handle the "draft" prefix
Date: Sat, 10 Feb 2024 10:43:07 -0800 [thread overview]
Message-ID: <m3cyt4p3d0.fsf@zsu.kismala.com> (raw)
In-Reply-To: <87h6ig2qbv.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
> Instead of hard-coding "draft", would there be an issue with replacing
> (0) with `zero-or-more'?
That would work too, just wasn't sure how strict we want the parsing to
be.
--
Istvan
next prev parent reply other threads:[~2024-02-10 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 7:15 bug#69010: 29.2.50; rcirc-process-regexp doesn't handle the "draft" prefix Istvan Marko
2024-02-10 17:15 ` Philip Kaludercic
2024-02-10 18:43 ` Istvan Marko [this message]
2024-02-10 19:28 ` Philip Kaludercic
2024-02-11 2:08 ` Istvan Marko
2024-02-11 9:29 ` Philip Kaludercic
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=m3cyt4p3d0.fsf@zsu.kismala.com \
--to=ebugs@kismala.com \
--cc=69010@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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).