From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 35784@debbugs.gnu.org, marc@bloodnok.com
Subject: bug#35784: emacs 26 crash
Date: Sat, 18 May 2019 16:03:28 +0300 [thread overview]
Message-ID: <831s0vap9b.fsf@gnu.org> (raw)
In-Reply-To: <87zhnkc5zg.fsf@gmail.com> (message from Noam Postavsky on Sat, 18 May 2019 08:16:51 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Marc Munro <marc@bloodnok.com>, 35784@debbugs.gnu.org
> Date: Sat, 18 May 2019 08:16:51 -0400
>
> I'm able to reproduce using the latest emacs-26 branch (I don't have the
> point releases checked out at the moment), both lucid and gtk3 builds.
> It doesn't reproduce using master, there is a Lisp error (Symbol's
> definition is void: new-frame) that interferes.
>
> It actually crashes as soon as I close the *GNU Emacs* frame, no chance
> to type M-x. I modified the .emacs to this:
I still cannot reproduce, even after pointing HOME to the directory of
.emacs. I get an error about string, nil, and some errors during
redisplay in *Messages*, that's all.
next prev parent reply other threads:[~2019-05-18 13:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 20:54 bug#35784: emacs 26 crash Marc Munro
2019-05-18 6:19 ` Eli Zaretskii
2019-05-18 9:39 ` Bhavin Gandhi
2019-05-18 12:09 ` Eli Zaretskii
2019-05-18 12:16 ` Noam Postavsky
2019-05-18 13:03 ` Eli Zaretskii [this message]
2019-05-18 14:03 ` martin rudalics
2019-05-18 14:19 ` Noam Postavsky
2019-05-18 15:39 ` Eli Zaretskii
2019-05-18 17:30 ` martin rudalics
2019-05-18 17:43 ` Eli Zaretskii
2019-05-19 2:54 ` Noam Postavsky
2019-05-19 4:51 ` Eli Zaretskii
2019-05-19 6:40 ` martin rudalics
2019-05-19 17:11 ` Noam Postavsky
2019-05-19 17:59 ` Eli Zaretskii
2019-05-20 18:27 ` Noam Postavsky
2019-05-19 23:57 ` bug#35784: Just built from head: it seems to be fixed Marc Munro
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=831s0vap9b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35784@debbugs.gnu.org \
--cc=marc@bloodnok.com \
--cc=npostavs@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.