From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Berman Newsgroups: gmane.emacs.bugs Subject: bug#14838: 24.3.50; repeating next-line or previous-line is broken Date: Thu, 11 Jul 2013 22:04:07 +0200 Message-ID: <87vc4gyibs.fsf@rosalinde.fritz.box> References: <87ip0ije8n.fsf@gmx.net> <83bo69vmev.fsf@gnu.org> <8761whxvjc.fsf@rosalinde.fritz.box> <838v1dulyl.fsf@gnu.org> <87zjttx741.fsf@rosalinde.fritz.box> <83ppuo6h73.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1373573121 27438 80.91.229.3 (11 Jul 2013 20:05:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 11 Jul 2013 20:05:21 +0000 (UTC) Cc: 14838@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Jul 11 22:05:21 2013 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 1UxN76-0002Jt-J4 for geb-bug-gnu-emacs@m.gmane.org; Thu, 11 Jul 2013 22:05:16 +0200 Original-Received: from localhost ([::1]:54276 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UxN76-0003g3-4s for geb-bug-gnu-emacs@m.gmane.org; Thu, 11 Jul 2013 16:05:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UxN6w-0003di-II for bug-gnu-emacs@gnu.org; Thu, 11 Jul 2013 16:05:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UxN6t-0006fz-DI for bug-gnu-emacs@gnu.org; Thu, 11 Jul 2013 16:05:06 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:54191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UxN6t-0006eO-93 for bug-gnu-emacs@gnu.org; Thu, 11 Jul 2013 16:05:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1UxN6r-00026B-PO for bug-gnu-emacs@gnu.org; Thu, 11 Jul 2013 16:05:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stephen Berman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 11 Jul 2013 20:05:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14838 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 14838-submit@debbugs.gnu.org id=B14838.13735730637986 (code B ref 14838); Thu, 11 Jul 2013 20:05:01 +0000 Original-Received: (at 14838) by debbugs.gnu.org; 11 Jul 2013 20:04:23 +0000 Original-Received: from localhost ([127.0.0.1]:48507 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1UxN6F-00024k-4t for submit@debbugs.gnu.org; Thu, 11 Jul 2013 16:04:23 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:55460) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1UxN6B-00024K-Bc for 14838@debbugs.gnu.org; Thu, 11 Jul 2013 16:04:20 -0400 Original-Received: from rosalinde.fritz.box ([89.245.121.253]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M5IdH-1TyG1P2Opr-00zaaZ; Thu, 11 Jul 2013 22:04:09 +0200 In-Reply-To: <83ppuo6h73.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 Jul 2013 22:16:00 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-Provags-ID: V03:K0:Ex0VJC1eUY8rJfTIIYSmxTYGWrfv7qkySisAFQwFjNWLYVYq2Mx yKyM5prt6qC6PvzDb5YXm3l6/S2vSu3B4PgxwtC6zh+WwsDCdp5nQXnRsEO4Z9f/+DiELSQ ie1O5GJ4ajDfNxAm5jjd1hQ1EQwUwWSCnm3C0qz0yJmSniAzyRGOBFw0P3Z0KFdqwd0k9UB dOT+LrSaB4nfajBIiBCWw== X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x 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:76246 Archived-At: On Thu, 11 Jul 2013 22:16:00 +0300 Eli Zaretskii wrote: >> From: Stephen Berman >> Cc: Jan Dj=C3=A4rv , 14838@debbugs.gnu.org >> Date: Thu, 11 Jul 2013 20:51:42 +0200 >>=20 >> Here are the top 200 lines of another profile (not identical to the one >> I posted previously, but similar), which account for 99% of the CPU >> time. Is this saying that 70% of CPU time is spent in line-move-partial >> (and 82% in aref)? > > I don't believe the aref part. I think the real culprit is font-info. > Let's conduct an experiment: if you modify default-font-height so that > it always just calls frame-char-height, does the problem go away? Yep, that it does. And no trace messages are emitted. So it seems some fonts are sensitive to this distinction and others aren't. What is the crucial difference? >> >> vs 0 dlh 14 this nil rowh 13 rbot 1 py 0 vpos 32 last 31.0 >> >> 2 >> >>=20 >> >> and nothing else. >> > >> > The "py 0" part is very strange. "py" is the vertical coordinate of >> > point in screen line units. Since this was with C-n, I expect py >> > never to be less than half the screen height, which is 16. How come >> > it is zero, i.e. point is in the first line? Can you step through >> > line-move-partial in Edebug and see what is going on there? >>=20 >> If I instrument line-move-partial and type `C-n', I see py =3D 0 on the >> first line and it increases by 1 on each subsequent line. I have no >> idea why *Messages* only showed a value of 0 for py; could it be that >> the messages were overwritten when the CPU load hit 90%? > > Could be, since the messages are produced as part of redisplay. > > Can you show the trace messages from when the CPU is not yet 100% > busy, and Emacs can still keep up with scrolling? There are no trace messages while scrolling is normal; only after redisplay stops (with >90% CPU load) and then recovers do the messages appear, and they are all as above, with py=3D0. I verified this by adding a counter to the messages, and the first message emitted, with count=3D1, shows py=3D0, as do all subsequent (none are overwritten). Steve Berman