From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Rant on ... Date: Thu, 17 Nov 2016 21:54:08 +0100 Message-ID: References: <20161117204729.GA3461@acm.fritz.box> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1479416071 9151 195.159.176.226 (17 Nov 2016 20:54:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 17 Nov 2016 20:54:31 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 17 21:54:26 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c7ThR-0000vP-H7 for ged-emacs-devel@m.gmane.org; Thu, 17 Nov 2016 21:54:25 +0100 Original-Received: from localhost ([::1]:33209 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c7ThT-0006NW-7X for ged-emacs-devel@m.gmane.org; Thu, 17 Nov 2016 15:54:27 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44870) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c7ThN-0006NO-JQ for emacs-devel@gnu.org; Thu, 17 Nov 2016 15:54:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c7ThJ-0002aW-NX for emacs-devel@gnu.org; Thu, 17 Nov 2016 15:54:21 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:41832) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c7ThJ-0002aM-Ha for emacs-devel@gnu.org; Thu, 17 Nov 2016 15:54:17 -0500 Original-Received: from cm-84.215.1.64.getinternet.no ([84.215.1.64] helo=stories) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1c7ThA-0004UA-Vq; Thu, 17 Nov 2016 21:54:13 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEWB3LYDBQICAwGLTD/+ Pl0ZEgzg9U3ZO1F/soICBAEBAgD+/+H+/+T+/9aE43hyfP9HAAACHklEQVQ4jXXSMWvbQBQA4Aul 0CFDn4Voz9DBMqXRbcFpweDRPyBu7BQFZTBG+gWGztk6ZDkJQ05bBB5yW/5BQRgC1RK6KpMRZNJv 6N3pTqZGfoN54tN7z/dOCOwiryMD/LFJLQQwap4Yva3TR3iPhrR5DScmvwEflWyle2XRPdUlE7hF r0B9DazvparkCVY5qiZM12dJP3Doscg22BJQYlpoiMOuey5H0E8Cttjxdas4HJJ1IUeMBFQeu9PD 43CRpNdiBBxLKKNeUVdYYXjl2PkG7FzCtst90yoMuOsfyeMIqL7zuwZCL4mHrl9Dye+LBoKEq81I 2CaqVw1hh/NVXoPodbKDOSGxgbpXxlYSFkytQsE2kWfMsILQU2tVUF3J/6VhgRm9NlAS0StjtoSA Rcw2sCXENxVzZj/QkQbR68QM99ilRy0DJV8XGjD9FoC4wRrEGUd1q4X8ncC5BrmvDMvhcxA7DsA2 UJL1XwWn+DKUJQZeu+6A2YOvswnMZheDHVRDThkDBhiDigZKkrrRAxNB/4eqyyMXQFThPRjyNH55 8diPnzLGaNaEgPw3wHKsAkWc85Q7Ucq5a4kv3h5rEDcpIyWCrfwZLAMR4Q5JHafndMSV3sDUAEK/ VCD0Fsd/JnC2AxNvwHpqRuzBphmxB0fwoR1OmxF7AL1lC7yDXu/zuBUc50srdHg6bQWxleUBWI8P QL8dHD49UJGe7eAfqov9awFnC5YAAAAASUVORK5CYII= In-Reply-To: <20161117204729.GA3461@acm.fritz.box> (Alan Mackenzie's message of "Thu, 17 Nov 2016 20:47:29 +0000") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:209458 Archived-At: Alan Mackenzie 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