From: Eli Zaretskii <eliz@gnu.org>
To: Lewis Creary <lewcreary@cs.com>
Cc: 66656@debbugs.gnu.org
Subject: bug#66656: Bug reports
Date: Sat, 21 Oct 2023 10:27:04 +0300 [thread overview]
Message-ID: <83edhosaev.fsf@gnu.org> (raw)
In-Reply-To: <472007690.294115.1697838145836@mail.yahoo.com> (bug-gnu-emacs@gnu.org)
> 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.
next prev parent reply other threads:[~2023-10-21 7:27 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 [this message]
2023-12-22 14:57 ` Stefan Kangas
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=83edhosaev.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66656@debbugs.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 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.