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#2749: 23.0.91; Visual Line Mode: incorrect line wrapping in corner case Date: Sun, 19 May 2013 18:28:59 +0200 Message-ID: <87fvxjkk6s.fsf@rosalinde.fritz.box> References: <87d4c694r2.fsf@cyd.mit.edu> <87obfhhn9d.fsf@rosalinde.fritz.box> <871u9f6ij1.fsf@rosalinde.fritz.box> <83ip2qc23k.fsf@gnu.org> <87wqr66dij.fsf@rosalinde.fritz.box> <83ehdebut7.fsf@gnu.org> <87sj1u64ew.fsf@rosalinde.fritz.box> <83d2sybphy.fsf@gnu.org> <87mwrs6ng7.fsf@rosalinde.fritz.box> <83sj1jvvhl.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1368980985 24054 80.91.229.3 (19 May 2013 16:29:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 19 May 2013 16:29:45 +0000 (UTC) Cc: 2749@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun May 19 18:29:44 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 1Ue6UR-0001FV-BY for geb-bug-gnu-emacs@m.gmane.org; Sun, 19 May 2013 18:29:43 +0200 Original-Received: from localhost ([::1]:46147 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ue6UQ-0006VV-Rb for geb-bug-gnu-emacs@m.gmane.org; Sun, 19 May 2013 12:29:42 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:46362) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ue6UL-0006SS-Tv for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 12:29:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ue6UJ-00032C-FJ for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 12:29:37 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:34996) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ue6UJ-000326-CU for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 12:29:35 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1Ue6Uk-0000H3-R9 for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 12:30:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stephen Berman Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 19 May 2013 16:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 2749 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 2749-submit@debbugs.gnu.org id=B2749.1368980979961 (code B ref 2749); Sun, 19 May 2013 16:30:02 +0000 Original-Received: (at 2749) by debbugs.gnu.org; 19 May 2013 16:29:39 +0000 Original-Received: from localhost ([127.0.0.1]:51587 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Ue6UM-0000FS-Ro for submit@debbugs.gnu.org; Sun, 19 May 2013 12:29:39 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:51714) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Ue6UK-0000F1-E1 for 2749@debbugs.gnu.org; Sun, 19 May 2013 12:29:37 -0400 Original-Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MJqWY-1UfCPK0rDA-001CMj for <2749@debbugs.gnu.org>; Sun, 19 May 2013 18:29:02 +0200 Original-Received: (qmail invoked by alias); 19 May 2013 16:29:01 -0000 Original-Received: from i59F56002.versanet.de (EHLO rosalinde.fritz.box) [89.245.96.2] by mail.gmx.net (mp028) with SMTP; 19 May 2013 18:29:01 +0200 X-Authenticated: #20778731 X-Provags-ID: V01U2FsdGVkX1+rD2hQ0CWrHzPabBwCmnWZrBdgpvSzcSfvohowIm CNM39ImwdR7RO8 In-Reply-To: <83sj1jvvhl.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 May 2013 18:29:26 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-Y-GMX-Trusted: 0 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.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:74405 Archived-At: On Sun, 19 May 2013 18:29:26 +0300 Eli Zaretskii wrote: >> From: Stephen Berman >> Cc: monnier@iro.umontreal.ca, 2749@debbugs.gnu.org >> Date: Sat, 18 May 2013 22:30:00 +0200 >> >> I hope Stefan's silence till now just means he hasn't yet had time to >> give this issue due consideration.... >> >> In the mean time, I've encountered another problem, which has nothing to >> do with display properties or overlays: > > So let me see if I understand how this works: you discover one by one > the problems about this change, those same problems I was afraid of, > and I get to debug them, is that right? ;-) Is this new problem one you anticipated? I thought you were worried about problems arising from heavy use of display properties, but this doesn't involve any. Anyway, I really do wish I knew how to debug this myself. I tried stepping though Fvertical_motion but that has many calls to other parts of the code and I couldn't follow it well -- didn't know what could be skipped over, or what values to test, etc. It looked like point moved into the fringe after a call to, I think, read_char but I couldn't tell if that was really the trigger (doesn't seem likely). Of course, I would be grateful if you'd give me any help or advice about how to debug it, but I suspect that wouldn't be less burdensome to you than debugging it yourself ;-) > Is there any point in this game where we say "enough", as too many > problems were discovered for too small a gain? Or does this go on > forever? Well, I hope you agree what started this is a real bug. If you, Stefan or other Emacs maintainers tell me it's not worth fixing, I can live with that. But as long as long as it's not fixed, other people may encounter it and report it again.... >> -1. Apply both my patch and yours (Eli's). > > If you don't apply mine, does this problem still happen? No, with my patch and without yours, this problem goes away. So then we're back to the previous problem.... ;-) Steve Berman