all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Eli Zaretskii" <eliz@gnu.org>,
	"Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: A tip: how to display longer function names in profiler-report
Date: Tue, 22 Dec 2020 12:22:04 +0000	[thread overview]
Message-ID: <X+Hk7FoCfYs1wAeS@ACM> (raw)
In-Reply-To: <63c6196a-319b-f436-4f8f-14b6719f90de@gmail.com>

Hello, Eli and Clément.

On Mon, Dec 21, 2020 at 16:34:10 -0500, Clément Pit-Claudel wrote:
> On 12/21/20 4:24 PM, Alan Mackenzie wrote:
> > Something like, very roughly: ....

> Precisely :) Love it.  And we can even remove the padding spaces from the last column.

The padding has now gone.  Function names are now never truncated by the
profiler.  The only truncation that can happen is when the user's window
is too narrow, something easily remedied.

This change (putting the usage figures on the left, and the function
names on the right) seems such a clear improvement, that I've taken the
liberty of just committing it (including NEWS item and amendments to
debugging.texi).  The commit hash is 9920929e7b.

In the event that there are any objections, it would be an easy commit
to reverse.

-- 
Alan Mackenzie (Nuremberg, Germany).



      parent reply	other threads:[~2020-12-22 12:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 16:32 A tip: how to display longer function names in profiler-report Alan Mackenzie
2020-12-21 17:15 ` Eli Zaretskii
2020-12-21 17:34   ` Alan Mackenzie
2020-12-21 18:12     ` Eli Zaretskii
2020-12-21 18:52       ` Alan Mackenzie
2020-12-21 17:52 ` Stefan Kangas
2020-12-21 18:14   ` Alan Mackenzie
2020-12-21 20:24 ` Clément Pit-Claudel
2020-12-21 21:24   ` Alan Mackenzie
2020-12-21 21:34     ` Clément Pit-Claudel
2020-12-21 22:09       ` Alan Mackenzie
2020-12-22 12:22       ` Alan Mackenzie [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X+Hk7FoCfYs1wAeS@ACM \
    --to=acm@muc.de \
    --cc=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.