From: Glenn Morris <rgm@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 32414@debbugs.gnu.org
Subject: bug#32414: 27.0.50; backtrace.el fails to require cl-print
Date: Fri, 10 Aug 2018 18:55:31 -0400 [thread overview]
Message-ID: <a9k1ox6dcs.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAOqdjBccOwrhbjNyFo+6OchW7JEoz7CxX-deOfqEf813gZsh6w@mail.gmail.com> (Pip Cet's message of "Fri, 10 Aug 2018 15:37:18 +0000")
Pip Cet wrote:
> (throw 'a (make-string 4096 ?a))
>
> in the *scratch* buffer. I expected a backtrace, but got an error
> message instead:
Works for me.
> backtrace--print-to-string: Symbol's function definition is void:
> cl-print-to-string-with-limit
cl-print-to-string-with-limit is autoloaded.
Perhaps you should "make bootstrap".
next prev parent reply other threads:[~2018-08-10 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 15:37 bug#32414: 27.0.50; backtrace.el fails to require cl-print Pip Cet
2018-08-10 22:55 ` Glenn Morris [this message]
2018-08-11 7:38 ` Pip Cet
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=a9k1ox6dcs.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=32414@debbugs.gnu.org \
--cc=pipcet@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).