From: Jim Myhrberg <contact@jimeh.me>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45701@debbugs.gnu.org, Justin Schell <justinmschell@gmail.com>
Subject: bug#45701: 28.0.50; [feature/native-comp] (33b8ce8) `M-x report-emacs-bug` error: "Wrong type argument: stringp, nil"
Date: Wed, 6 Jan 2021 23:54:56 +0000 [thread overview]
Message-ID: <CAGaZ61toD0kocgi3SZ+mj6KtauJUqvC+DM6sej5Vpm7R6qcZ0Q@mail.gmail.com> (raw)
In-Reply-To: <CAGaZ61vGpy66DOBOeALsuLj1FcDR4_ipw2m5g3YZWHSw5x7AEQ@mail.gmail.com>
I'm afraid I can't reproduce the `M-x report-emacs-bug` issue on
33b8ce8, both with -Q and with my full config. I'm currently on macOS
Big Sur 11.1 (20C69) and Xcode 12.3 (12C33), with all the latest
dependencies from the Brewfile installed. But I have a build of commit
bd693cc (2020-12-25) from macOS Catalina 10.15.7 which does not
exhibit the issue either.
Justin, if your Xcode or Homebrew deps are not fully up to date, I'd
say start there, I've seen odd behavior a few times fixed by simply
updating deps.
> I've been trying to isolate the commit that introduced the reported
> issue and it appears to be between commits `0f561ee` (issue not
> present) and `a3f2373` (issue present).
As far as I can tell commit 0f561ee is from the master branch, so it
does not include any of the changes from the feature/native-comp
branch. I tend to use this as a quick way to see recent commits:
https://github.com/emacs-mirror/emacs/compare/feature/native-comp
And probably of less use in this particular case, but I maintain a
list of feature/native-comp commits which have yielded problem free
builds for me: https://github.com/jimeh/build-emacs-for-macos/issues/6
next prev parent reply other threads:[~2021-01-06 23:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 19:16 bug#45701: 28.0.50; [feature/native-comp] (33b8ce8) `M-x report-emacs-bug` error: "Wrong type argument: stringp, nil" Justin Schell
2021-01-06 19:28 ` Eli Zaretskii
2021-01-06 20:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-06 20:46 ` Justin Schell
2021-01-06 20:48 ` Jim Myhrberg
2021-01-06 23:54 ` Jim Myhrberg [this message]
2021-01-07 0:45 ` Justin Schell
2021-01-07 22:45 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-08 0:20 ` Justin Schell
2021-01-08 11:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-08 14:47 ` Justin Schell
2021-01-08 15:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-01 21:13 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-01 21:51 ` Justin Schell
2021-02-01 22:21 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-01 23:10 ` Justin Schell
2021-02-02 9:05 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-03 1:30 ` Justin Schell
2021-02-03 20:31 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-03 20:36 ` Justin Schell
2021-02-08 20:49 ` Justin Schell
2021-02-08 20:57 ` Justin Schell
2021-02-09 20:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-09 21:10 ` Justin Schell
2021-02-09 21:23 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-09 21:33 ` Justin Schell
2021-02-10 3:18 ` Jim Myhrberg
2021-02-10 4:40 ` Justin Schell
2021-02-10 9:09 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CAGaZ61toD0kocgi3SZ+mj6KtauJUqvC+DM6sej5Vpm7R6qcZ0Q@mail.gmail.com \
--to=contact@jimeh.me \
--cc=45701@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=justinmschell@gmail.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.