unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vasilij Schneidermann <mail@vasilij.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	Keith David Bershatsky <esq@lawlist.com>,
	27779@debbugs.gnu.org
Subject: bug#27779: #27779; C stack overflow from `read' on deeply nested lisp object.
Date: Thu, 7 Jun 2018 10:18:03 +0200	[thread overview]
Message-ID: <20180607081801.dzcldvkblxhakais@odonien.localdomain> (raw)
In-Reply-To: <87o9gn4n7u.fsf@gmail.com>

> Only if they've set undo-tree-auto-save-history, right?  (which, for all
> I know, might be a really popular setting)

Hm, you're right.  This bug effectively neuters that feature, if I
disable it I can load up Emacs just fine.  The setting isn't nearly as
popular as Evil.

I can only wonder how many more packages rely on reading deeply nested
trees...





  reply	other threads:[~2018-06-07  8:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21  2:12 bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow Keith David Bershatsky
2017-07-21  3:03 ` Keith David Bershatsky
2017-07-22  3:24   ` npostavs
2017-07-22  5:52 ` Keith David Bershatsky
2017-07-22 12:05   ` npostavs
2017-07-22 16:32 ` Keith David Bershatsky
2017-07-22 17:23   ` npostavs
2017-07-22 21:31 ` Keith David Bershatsky
2017-07-23  2:45   ` npostavs
2017-07-23 22:28 ` Keith David Bershatsky
2018-01-09  1:38 ` bug#27779: #27779; C stack overflow from `read' on deeply nested lisp object Keith David Bershatsky
2018-06-06 21:04 ` Vasilij Schneidermann
2018-06-06 21:30   ` Noam Postavsky
2018-06-07  8:18     ` Vasilij Schneidermann [this message]
2019-05-02  2:30   ` Noam Postavsky
2019-05-02  7:05 ` Keith David Bershatsky
2019-05-02  7:26   ` Paul Eggert
2019-05-02  8:00 ` Keith David Bershatsky
2022-04-21 13:33   ` bug#27779: 26.0.50: read -- Re-entering top level after C stack overflow Lars Ingebrigtsen
2022-04-21 18:56 ` Keith David Bershatsky
2022-04-22  0:26   ` Paul Eggert

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=20180607081801.dzcldvkblxhakais@odonien.localdomain \
    --to=mail@vasilij.de \
    --cc=27779@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=esq@lawlist.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 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).