From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#56683: 29.0.50; long lines fix doesn't work correctly when lines are truncated Date: Fri, 22 Jul 2022 09:52:16 +0200 Message-ID: References: <87h73ab8bo.fsf@gmail.com> <83zgh2kzlo.fsf@gnu.org> <83y1wlllnc.fsf@gnu.org> <83mtd1li6o.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7556"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (darwin) Cc: andreyorst@gmail.com, 56683@debbugs.gnu.org, gregory@heytings.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 22 09:54:43 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 1oEnUh-0001j7-4Z for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 22 Jul 2022 09:54:43 +0200 Original-Received: from localhost ([::1]:42674 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oEnUf-0008OS-Fx for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 22 Jul 2022 03:54:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57536) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oEnT3-0007TP-VA for bug-gnu-emacs@gnu.org; Fri, 22 Jul 2022 03:53:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50315) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oEnT3-0000PQ-Lc for bug-gnu-emacs@gnu.org; Fri, 22 Jul 2022 03:53:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oEnT3-0000Gw-HL for bug-gnu-emacs@gnu.org; Fri, 22 Jul 2022 03:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 22 Jul 2022 07:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56683 X-GNU-PR-Package: emacs Original-Received: via spool by 56683-submit@debbugs.gnu.org id=B56683.1658476348954 (code B ref 56683); Fri, 22 Jul 2022 07:53:01 +0000 Original-Received: (at 56683) by debbugs.gnu.org; 22 Jul 2022 07:52:28 +0000 Original-Received: from localhost ([127.0.0.1]:40045 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oEnSW-0000FK-0F for submit@debbugs.gnu.org; Fri, 22 Jul 2022 03:52:28 -0400 Original-Received: from mail-ed1-f46.google.com ([209.85.208.46]:33776) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oEnSU-0000F3-BP for 56683@debbugs.gnu.org; Fri, 22 Jul 2022 03:52:26 -0400 Original-Received: by mail-ed1-f46.google.com with SMTP id t3so4915618edd.0 for <56683@debbugs.gnu.org>; Fri, 22 Jul 2022 00:52:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :user-agent:mime-version:content-transfer-encoding; bh=ZVtNaqbscSx/QjKIfu8vljzZWfIJO2VappmX3C8ucyY=; b=WPZtzQVGv22yEzJzkcf3QxJegLKDNqZjf3SES0E0QDeUl8zWlGXhyrqCpozb7xdVs+ VgE0nwcEluhi3BVMW4T1HF8dUOMi8eCLBuTibfzDOWUQh7vYM8kiLT8Wg6jD+S9Kv9lY JFL2bWQTrl37VyfD2//HhesF/mvtELIjgnZz2eJFgLgQikZ+nS/lBoohqTwXKM0WEao9 ny1oHuh+WYdaYMqBX7Duy29ZT2bxedQVbdlebxE/9SuuCGfwkKYt6hmQ6tJdrD/tRTiq SeQEDvqSG7Ncdx0+wN5xrjSS6zQyhfgXzFy8naa91sMkaetk/Y4/aWFoJ8IjqXZ2EBjM Wxmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:user-agent:mime-version:content-transfer-encoding; bh=ZVtNaqbscSx/QjKIfu8vljzZWfIJO2VappmX3C8ucyY=; b=TZnlswxNS6iauAd4ODhpLerkABcD4Us8MU6rQDhtwmiCkIhGrUODN+h/tS/5hixhwV Lv1gQ4ETb2gsR+ToR0nyNHOT+i4Clb+TSE80JVRq4in1e6tmW2tObPI+C+/ZC810mRoJ R0MxRrEz6UVH9pdSnwc+ftEbnp6YoXEVZfgFpi7Ig797YFmLFu6WzmfBPFU/P86Gqdyd QqkdcBku8qZ9Q7P2R/V71or7Fdu1HZGSrBY1KICLomdF3fWS0A1Z4uAwdGky1S9f0M71 wZno3k4WJ7ad5pigrKiupw7n5y8wwMtr+S+O85d8DrERkLxWZNmAfGFYKMTkIHgMKD5x 0kAg== X-Gm-Message-State: AJIora9A6clVVIcEjZwcT9FVc7Bfz6qMwfZ5Q5HQcop5NaPd89vKoVDQ ysL9kmI9vzumhO7RENl6DoY= X-Google-Smtp-Source: AGRyM1tUFXaIJW7IGQGv0wqx+osDvUzR5tOJoANca2l3cfZ95oBFXWf3KZAeIrLuxvw/kljmhKyPlg== X-Received: by 2002:a05:6402:2395:b0:43a:6d91:106c with SMTP id j21-20020a056402239500b0043a6d91106cmr2247746eda.299.1658476338007; Fri, 22 Jul 2022 00:52:18 -0700 (PDT) Original-Received: from Mini.fritz.box (p4fe3a8ba.dip0.t-ipconnect.de. [79.227.168.186]) by smtp.gmail.com with ESMTPSA id w23-20020a17090649d700b0072b33e91f96sm1713686ejv.190.2022.07.22.00.52.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Jul 2022 00:52:17 -0700 (PDT) In-Reply-To: <83mtd1li6o.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Jul 2022 10:28:47 +0300") 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:237599 Archived-At: Eli Zaretskii writes: >> From: Gerd M=C3=B6llmann >> If we really want infinity, how about setting last_visible_x to -1 in >> that case. But that requires checking/changing some places where >> the iterator pisition is tested against last_visible_x. > > I don't really see how this could help in general, because the > current_x member (what you call the "iterator position") will still > overflow at some point, and we can no longer do any layout decisions > for the X coordinate after that. > > Or what am I missing? You were asking for a good value of DISP_OMEGA, that's at least what I understood. My answer is -1, plus code changes. That current_x can overflow is something completely different, IMO. But now I'm cautious enough to ask what do you mean? Overflowing which bound? I read this as integer overflow, integer =3D the data type. > >> Your "ticks" check kicks in should be burn to much time because of the >> infinite last x, right? > > Sorry, I don't think I understand what you are asking here. Please > elaborate or rephrase. The thing you implemented in set_iterator_to_next we talked about. if (max_redisplay_ticks > 0) update_redisplay_ticks (1, it->w); I don't remember the offical name ATM.