How to get full value of variable during edebug function tracing?

How to get full value of variable during edebug function tracing?

[Jean Louis]

How to get full value of variable during edebug function tracing?

I need to see full large value, not just the first few chars.

Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: How to get full value of variable during edebug function tracing?

[Stefan Monnier via Users list for the GNU Emacs text editor]

Jean Louis [2022-06-17 21:25:19] wrote:
> How to get full value of variable during edebug function tracing?

You can try to use the `inspect` package newly added to GNU ELPA.
Personally, in similar circumstances I tend to do the following:

    e (setq my-foo <THEVARIABLE>) RET

and then I go to my trusty `ielm` buffer to look at `my-foo` in all
its glory.


        Stefan

Re: How to get full value of variable during edebug function tracing?

[Lars Ingebrigtsen]

Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

> Personally, in similar circumstances I tend to do the following:
>
>     e (setq my-foo <THEVARIABLE>) RET
>
> and then I go to my trusty `ielm` buffer to look at `my-foo` in all
> its glory.

That's what I do, too, but it's kinda cumbersome, isn't it?  So I've now
made `C-u e' in edebug in Emacs 29 pop up a new buffer and pretty-print
the value.

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

Re: How to get full value of variable during edebug function tracing?

[Stefan Monnier via Users list for the GNU Emacs text editor]

Lars Ingebrigtsen [2022-06-18 00:19:07] wrote:
> Stefan Monnier via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org> writes:
>> Personally, in similar circumstances I tend to do the following:
>>
>>     e (setq my-foo <THEVARIABLE>) RET
>>
>> and then I go to my trusty `ielm` buffer to look at `my-foo` in all
>> its glory.
>
> That's what I do, too, but it's kinda cumbersome, isn't it?

Not really, because most of the time I don't just want to see the full
value but I want to actually use it, passing it to functions,
etc... which is a lot more convenient to do in IELM than in Edebug.


        Stefan

Re: How to get full value of variable during edebug function tracing?

[Jean Louis]

* Lars Ingebrigtsen <larsi@gnus.org> [2022-06-18 08:42]:
> That's what I do, too, but it's kinda cumbersome, isn't it?  So I've now
> made `C-u e' in edebug in Emacs 29 pop up a new buffer and pretty-print
> the value.

Thank you, that is good solution in sight. I have tried it.

I was always using C-x C-e to evaluate last expression, why not
include that also with C-u, becase that one automatically knows what
to evaluate.

While when I press only "e" I get the prompt "Edebug eval: " and then
I need to enter name of variable making it more work than C-x C-e



-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: How to get full value of variable during edebug function tracing?

[Lars Ingebrigtsen]

Jean Louis <bugs@gnu.support> writes:

> I was always using C-x C-e to evaluate last expression, why not
> include that also with C-u, becase that one automatically knows what
> to evaluate.

Hm...  Yes, `M-0 C-x C-e' maps to NO-TRUNCATE, but I guess we could have
`C-u C-x C-e' map to PP.

Now fixed in Emacs 29.

Re: How to get full value of variable during edebug function tracing?

[Arthur Miller]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Stefan Monnier via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org> writes:
>
>> Personally, in similar circumstances I tend to do the following:
>>
>>     e (setq my-foo <THEVARIABLE>) RET
>>
>> and then I go to my trusty `ielm` buffer to look at `my-foo` in all
>> its glory.
>
> That's what I do, too, but it's kinda cumbersome, isn't it?  So I've now
> made `C-u e' in edebug in Emacs 29 pop up a new buffer and pretty-print
> the value.

That sounds useful. Could you pop it up in a tooltip?

What about using mouse pointer as a "secondary cursor", if we would like to see
some previous value, so we don't have to move cursor around:

(defun pointer (x y)
  (save-excursion
    (goto-char (window-start))
    (forward-line x)
    (when (> (- (line-end-position) (line-beginning-position)) y)
      (move-to-column y)
      (1- (point)))))

(defun symbol-value-under-pointer ()
  (interactive)
  (save-excursion
    (let ((pointer (mouse-position)))
    (goto-char (pointer (cddr pointer) (cadr pointer)))
    (let ((sym (intern-soft (current-word))))
      (when sym
        (message "%S: %S" sym (symbol-value sym)))))))

Could that be useful to have on a C-u C-u e?

Re: How to get full value of variable during edebug function tracing?

[Lars Ingebrigtsen]

Arthur Miller <arthur.miller@live.com> writes:

> That sounds useful. Could you pop it up in a tooltip?

The main point of this is to allow the user to interact with the value,
which a tooltip doesn't help with.

> What about using mouse pointer as a "secondary cursor", if we would
> like to see some previous value, so we don't have to move cursor
> around:

[...]

> Could that be useful to have on a C-u C-u e?

It sounds like a quite specialised use case.

Re: How to get full value of variable during edebug function tracing?

[Arthur Miller]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Arthur Miller <arthur.miller@live.com> writes:
>
>> That sounds useful. Could you pop it up in a tooltip?
>
> The main point of this is to allow the user to interact with the value,
> which a tooltip doesn't help with.

One does not exclude the other?

Anyway, I just replied on what you wrote:

> That's what I do, too, but it's kinda cumbersome, isn't it?  So I've now
> made `C-u e' in edebug in Emacs 29 pop up a new buffer and pretty-print
> the value.

If you just pretty print it in a separate buffer, it is almost as good as in a
tooltip, but can be a bit distracting depending on how Emacs chose to split
buffer. Didn't have time to build and test your code, my build is like two weeks
old or so.

>> What about using mouse pointer as a "secondary cursor", if we would
>> like to see some previous value, so we don't have to move cursor
>> around:
>
> [...]
>
>> Could that be useful to have on a C-u C-u e?
>
> It sounds like a quite specialised use case.

Examining the value of a variable while debugging?

For me it is a normal thing. I press 'e' and then type the name of a variable,
or I sometimes move curser at the end of var/expression and press C-x C-e. Would
be nice if edebug instrumented code with help-echo to display values, or even
the doc together with the value, similar as in help buffer but in a
tooltip. That way we could just move the pointer over symbols and quickly see
values/docs, instead of pressing e and typing.