From: Fernando de Morais <fernandodemorais.jf@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: 62444@debbugs.gnu.org, emacs-erc@gnu.org, daniel@dpettersson.net
Subject: bug#62444: [PATCH] erc: Fix "dcc get" flag parsing
Date: Sun, 09 Jul 2023 15:02:21 -0300 [thread overview]
Message-ID: <871qhh55g2.fsf__1985.8526926086$1688925801$gmane$org@gmail.com> (raw)
In-Reply-To: <87ttue32rd.fsf@neverwas.me> (J. P.'s message of "Sat, 08 Jul 2023 07:18:46 -0700")
Hi J.P.,
"J.P." <jp@neverwas.me> writes:
> Gah, right, that was a dumb hack anyway. I shouldn't have suggested it.
It's always nice to help test ERC solutions, so don't worry about it! 😄
> But if you're still willing at this juncture, please give this one a
> go. And if you're not already doing something like
>
> find lisp/erc -name \*.elc -delete
>
> before rerunning make, please do, so we can rule out some corner-case
> weirdness (if you wouldn't mind). Thanks again.
I've applied the patch and tested it: the problem was solved!
Thanks for all the work on ERC!
--
Regards,
Fernando de Morais.
next prev parent reply other threads:[~2023-07-09 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 15:25 bug#62444: [PATCH] erc: Fix "dcc get" flag parsing Daniel Pettersson
2023-03-26 4:10 ` J.P.
[not found] ` <87a600xidp.fsf@neverwas.me>
2023-03-27 3:50 ` J.P.
2023-04-05 18:27 ` Daniel Pettersson
2023-04-08 22:53 ` J.P.
2023-07-08 3:22 ` Fernando de Morais
[not found] ` <878rbrxfkl.fsf@gmail.com>
2023-07-08 4:24 ` J.P.
2023-07-08 12:56 ` Fernando de Morais
[not found] ` <87sf9ywohp.fsf@gmail.com>
2023-07-08 14:18 ` J.P.
[not found] ` <87ttue32rd.fsf@neverwas.me>
2023-07-09 18:02 ` Fernando de Morais [this message]
[not found] ` <871qhh55g2.fsf@gmail.com>
2023-07-14 2:22 ` J.P.
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='871qhh55g2.fsf__1985.8526926086$1688925801$gmane$org@gmail.com' \
--to=fernandodemorais.jf@gmail.com \
--cc=62444@debbugs.gnu.org \
--cc=daniel@dpettersson.net \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
/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).