From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#8789: 23.3; debug backtrace buffer changes window on step-through Date: Thu, 20 Sep 2012 22:17:36 +0200 Message-ID: <87vcf8fnz3.fsf@web.de> References: <4F3CB843.6030401@gmx.at> <4F3D41DD.6080603@gmx.at> <877gzmqwcf.fsf@web.de> <504B4940.9000809@gmx.at> <86wqzznwzv.fsf@web.de> <9BABA419184241F5A7246DC5D9A9EF81@us.oracle.com> <5057A4A3.4010100@gmx.at> <4617F483F2CC446D980DF7194E06BB3A@us.oracle.com> <50581E7F.3040108@gmx.at> <1C1E224E1D674670BEE043B4A35A271F@us.oracle.com> <5059FC9C.8020702@gmx.at> <2D8C133406A54B26AD253EC7EE52C666@us.oracle.com> <505B1F26.20209@gmx.at> <87ehlwzklr.fsf@web.de> <505B51AD.2080908@gmx.at> <91FFA03F2A7341A09E280DD2BCC4A428@us.oracle.com> <83392czgvc.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348172137 30253 80.91.229.3 (20 Sep 2012 20:15:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Sep 2012 20:15:37 +0000 (UTC) To: 8789@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Sep 20 22:15:41 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TEn9t-0005Uc-W0 for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Sep 2012 22:15:38 +0200 Original-Received: from localhost ([::1]:51137 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEn9p-0000MR-I5 for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Sep 2012 16:15:33 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42992) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEn9m-0000LL-Bu for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:15:31 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEn9l-0006At-BC for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:15:30 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:36109) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEn9l-0006Ap-7v for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:15:29 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TEnBF-0002pm-PS for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:17:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 20 Sep 2012 20:17:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 8789 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.134817222010884 (code B ref -1); Thu, 20 Sep 2012 20:17:01 +0000 Original-Received: (at submit) by debbugs.gnu.org; 20 Sep 2012 20:17:00 +0000 Original-Received: from localhost ([127.0.0.1]:45655 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TEnBD-0002pU-MX for submit@debbugs.gnu.org; Thu, 20 Sep 2012 16:16:59 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43570) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TEnAx-0002oy-Ot for submit@debbugs.gnu.org; Thu, 20 Sep 2012 16:16:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEn9Q-0005m0-Mk for submit@debbugs.gnu.org; Thu, 20 Sep 2012 16:15:10 -0400 Original-Received: from lists.gnu.org ([208.118.235.17]:60561) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEn9Q-0005ls-Jf for submit@debbugs.gnu.org; Thu, 20 Sep 2012 16:15:08 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42945) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEn9P-0000Ba-EN for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:15:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEn9O-0005gh-E9 for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:15:07 -0400 Original-Received: from mout.web.de ([212.227.17.11]:63804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEn9O-0005e2-5a for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 16:15:06 -0400 Original-Received: from snow.dragon ([89.204.130.212]) by smtp.web.de (mrweb101) with ESMTPSA (Nemesis) id 0MYf78-1T0vNK2m38-00VpkB; Thu, 20 Sep 2012 22:15:05 +0200 In-Reply-To: <83392czgvc.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Sep 2012 21:30:47 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-Provags-ID: V02:K0:sMEcXYecla/IYMvoLvjvzuZHw6hsupILH73GzsrXgGi 1QNkUmy/iQ0vcejOl5Lf45iw607oaSMuKJF4fbKEzRTAt3kxpL SAk3pAgsjleJ/l3j86JU8GCbFquvxo2MOeyXyiGT148YwRHruH pfIm12z0/9RKXy1kH4Ghqj40Jf4oljBuf6CDb8UuPWa8pAioM3 sm7fQM1b2nnKTRHm8+7Ab5MH4FmW2Mo5RJ9PDkZbuU= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:64655 Archived-At: Eli Zaretskii writes: > > > So the solution is probably to never enable `debug-on-entry' for > > > functions that run through the mode-line mechanism. > > > > That does not sound like the solution to me. I don't see this as critical as Drew, IMHO this is not really a bug. It is consistent behavior, and sometimes it can useful to be able to enter the debugger from code run by redisplaying. But OTOH, invoking the debugger in such situations can (a) be surprising, and even a experienced user may take some time to see what's happening. And, b), it is not what you want most of the time. So, what would be cool is a user-option for that behavior. The default could be to not invoke the debugger from redisplay code. A question would be how to handle similar stuff, like menu calculation, things in pre|post-command-hook, code run by timers, etc. I mean all the stuff that is not run directly while processing a user command. If such an option could easily be implemented, that would be fine. But if it would be too much work, I also could live without it. I can use `debug' to invoke the debugger directly, which prevents such surprises. Michael.