unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 1428@emacsbugs.donarmstrong.com
Subject: bug#1428: backtrace from edebug does not have links
Date: Tue, 14 Feb 2012 00:44:55 +0100	[thread overview]
Message-ID: <87k43ql2mg.fsf@web.de> (raw)
In-Reply-To: <200811251559.mAPFxWQI016550@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Tue, 25 Nov 2008 07:59:32 -0800 (PST)")

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.





  reply	other threads:[~2012-02-13 23:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 15:59 bug#1428: backtrace from edebug does not have links Dan Nicolaescu
2012-02-13 23:44 ` Michael Heerdegen [this message]
2012-03-21 18:14   ` Stefan Monnier
2018-08-03 18:36   ` Gemini Lasswell
2018-08-04  1:56     ` Michael Heerdegen

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=87k43ql2mg.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=1428@emacsbugs.donarmstrong.com \
    --cc=dann@ics.uci.edu \
    /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).