unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Rant on ...
Date: Thu, 17 Nov 2016 21:25:04 -0500	[thread overview]
Message-ID: <ed606138-80a9-8c94-c2ee-11b03aeb3f30@gmail.com> (raw)
In-Reply-To: <m3vavlbv07.fsf@gnus.org>


[-- Attachment #1.1: Type: text/plain, Size: 737 bytes --]

On 2016-11-17 17:29, Lars Ingebrigtsen wrote:
> Drew Adams <drew.adams@oracle.com> writes:
> 
>> > 2. And another key to toggle expansion of `...' everywhere.
> Yes, that would be very nice.  And a command to expand the `...' under
> point.  If we had those commands, I think we'd cover most of the
> complaints and confusion tied to the *print-le* variables.

Would this cover performance issues, too? When a large string (like buffer-string) is passed down a bunch of functions, printing a stack trace can take in the tens of seconds.  A really awesome implementation would abbreviate this to a button that would print the string once clicked (instead of just having an 'invisible region of pre-printed text) :)

Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-11-18  2:25 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
2016-11-19  0:10               ` Michael Heerdegen
2016-11-18  2:25         ` Clément Pit--Claudel [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=ed606138-80a9-8c94-c2ee-11b03aeb3f30@gmail.com \
    --to=clement.pit@gmail.com \
    --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).