all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How do you inspect variables when debugging with EDebug?
Date: Fri, 01 Apr 2022 10:20:08 -0400	[thread overview]
Message-ID: <jwvbkxkq4hn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: trinity-fd9a3449-c8d5-4f19-b964-4e7c0ec6c36c-1648792786054@3c-app-mailcom-lxa04

I think it's worth pointing out that while EDebug is quite nice (and
was great when it came out), it hasn't seen much development on the UI
side over the last 20 years.

So yes there are many things that could be added to improve it.
This thread already mentioned:
- A display of local vars.
- A way to get the value of the variable under point.
I would add to that:
- A way to "go back".  Probably not true reverse execution, but at
  least a way to move back&forth in time to see which values were returned
  where (this just requires keeping around the sequence of return values
  along with the corresponding buffer position).
- A way to ask Edebug to "finish the current loop" or more generally to
  run without stopping until we exit the currently surrounding sexp.


        Stefan




  parent reply	other threads:[~2022-04-01 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  5:59 How do you inspect variables when debugging with EDebug? John Kliny
2022-04-01  6:42 ` Tassilo Horn
2022-04-01  7:22   ` John Kliny
2022-04-01  7:25 ` Michael Albinus
2022-04-01  7:40   ` John Kliny
2022-04-01  7:56     ` Michael Albinus
2022-04-01 14:20 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-01 15:04 John Kliny
2022-04-01 20:17 ` Stefan Monnier via Users list for the GNU Emacs text editor

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=jwvbkxkq4hn.fsf-monnier+emacs@gnu.org \
    --to=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.