From: Noam Postavsky <npostavs@gmail.com>
To: Jonathan Kyle Mitchell <kyle@jonathanmitchell.org>
Cc: 31326@debbugs.gnu.org
Subject: bug#31326: 27.0.50; eshell/clear exceeds max-lisp-eval-depth
Date: Tue, 01 May 2018 08:21:20 -0400 [thread overview]
Message-ID: <87tvrro9bz.fsf@gmail.com> (raw)
In-Reply-To: <4d356aa0-7783-e22f-b943-0a3f70119b94@jonathanmitchell.org> (Jonathan Kyle Mitchell's message of "Tue, 1 May 2018 01:08:20 -0500")
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
retitle 31326 eshell/clear goes into infinite loop with eshell-smart-initialize
found 31326 25
tags 31326 + confirmed
quit
Jonathan Kyle Mitchell <kyle@jonathanmitchell.org> writes:
> The eshell/clear elisp function seems to go into an infinite loop before
> ending in an error when the eshell smart display functionality is
> enabled in eshell-mode-hook. Several "Error during redisplay" messages
> are printed to *Messages* buffer.
>
> Steps to reproduce:
> 1. ./emacs -Q
> 2. In the scratch buffer evaluate:
> (require 'em-smart)
> (add-hook 'eshell-mode-hook 'eshell-smart-initialize)
> 4. M-x eshell
> 5. type "clear" in eshell and press RET
This reproduces back to 25.3; it doesn't happen in 24.5, but "clear"
seems to do nothing in that version. I caught a backtrace (attached)
with M-x toggle-debug-on-quit and quickly hitting C-g.
[-- Attachment #2: backtrace from C-g --]
[-- Type: application/gzip, Size: 1012 bytes --]
next prev parent reply other threads:[~2018-05-01 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 6:08 bug#31326: 27.0.50; eshell/clear exceeds max-lisp-eval-depth Jonathan Kyle Mitchell
2018-05-01 12:21 ` Noam Postavsky [this message]
2018-05-03 4:09 ` Jonathan Kyle Mitchell
2018-05-04 10:42 ` Noam Postavsky
2018-05-04 18:07 ` Jonathan Kyle Mitchell
2018-05-04 20:16 ` Eli Zaretskii
2018-05-05 0:53 ` Jonathan Kyle Mitchell
2018-05-05 6:40 ` Eli Zaretskii
2018-07-11 1:30 ` Noam Postavsky
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=87tvrro9bz.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31326@debbugs.gnu.org \
--cc=kyle@jonathanmitchell.org \
/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.