From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#2749: 23.0.91; Visual Line Mode: incorrect line wrapping in corner case Date: Sun, 19 May 2013 20:38:46 +0300 Message-ID: <83mwrqx42h.fsf@gnu.org> 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> <87fvxjkk6s.fsf@rosalinde.fritz.box> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1368985183 30458 80.91.229.3 (19 May 2013 17:39:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 19 May 2013 17:39:43 +0000 (UTC) Cc: 2749@debbugs.gnu.org To: Stephen Berman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun May 19 19:39:41 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 1Ue7a7-0003AZ-G8 for geb-bug-gnu-emacs@m.gmane.org; Sun, 19 May 2013 19:39:39 +0200 Original-Received: from localhost ([::1]:58170 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ue7a7-0008EF-3W for geb-bug-gnu-emacs@m.gmane.org; Sun, 19 May 2013 13:39:39 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:33831) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ue7a4-0008E8-6o for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 13:39:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ue7a1-0006uS-UZ for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 13:39:36 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:35062) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ue7a1-0006uO-RU for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 13:39:33 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1Ue7aT-0002fw-Rv for bug-gnu-emacs@gnu.org; Sun, 19 May 2013 13:40:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 19 May 2013 17:40:01 +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.136898518310242 (code B ref 2749); Sun, 19 May 2013 17:40:01 +0000 Original-Received: (at 2749) by debbugs.gnu.org; 19 May 2013 17:39:43 +0000 Original-Received: from localhost ([127.0.0.1]:51653 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Ue7aB-0002f9-5Q for submit@debbugs.gnu.org; Sun, 19 May 2013 13:39:43 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:47292) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Ue7a9-0002ev-4J for 2749@debbugs.gnu.org; Sun, 19 May 2013 13:39:42 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MN200D003NZFA00@a-mtaout22.012.net.il> for 2749@debbugs.gnu.org; Sun, 19 May 2013 20:38:58 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MN200DHA3OX4H90@a-mtaout22.012.net.il>; Sun, 19 May 2013 20:38:58 +0300 (IDT) In-reply-to: <87fvxjkk6s.fsf@rosalinde.fritz.box> X-012-Sender: halo1@inter.net.il 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:74406 Archived-At: > From: Stephen Berman > Cc: monnier@iro.umontreal.ca, 2749@debbugs.gnu.org > Date: Sun, 19 May 2013 18:28:59 +0200 > > 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. Changes such as the one you suggested are bound to break any number of places that are all related to functions that simulate display. vertical-motion is one of them, but in no way the only one. Display properties and overlays tend to reveal such problems sooner, because they already strain the relevant code, and require all kinds of ad-hoc'ery that is easy to break. But they are not the only ones. > 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.... I don't mind trying a bit longer, I just want to know what kind of process are we involved in here. If there were a decision (by Stefan) to introduce this feature no matter what, then I'd understand that any fallout needs to be fixed. But this not being the case, I wonder what are we trying to accomplish here. I'll take a look when I have time.