From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66656-done@debbugs.gnu.org, Lewis Creary <lewcreary@cs.com>
Subject: bug#66656: Bug reports
Date: Fri, 22 Dec 2023 06:57:05 -0800 [thread overview]
Message-ID: <CADwFkm=FvPD_nhmhQ-0Aa+NW0z=F_JzAgNL=dVf46XcBwcA7cw@mail.gmail.com> (raw)
In-Reply-To: <83edhosaev.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Oct 2023 10:27:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Fri, 20 Oct 2023 21:42:25 +0000 (UTC)
>> From: Lewis Creary via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> I'm reporting a bug in Gnu emacs lisp, but I'm also reporting a bug in the
>> process of reporting emacs lisp bugs. This first bug consists in the fact
>> that, in bug reports sent using M-x report-emacs-bug, my email address (lewcreary@cs.com, in the
>> "from:" field of the email), would have been mangled into a somewhat similar, but different, address
>> in the process of submitting the report. As a result, any acknowledgment email intended for me (but
>> sent to the mangled address) would not reach me, but would
>> instead generate a "no such person" mailing error.
>
> AFAIK, this should not happen. In particular, this response email,
> where the To: header was produced by my MUA, has your correct
> unmangled email address.
>
>> The main bug I'm reporting consists in the fact that recently, when I tried
>> to test the lisp function displayed just below, I triggered the lisp error
>> message "`let' bindings can have only one value-form", when it is clear from inspection of the let* form
>> in question that no such bug exists. The let* form in question does have just one value-form, the lisp
>> variable
>> eight-powr-sum..
>
> As Steve points out, the first binding includes an error, a typo,
> where { was used instead of (.
>
> I see no Emacs bug here.
I'm therefore closing this bug report.
prev parent reply other threads:[~2023-12-22 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <472007690.294115.1697838145836.ref@mail.yahoo.com>
2023-10-20 21:42 ` bug#66656: Bug reports Lewis Creary via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20 22:06 ` Stephen Berman
2023-10-21 7:27 ` Eli Zaretskii
2023-12-22 14:57 ` Stefan Kangas [this message]
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='CADwFkm=FvPD_nhmhQ-0Aa+NW0z=F_JzAgNL=dVf46XcBwcA7cw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=66656-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lewcreary@cs.com \
/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).