[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Backtrace mode
From: |
Clément Pit-Claudel |
Subject: |
Re: Backtrace mode |
Date: |
Wed, 1 Aug 2018 17:07:41 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
On 2018-07-27 16:13, Gemini Lasswell wrote:
> - C functions in backtraces now get links to their source code. Links
> are also created for the reading position of 'eval-buffer' and
> 'eval-region'.
A small potential bug: if I install ido-completin-read+ emacs -Q, then running
M-: (debug) produces a backtrace in which call-interactively isn't highlighted:
- Without ido-cr+ (all lines have a hyperlink to their sources):
Debugger entered: nil
eval((debug) nil)
eval-expression((debug) nil nil 127)
funcall-interactively(eval-expression (debug) nil nil 127)
call-interactively(eval-expression nil nil)
command-execute(eval-expression)
- With ido-cr+ (lines marked with ‘!’ don't have hyperlinks):
Debugger entered: nil
eval((debug) nil)
eval-expression((debug) nil nil 127)
funcall-interactively(eval-expression (debug) nil nil 127)
! #<subr call-interactively>(eval-expression nil nil)
apply(#<subr call-interactively> eval-expression (nil nil))
address@hidden(#<subr call-interactively> eval-expression nil nil)
apply(address@hidden #<subr call-interactively> (eval-expression nil nil))
! call-interactively(eval-expression nil nil)
command-execute(eval-expression)
I imagine this is due to advice?
:around advice: address@hidden
Cheers,
Clément.