From: Mario Lang <mlang@delysid.org>
Subject: Re: Something smells rotten in redisplay
Date: Wed, 24 Jul 2002 18:44:29 +0200 [thread overview]
Message-ID: <87eldtdqj6.fsf@lexx.delysid.org> (raw)
In-Reply-To: <20020722105950.4693.LEKTU@terra.es> (Juanma Barranquero's message of "Mon, 22 Jul 2002 11:08:29 +0200")
Juanma Barranquero <lektu@terra.es> writes:
[...]
> Debugger entered--Lisp error: (quit)
> recursive-edit()
> byte-code("Æ\b!^[,HG^[(B ^[,HH ^[(B!^[,H\^[(Bn^[,C?
Seeing this reminds me of a question I have: Is that
backtrace representation of byte-code("...") really necessary that way.
The actual string is useless in most cases, you can't really copy
that and use it for something.
COuldn't we either elide such byte-code strings, or replace them with
a human readable version of a byte-code string?
--
CYa,
Mario
prev parent reply other threads:[~2002-07-24 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 9:08 Something smells rotten in redisplay Juanma Barranquero
2002-07-24 16:44 ` Mario Lang [this message]
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=87eldtdqj6.fsf@lexx.delysid.org \
--to=mlang@delysid.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 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).