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#56393: Actually fix the long lines display bug Date: Fri, 8 Jul 2022 07:59:06 +0200 Message-ID: <77F17106-A919-4D17-B22C-F35E677E31A3@gmail.com> References: <38c1a31040d2d2bc47ae@heytings.org> <38c1a310405bd4bbe370@heytings.org> <87a69n98yy.fsf@yahoo.com> <38c1a31040f5546dbd3a@heytings.org> <87czej6buq.fsf@gnus.org> <38c1a31040e66d2b273e@heytings.org> <3ffab19196f1cb984244@heytings.org> Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Content-Type: multipart/signed; boundary="Apple-Mail=_B12ECABB-DB0D-4759-BF62-0E66E4D45146"; protocol="application/pgp-signature"; micalg=pgp-sha512 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33163"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 56393@debbugs.gnu.org To: Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 08 08:00:20 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 1o9h2J-0008Lv-9B for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 08 Jul 2022 08:00:19 +0200 Original-Received: from localhost ([::1]:55874 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o9h2H-00013a-O4 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 08 Jul 2022 02:00:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50398) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o9h25-00013K-MN for bug-gnu-emacs@gnu.org; Fri, 08 Jul 2022 02:00:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36422) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o9h22-0005KO-HC for bug-gnu-emacs@gnu.org; Fri, 08 Jul 2022 02:00:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o9h22-0001S6-G0 for bug-gnu-emacs@gnu.org; Fri, 08 Jul 2022 02:00:02 -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, 08 Jul 2022 06:00: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.16572599565487 (code B ref 56393); Fri, 08 Jul 2022 06:00:02 +0000 Original-Received: (at 56393) by debbugs.gnu.org; 8 Jul 2022 05:59:16 +0000 Original-Received: from localhost ([127.0.0.1]:58552 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9h1I-0001QR-4F for submit@debbugs.gnu.org; Fri, 08 Jul 2022 01:59:16 -0400 Original-Received: from mail-ej1-f46.google.com ([209.85.218.46]:39511) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9h1F-0001QD-PP for 56393@debbugs.gnu.org; Fri, 08 Jul 2022 01:59:14 -0400 Original-Received: by mail-ej1-f46.google.com with SMTP id a9so6249890ejf.6 for <56393@debbugs.gnu.org>; Thu, 07 Jul 2022 22:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=4b20ChKdwM4bxMYE2bM2vIfB5ABxClMgYPiH7FFhnHE=; b=YzhVCYUnEJ33fIxoVOutmZoK0OubKG74EJ1IsSGfwlB58JYKhH6sAhmysGQlU/Qavm XEXyA2nIW6oDz9N08QnuY07T1Y9aXjnwFj4OCo96mkO9olrUTQ1Nc/2KZPUD14yRDCZN 3CVwRRDZZ5WOgfw0xmKhAbc/gV0xl/YSio/fNFB49clEYXYT+ZrsYGqxYGJCoQ8gZ6aE epEv9ugvRi0ElL5NVPJhg/ncfCb6kjasjmtadMB2fulUR20Vb5MW5xGm6ESyB23aF7MD Tr3nFjOszxGOO8XzmwSJAgRaj7trFTOYVbFKDez6Z92FSbFeuXbGZ8vMdl6FQnYRBleP cThw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=4b20ChKdwM4bxMYE2bM2vIfB5ABxClMgYPiH7FFhnHE=; b=yhkQhj2AWT3JN5dKu6wA6t5UJv69DPXGejEsyzcQxJuQXyeksS398DnIZn1KfDkfJY 2XYqgFRTYQOMRXatoOIG9EgNH4JIIfhOgtsfFkQs7tdYCGfiLCfceqaM/dUo1MuF2NsE /sQLMqDNLmPUw7BmcQ6ivcg61jOO/coPfWWP6u5wf5ThfVekBnauRw14DvQ3PFmSlIWe SIAOg4yXbrj5BFs7jxHLcLRgU5UFfRiNJjmJWme8NShyLgNq89+zZ9YrOABrL1rcrwQg w9ac4pOdXVPE3rCA6fakMX+0xQSI2GX/hIpaoPK+f/GhXEuyaiK+xOiv6Y+rzIB1vRTg lbkA== X-Gm-Message-State: AJIora90PbM6gOe2KTjiFWxUdYAEbaInh5ZzGpF/ztzXnr9N1N7Kl7UG inDvaUn4EQz9/8M9nAjsmJs= X-Google-Smtp-Source: AGRyM1uFURrNVWVeVBL9QjUPaCO6njEVzaSet1ksZ5Yhlf0MzYnW8Y7I97ovSmdnZOqdRamCWmh60w== X-Received: by 2002:a17:906:7a58:b0:724:c5f7:21e9 with SMTP id i24-20020a1709067a5800b00724c5f721e9mr1877963ejo.90.1657259947930; Thu, 07 Jul 2022 22:59:07 -0700 (PDT) Original-Received: from smtpclient.apple (pd9e36b80.dip0.t-ipconnect.de. [217.227.107.128]) by smtp.gmail.com with ESMTPSA id f15-20020a1709062c4f00b007081282cbd8sm19869995ejh.76.2022.07.07.22.59.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jul 2022 22:59:07 -0700 (PDT) In-Reply-To: <3ffab19196f1cb984244@heytings.org> X-Mailer: Apple Mail (2.3696.100.31) 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:236430 Archived-At: --Apple-Mail=_B12ECABB-DB0D-4759-BF62-0E66E4D45146 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 2022-07-07,, at 20:38 , Gregory Heytings = wrote: >=20 >> I'd find it easier to read if the if/else were reversed to that the ! = isn't needed. >>=20 >=20 > I'm not sure what the convention is here (or even if there is a = convention). But my feeling is that it's better to place the "normal" = case first, and the exceptional case in the else part. Ok. Tastes differ, I guess. >> Could you please tell in what circumstances the call would not set = the variable? And wouldn't the minot mode print something, also? In = other words, can we remove it more or less safely? (If the user screws = up, all bets are off anyway.) >>=20 >=20 > It should always set the variable indeed, but who knows what a user = could do if they decide for some reason to override the definition of = auto-narrow-mode in their init file? Setting the narrowing state again = here is a cheap safety measure that avoids calling that function again = during each redisplay cycle. >=20 > I don't know why the minor mode doesn't print something when it's = called from C, but it doesn't. I think we could use Ffuncall_interactively here to get the message = printed. --Apple-Mail=_B12ECABB-DB0D-4759-BF62-0E66E4D45146 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEEirYePpiT82Hjkftpc+obGZDFPmMFAmLHx6oACgkQc+obGZDF PmNQPBAA0Ii73nUx6KGeR/krs2UtkKJ9x6UhFT50wGhAddZDHuhm5LdrwqgsSuHk WNMJHNU39FAhQuecLt1IQ6iYamjzw84ePVI/2UcBi1g+hfc4rVwK6uZQKjJCrGdl 0lZx4wxoTyDyf55jnbVZajCDH6TIPIlwBR6EeYizJGNty8bBFd/91mvy6zS+qYES CLnR5g/MfLyLIaw83E8jXjHryAbXRqTWg6KM0IKbXCYyZ9w1EVS7Hh9C60Gsk2U3 SXxxlE+h/BBlbBfrzNPxUBl+wnHTs8PCVAA5kC9t5txeWcxmMBbAr/EZhN2l1Qg/ hN3GWoKoPjpYhc/pCSXLBM/szxHrD4L+Qh9Z2HO51XWGmACxSzNA7WhlMROGMLEp 3bJgPt/bEvq6/ykvpWaDUH+ZhyOL9DjeiO0p8mb5ke7QUQgHdPZcIt+jIOw0bb94 jxBbtzXryPaqHMMU1XNbKFMKJ8G8LQXRMeafVVIB63ytLNNQDuGvHsq0ldvUWtbB vI32JqW/+3x4I/BJh4AVK7NjI4puVjYT7HGXWE5J6RETpm3Pw1XVhnWt5R/WyAgJ 4xww6DoAFQC7fO0VlW1B/eG3PUEe3d9U4NGeY3F2Fv4J3oRM0OKMTHOIJF6TBzTj FMi1RfnRjyxoZqZzTs/djsCy90wyYaaFJm41pedl4iVizuCE0zA= =hR4T -----END PGP SIGNATURE----- --Apple-Mail=_B12ECABB-DB0D-4759-BF62-0E66E4D45146--