From: "J.P." <jp@neverwas.me>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Amin Bandali <bandali@gnu.org>, 50005@debbugs.gnu.org
Subject: bug#50005: 28.0.50; silence a couple byte-compiler warnings in ERC
Date: Thu, 12 Aug 2021 06:35:31 -0700 [thread overview]
Message-ID: <87sfzeeqfw.fsf@neverwas.me> (raw)
In-Reply-To: <DED2F755-91E6-441B-9065-B91732D304CE@acm.org> ("Mattias Engdegård"'s message of "Thu, 12 Aug 2021 13:52:16 +0200")
Mattias Engdegård <mattiase@acm.org> writes:
> The string made it look like backslash were a special character inside
> [...]. It isn't;
Thanks, and sorry you had to explain that. Sad as it is, I'm fairly
certain I even read as much in the Info manual only moments before
defiling that doc string:
You cannot use ‘\’ to escape these three characters, since ‘\’ is not
special here.
> Most ordinary uses of rx will not even require rx.el to be loaded at
> runtime since the macros are expanded during compilation
Again, thanks. Although I should know this instinctively by now, I too
often forget it when deep in the weeds.
> If you meant (in "a-c") in your first example then yes, quite right
Um, yeah, sure, let's go with that! ;)
> Wish I could but time probably doesn't permit, sorry.
Darn, well I definitely appreciate your insights on this one and the
effort made relating them (frustrating as that might have been).
> Of course I'll be happy to answer specifics about parts that I happen
> to know something about.
You may live to regret those words. (Thanks again.)
next prev parent reply other threads:[~2021-08-12 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 13:57 bug#50005: 28.0.50; silence a couple byte-compiler warnings in ERC J.P.
2021-08-12 8:15 ` Mattias Engdegård
2021-08-12 10:56 ` J.P.
2021-08-12 11:52 ` Mattias Engdegård
2021-08-12 13:35 ` J.P. [this message]
2021-09-12 12:03 ` J.P.
2021-09-16 13:25 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfzeeqfw.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=50005@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=mattiase@acm.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.