unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#1428: backtrace from edebug does not have links
@ 2008-11-25 15:59 Dan Nicolaescu
  2012-02-13 23:44 ` Michael Heerdegen
  0 siblings, 1 reply; 5+ messages in thread
From: Dan Nicolaescu @ 2008-11-25 15:59 UTC (permalink / raw)
  To: bug-gnu-emacs


In edebug when using d to show the backtrace, the *Backtrace* buffer
does not have links to the functions that you get in the *Backtrace*
buffer when using debug-on-error.  
It would be nice if the links would work for the edebug case too.







^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#1428: backtrace from edebug does not have links
  2008-11-25 15:59 bug#1428: backtrace from edebug does not have links Dan Nicolaescu
@ 2012-02-13 23:44 ` Michael Heerdegen
  2012-03-21 18:14   ` Stefan Monnier
  2018-08-03 18:36   ` Gemini Lasswell
  0 siblings, 2 replies; 5+ messages in thread
From: Michael Heerdegen @ 2012-02-13 23:44 UTC (permalink / raw)
  To: Dan Nicolaescu; +Cc: 1428

Dan Nicolaescu <dann@ics.uci.edu> writes:

> In edebug when using d to show the backtrace, the *Backtrace* buffer
> does not have links to the functions that you get in the *Backtrace*
> buffer when using debug-on-error.  
> It would be nice if the links would work for the edebug case too.

Maybe nobody implements that because `edebug-backtrace' is planned to be
rewritten so that it gets better than "Better than nothing..." (see
docstring)?

However, until that happens, maybe this problem should be solved.


Can't we just append some code like this:

  (goto-char (point-min))
  (while (progn
  	 (goto-char (+ (point) 2))
           (skip-syntax-forward "^w_")
           (not (eobp)))
    (let* ((beg (point))
           (end (progn (skip-syntax-forward "w_") (point)))
           (sym (intern-soft (buffer-substring-no-properties
                              beg end)))
           (file (and sym (symbol-file sym 'defun))))
      (when file
        (goto-char beg)
        ;; help-xref-button needs to operate on something matched
        ;; by a regexp, so set that up for it.
        (re-search-forward "\\(\\sw\\|\\s_\\)+")
        (help-xref-button 0 'help-function-def sym file)))
    (forward-line 1))

to `edebug-backtrace' (the code is from `debugger-make-xrefs')?


Thanks,

Michael.





^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#1428: backtrace from edebug does not have links
  2012-02-13 23:44 ` Michael Heerdegen
@ 2012-03-21 18:14   ` Stefan Monnier
  2018-08-03 18:36   ` Gemini Lasswell
  1 sibling, 0 replies; 5+ messages in thread
From: Stefan Monnier @ 2012-03-21 18:14 UTC (permalink / raw)
  To: michael_heerdegen; +Cc: Dan Nicolaescu, 1428

>> In edebug when using d to show the backtrace, the *Backtrace* buffer
>> does not have links to the functions that you get in the *Backtrace*
>> buffer when using debug-on-error.  
>> It would be nice if the links would work for the edebug case too.

> Maybe nobody implements that because `edebug-backtrace' is planned to be
> rewritten so that it gets better than "Better than nothing..." (see
> docstring)?
> However, until that happens, maybe this problem should be solved.

(defalias 'edebug-debug 'debug) might be a good replacement in the mean time.


        Stefan





^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#1428: backtrace from edebug does not have links
  2012-02-13 23:44 ` Michael Heerdegen
  2012-03-21 18:14   ` Stefan Monnier
@ 2018-08-03 18:36   ` Gemini Lasswell
  2018-08-04  1:56     ` Michael Heerdegen
  1 sibling, 1 reply; 5+ messages in thread
From: Gemini Lasswell @ 2018-08-03 18:36 UTC (permalink / raw)
  To: Michael Heerdegen; +Cc: Dan Nicolaescu, 1428, 1428

tags 1428 fixed
close 1428 27.1
thanks

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
>> In edebug when using d to show the backtrace, the *Backtrace* buffer
>> does not have links to the functions that you get in the *Backtrace*
>> buffer when using debug-on-error.  
>> It would be nice if the links would work for the edebug case too.
>
> Maybe nobody implements that because `edebug-backtrace' is planned to be
> rewritten so that it gets better than "Better than nothing..." (see
> docstring)?

I've just pushed to Emacs master that long-anticipated rewrite of
edebug-backtrace, which includes making links to functions.

Gemini





^ permalink raw reply	[flat|nested] 5+ messages in thread

* bug#1428: backtrace from edebug does not have links
  2018-08-03 18:36   ` Gemini Lasswell
@ 2018-08-04  1:56     ` Michael Heerdegen
  0 siblings, 0 replies; 5+ messages in thread
From: Michael Heerdegen @ 2018-08-04  1:56 UTC (permalink / raw)
  To: Gemini Lasswell; +Cc: Dan Nicolaescu, 1428, 1428

Gemini Lasswell <gazally@runbox.com> writes:

> I've just pushed to Emacs master that long-anticipated rewrite of
> edebug-backtrace, which includes making links to functions.

Yet I only read the documentation additions of your merge, but that all
sounds very nice, thank you!


Michael.





^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-08-04  1:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-25 15:59 bug#1428: backtrace from edebug does not have links Dan Nicolaescu
2012-02-13 23:44 ` Michael Heerdegen
2012-03-21 18:14   ` Stefan Monnier
2018-08-03 18:36   ` Gemini Lasswell
2018-08-04  1:56     ` Michael Heerdegen

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).