unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Rant on ...
Date: Thu, 17 Nov 2016 21:54:08 +0100	[thread overview]
Message-ID: <m3a8cxddzj.fsf@gnus.org> (raw)
In-Reply-To: <20161117204729.GA3461@acm.fritz.box> (Alan Mackenzie's message of "Thu, 17 Nov 2016 20:47:29 +0000")

Alan Mackenzie <acm@muc.de> writes:

> Are there really hackers who prefer to see only some of the relevant
> debugging information?

I prefer the truncated lines in the debugging buffer.  It allows me to
scan the stack trace faster.  I can expand the lines I'm interested in
after finding them.

> If anybody knows offhand what settings I need to make, please tell me.

I think there's something binding print-length somewhere annoying, but I
forget the details.  Or was it eval-expression-print-length?

> Would anybody object to my getting rid of this obfuscation in Emacs, and
> setting the appropriate defaults (whatever they are) not arbitrarily to
> truncate backtraces and other info users have requested?

Data forms can be arbitrarily long.  Not truncating them when printing
them can result in printing an expression taking a long time.  (I've
experience something like half-minute pauses when dealing with extreme
data structures.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2016-11-17 20:54 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 [this message]
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
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=m3a8cxddzj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.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).