From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#56393: Actually fix the long lines display bug Date: Wed, 20 Jul 2022 09:13:21 +0000 Message-ID: <7d422ac79b1f73068b54@heytings.org> References: <38c1a31040d2d2bc47ae@heytings.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="wRnW4V0QVi" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39290"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56393@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jul 20 11:26:00 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oE5xw-0009zJ-CO for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 20 Jul 2022 11:26:00 +0200 Original-Received: from localhost ([::1]:35264 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oE5xv-0004U5-5c for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 20 Jul 2022 05:25:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oE5mN-0002DZ-K9 for bug-gnu-emacs@gnu.org; Wed, 20 Jul 2022 05:14:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58095) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oE5mM-0002ur-BR for bug-gnu-emacs@gnu.org; Wed, 20 Jul 2022 05:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oE5mM-0006JB-4E for bug-gnu-emacs@gnu.org; Wed, 20 Jul 2022 05:14:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 20 Jul 2022 09:14:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56393 X-GNU-PR-Package: emacs Original-Received: via spool by 56393-submit@debbugs.gnu.org id=B56393.165830840524114 (code B ref 56393); Wed, 20 Jul 2022 09:14:02 +0000 Original-Received: (at 56393) by debbugs.gnu.org; 20 Jul 2022 09:13:25 +0000 Original-Received: from localhost ([127.0.0.1]:55854 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oE5lk-0006Gr-Jk for submit@debbugs.gnu.org; Wed, 20 Jul 2022 05:13:24 -0400 Original-Received: from heytings.org ([95.142.160.155]:45048) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oE5li-0006Gi-VQ for 56393@debbugs.gnu.org; Wed, 20 Jul 2022 05:13:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1658308402; bh=MASF2o5mBstdnBD8Wt4R3M1zXAh412bQ8TbSlq+hn88=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=5NngT9OjuURxnRcSt4VP1O8n7kzJtg9sSJbVpEYclY7LWOcD8efuPQLbGkKOcJXom ZWzjCbvJItM/PUfZmkKNelF9Jy4fMswkn6lLMvz2kgINFGtZ/UQMdoIdlOf3e9NmwE ALjpha1FOqjF1SpcFv+cHs0mNCnpb5COdPxvZuMdohjnTncu5pWYLcFfmZeFgKcr9+ WOcIN/RuJShe3O9tS2WH1Aq/OCfOeaoXaHoyGxutWbakRr7NqfOJBjS1De+Lg7YJ1J O/PzwUoeajbQ85EtsRYx3dgXtnVCyF61NF0XkcsAIcqeSqeFc7g45aCw/TKZi1Pc+Y U/go52p1pDB1g== In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:237484 Archived-At: --wRnW4V0QVi Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >> Which leaves me with something to think about, of course: when=20 >> redisplay sets the flag in the buffer, then there's of course a time=20 >> before that. And the question is what can happen in that interval.=20 >> But not today. I'll come back to you. > > So far, I can't think of something specifically catastrophic happening=20 > in the interval between a buffer being loaded, let's say, and it being=20 > marked with the flag. > > I think it's the same situation we talked about previously wrt a buffer= =20 > that is never or not yet displayed: > > Pretty much anything could potentially happen as soon as an iterator is= =20 > used. The reason for this is that iterators must know faces and other=20 > stuff, let's simply say they must know text properties and overlays. And= =20 > that can call Lisp, and then all bets are off. > > If that happens in practice, how often it happens, or what else, I don't= =20 > know. > > What's the worst thing that can happen? Slowness, I guess. I can't=20 > think of something going seriously down the drain ATM. > Okay, now I see what you mean. As far as I can see (but I could be=20 wrong), there are no significant slowdowns between the moment the file is= =20 opened and the moment it is displayed. If such slowdowns exist, they are= =20 a separate problem, and will be dealt with when they will be reported. > > I guess that's about what I can continute to the whole matter. > > Nice work. THanks! > Thanks! =F0=9F=98=83 --wRnW4V0QVi--