all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: eller.helmut@gmail.com, 18558@debbugs.gnu.org
Subject: bug#18558: 24.4.50; Debugger slow with long strings
Date: Fri, 19 Feb 2016 11:03:41 +0200	[thread overview]
Message-ID: <83povtrs0i.fsf@gnu.org> (raw)
In-Reply-To: <87h9h5jdnm.fsf@mbork.pl> (message from Marcin Borkowski on Fri,  19 Feb 2016 09:41:01 +0100)

> From: Marcin Borkowski <mbork@mbork.pl>
> Date: Fri, 19 Feb 2016 09:41:01 +0100
> Cc: 18558@debbugs.gnu.org
> 
> On 2014-09-25, at 12:16, Helmut Eller <eller.helmut@gmail.com> wrote:
> 
> > Moving the cursor in the debugger window is very slow in the following
> > example:
> >
> > shell> cat test.el
> > (progn
> >   (defun foo (n string)
> >     (cond ((= n 0) (debug))
> >           (t (foo (1- n) string))))
> >   (foo 30 (make-string 500000 ?\\)))
> >
> > shell> emacs -Q -nw -l test.el
> >
> > Now move the cursor around to see the slowness.
> >
> > Maybe the debugger should truncate long strings as it does with long
> > lists.
> 
> Confirmed on GNU Emacs 25.1.50.2 (commit 4ccd268).
> 
> I would guess that the problem is not in long string /per se/, but with
> lon lines in the *Backtrace* buffer, i.e. probably something connected
> with the display engine.  I guess this bug should either be closed or
> merged with some other one (one of the other ones, perhaps) dealing with
> efficiency problems with long lines.

Yes, please merge it.

Thanks.





  reply	other threads:[~2016-02-19  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  9:16 bug#18558: 24.4.50; Debugger slow with long strings Helmut Eller
2016-02-19  8:41 ` Marcin Borkowski
2016-02-19  9:03   ` Eli Zaretskii [this message]
2016-02-19  9:15   ` Helmut Eller

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=83povtrs0i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18558@debbugs.gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=mbork@mbork.pl \
    /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.