From: Lewis Creary via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 66656@debbugs.gnu.org
Subject: bug#66656: Bug reports
Date: Fri, 20 Oct 2023 21:42:25 +0000 (UTC) [thread overview]
Message-ID: <472007690.294115.1697838145836@mail.yahoo.com> (raw)
In-Reply-To: 472007690.294115.1697838145836.ref@mail.yahoo.com
[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]
I'm reporting a bug in Gnu emacs lisp, but I'm also reporting a bug in theprocess of reporting emacs lisp bugs. This first bug consists in the factthat, 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 wouldinstead generate a "no such person" mailing error.
The main bug I'm reporting consists in the fact that recently, when I triedto test the lisp function displayed just below, I triggered the lisp errormessage "`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..
(defun octal-to-dec (n) (let* ((oct-str {number-to-string n) (octal-digits (string-to-reverse-numlist oct-str)) (oct-digit nil) (eight-powr-term-val 0) (eight-powr-sum 0) (indx 0) (while-nil-val (while (<= indx (length octal-digits)) (setq oct-digit (nth indx octal-digits) eight-powr-term-val (* oct-digit (expt 8 indx)) eight-powr-sum (+ eight-powr-sum eight-powr-term-val) indx (1+ index) ))) ) ; end of let-variables eight-powr-sum )))
Subject: 29.1; "lisp error when there is no error"
In GNU Emacs 29.1 (build 2, x86_64-w64-mingw32) of 2023-08-02 built on AVALONWindowing system distributor 'Microsoft Corp.', version 10.0.22621System Description: Microsoft Windows 10 Home (v10.0.2009.22621.2428)
Configured using: 'configure --with-modules --without-dbus --with-native-compilation=aot --without-compress-install --with-tree-sitter CFLAGS=-O2'
Configured features:ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMPNOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFFTOOLKIT_SCROLL_BARS TREE_SITTER WEBP XPM ZLIB
(NATIVE_COMP present but libgccjit not available)
Important settings: value of $LANG: ENU locale-coding-system: cp1252
Major mode: ELisp/d
[-- Attachment #2: Type: text/html, Size: 4310 bytes --]
next parent reply other threads:[~2023-10-20 21:42 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 ` Lewis Creary via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-20 22:06 ` bug#66656: Bug reports Stephen Berman
2023-10-21 7:27 ` Eli Zaretskii
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
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=472007690.294115.1697838145836@mail.yahoo.com \
--to=bug-gnu-emacs@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 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).