From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Lars Ingebrigtsen <larsi@gnus.org>,
Emacs Development <emacs-devel@gnu.org>
Subject: RE: Rant on ...
Date: Thu, 17 Nov 2016 19:50:56 -0800 (PST) [thread overview]
Message-ID: <ce478015-828a-488c-ae1d-336528291b33@default> (raw)
In-Reply-To: <CAM-tV-_o67HBPHSPjfdY-y_JSYTf7cBcdG_JuUA8BE4B0_QgFA@mail.gmail.com>
> > Getting rid of the bytecode is important for communicating by
> > copying/pasting backtrace text. You cannot copy/paste it all
> > when some of it is bytecode - you only get the first part of it
> > - up to some binary character - and the rest is truncated away.
>
> I've been thinking we could keep the bytecode, but just print it
> with the non-text characters escaped.
That would be OK too. But better might be to (1) remove/elide the
stuff that is meaningless and (2) keep the embedded readable chars.
There is little sense, I think, in escaping junk that is unreadable,
just to (presumably) avoid any loss of info.
For me, it's just about communicating a human-readable backtrace,
but perhaps (?) there is also a need, for some people, to be able
to communicate the whole, real deal, and enable someone else to
restore the escaped byte code from it. I don't need that.
> I'll reopen and follow up on the bug thread tomorrow.
Good to hear. Thx.
next prev parent reply other threads:[~2016-11-18 3:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 20:47 Rant on Alan Mackenzie
2016-11-17 20:54 ` Lars Ingebrigtsen
2016-11-17 21:04 ` Clément Pit--Claudel
2016-11-17 21:09 ` Lars Ingebrigtsen
2016-11-17 21:20 ` Clément Pit--Claudel
2016-11-17 21:31 ` Drew Adams
2016-11-17 21:33 ` Drew Adams
2016-11-17 22:29 ` Lars Ingebrigtsen
2016-11-18 2:17 ` Michael Heerdegen
2016-11-18 2:56 ` Drew Adams
2016-11-18 3:27 ` Noam Postavsky
2016-11-18 3:50 ` Drew Adams [this message]
2016-11-19 0:10 ` Michael Heerdegen
2016-11-18 2:25 ` Clément Pit--Claudel
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=ce478015-828a-488c-ae1d-336528291b33@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
/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).