GNU bug report logs -
#8789
23.3; debug backtrace buffer changes window on step-through
Previous Next
Reported by: Pete Beardmore <pete.beardmore <at> msn.com>
Date: Thu, 2 Jun 2011 17:28:02 UTC
Severity: normal
Found in version 23.3
Done: martin rudalics <rudalics <at> gmx.at>
Bug is archived. No further changes may be made.
Full log
Message #164 received at 8789 <at> debbugs.gnu.org (full text, mbox):
> But what if you want to M-x debug-on-entry
> find-file-name-handler or any other function called by
> `file-remote-p' (or your mode-line version)?
Yes of course, agreed. If you explicitly access the debugger intentionally for
`find-file-name-handler', `if', or `funcall' (the 3 fns called by
`file-remote-p'), then you will run into the same problem.
The proposed fix would nevertheless be a big improvement. And you will not run
into such a problem if you debug other code that calls any of those three fns or
`file-remote-p'. That was my point.
I think you are perhaps exaggerating the problems, _in practice_, that such a
simple fix might not handle, and you are perhaps downplaying the real problem
already caused by the regression.
IOW, while Someone (TM) works on an elegant, general fix, implementing a simple
fix that does a pretty good job now is better than doing nothing now and until
that general fix is available.
This bug report was last modified 12 years and 223 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.