From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.emacs.semantic Subject: Re: [cedet-semantic] scrolling while editing RFC Date: Mon, 08 Jul 2013 21:09:42 +0300 Message-ID: <83fvvox6s9.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1373307041 16250 80.91.229.3 (8 Jul 2013 18:10:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Jul 2013 18:10:41 +0000 (UTC) Cc: gundaetiapo@gmail.com, eric@siege-engine.com, cedet-semantic@lists.sourceforge.net, emacs-devel@gnu.org To: Dave Milter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 08 20:10:41 2013 Return-path: Envelope-to: ged-emacs-devel@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 1UwFtY-0007Ie-Gk for ged-emacs-devel@m.gmane.org; Mon, 08 Jul 2013 20:10:40 +0200 Original-Received: from localhost ([::1]:60504 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwFtY-0001Im-0W for ged-emacs-devel@m.gmane.org; Mon, 08 Jul 2013 14:10:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwFtS-0001G6-Vn for emacs-devel@gnu.org; Mon, 08 Jul 2013 14:10:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwFtQ-0001nZ-7U for emacs-devel@gnu.org; Mon, 08 Jul 2013 14:10:34 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:41936) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwFtQ-0001nD-06 for emacs-devel@gnu.org; Mon, 08 Jul 2013 14:10:32 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MPM00300QFB8100@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Mon, 08 Jul 2013 21:09:56 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MPM003BOQGK4I50@a-mtaout20.012.net.il>; Mon, 08 Jul 2013 21:09:56 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:161733 gmane.emacs.semantic:3357 Archived-At: > Date: Mon, 8 Jul 2013 15:55:22 +0400 > From: Dave Milter > Cc: semantic cedet , > "Eric M. Ludlam" > > I met the same problem. > It is fun to see what happens for example when I use 'C-x 2' to work with > two buffers. > While I editing one buffer, another buffer scroll forward and backward, it > looks like ghost work on my machine with me. > > May be experienced emacs developer suggest how track down this problem? > > I see it like for example exists two function: > the-most-internal-scroll-buffer-function > the-most-internal-move-cursor-function > > I put breakpoints on them with condition that on top of call stack is > "timer event", not "key event". And then see who is ghost. > > Anybody from top emacs coders know is it possible? > Are there > the-most-internal-scroll-buffer-function > the-most-internal-move-cursor-function > and what are their names, What you see is not some scroll-buffer function, it is redisplay trying to keep point in view. This part of Emacs is written in C, so you'd need to set breakpoints in GDB. But there are too many places that could be involved in these unwarranted scrolls; setting breakpoints on all of them will produce gobs of clutter. The best I can suggest is this: . build Emacs with -DGLYPH_DEBUG=1 . run it as you do usually, and after setting up the stage for these scrolls, type "M-x trace-redisplay RET" . watch the screen where Emacs's stderr goes, and try to identify the traces emitted when those "ghost" scrolls happen . post those traces here Armed with the above, I might be able to tell you where to set breakpoints in GDB so that you catch the Lisp code which triggers these scrolls. That said, I'm not sure what you expect to find, since Eric already told you where this is done, and even said this is on purpose: > The place to start is in cedet/semantic/idle.el. The outward call to > the various work functions purposely does not use 'save-excursion' so > tools like completion can move things around for you. Or maybe I don't understand what he meant.