From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#56423: 29.0.50; Hi-lock in dired broken by toggling wdired-mode Date: Fri, 08 Jul 2022 14:57:34 +0200 Message-ID: <871quv92yp.fsf@web.de> References: <874jzui52r.fsf@web.de> <87iloa2hlm.fsf@web.de> <87mtdmyrp4.fsf@web.de> <83o7y15vtz.fsf@gnu.org> <87edyxz0as.fsf@web.de> <83czeh5hy9.fsf@gnu.org> <87bku15g5e.fsf@web.de> <835yk959w4.fsf@gnu.org> <87sfndufh3.fsf@web.de> <87o7y1uf03.fsf@web.de> <83y1x452r7.fsf@gnu.org> <875yk795fd.fsf@web.de> <83a69j4wwc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40193"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 56423@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 08 15:04:40 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 1o9nex-000AEw-TD for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 08 Jul 2022 15:04:39 +0200 Original-Received: from localhost ([::1]:52962 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o9new-0007he-TM for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 08 Jul 2022 09:04:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56230) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o9nYY-0003tx-KZ for bug-gnu-emacs@gnu.org; Fri, 08 Jul 2022 08:58:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36934) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o9nYY-0003Gi-Bl for bug-gnu-emacs@gnu.org; Fri, 08 Jul 2022 08:58:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o9nYY-00022T-AS for bug-gnu-emacs@gnu.org; Fri, 08 Jul 2022 08:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 08 Jul 2022 12:58:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56423 X-GNU-PR-Package: emacs Original-Received: via spool by 56423-submit@debbugs.gnu.org id=B56423.16572850677767 (code B ref 56423); Fri, 08 Jul 2022 12:58:02 +0000 Original-Received: (at 56423) by debbugs.gnu.org; 8 Jul 2022 12:57:47 +0000 Original-Received: from localhost ([127.0.0.1]:59064 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9nYJ-00021C-0W for submit@debbugs.gnu.org; Fri, 08 Jul 2022 08:57:47 -0400 Original-Received: from mout.web.de ([212.227.15.3]:51901) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o9nYD-00020O-9j for 56423@debbugs.gnu.org; Fri, 08 Jul 2022 08:57:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1657285055; bh=NMfZG5vPjC5Cy9n6YVCc2eJy0RPm7DIyB3DryHk/OqE=; h=X-UI-Sender-Class:From:To:Cc:Subject:In-Reply-To:References:Date; b=Wj+qfI7i4AU2tDJzCSa5TFqv+Ho4zYIo271A2oheE/iloc1aRd8nYXbqE1VUxE6y6 KQ236qXXyTzSt8B0gJIGKc8fobBfXguuVSqvlAdA+zHWbKIcImNfWDr94CzQHcr9bp mI2HmFeICqD8gzzig22qWVgWelYMmoRX81ACsETw= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([84.59.210.236]) by smtp.web.de (mrweb005 [213.165.67.108]) with ESMTPSA (Nemesis) id 1MdwJO-1ncOTJ0wEw-00arGJ; Fri, 08 Jul 2022 14:57:35 +0200 In-Reply-To: <83a69j4wwc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Jul 2022 15:22:11 +0300") X-Provags-ID: V03:K1:Cs9vqR/C3pDW+n3UD8mTh3etw9Js8paOS6/fSn7FOmhkLJL4fqm euWnhRWvJCiYmUkhM5mDpIyU2yri6biZAyMCGqPpx98FsvpJbFSZICbo9VFQk8CBn9BS5no 7fF6LByC7pGQEq5WyMwlMSAFnlBTQM0+70NN6qoHrlBVJBoUu10Gmna0MlBmYFHHkxnaGG8 0prwiwSDBERhMENauY52w== X-UI-Out-Filterresults: notjunk:1;V03:K0:CwZuiY7Rdug=:SLTIMTr9+Q2qQxmk2yyuNj pWrlfNzIU77fRhQMpUeG3CYOvFV/Zi3iVJrNDYAbrSmpMQeo/yWn8n3ghOY16aTgK01LW2qWy xC3Dtf28gCxdUZtysGNT8qfrrnBaywFXPX/ggroWQBN+HvRimPZRoZelXksOp3MwUdncAQhxU gWH/qVdltrA1HMoVylKXWyD6Rg9qTw2h+/26ttH+OvZeSKW5Z7wB+2zVzDMCv54cy68vpjmUZ kfS6lprG464ZF7s4zrqtw8i58EhngeF/oPN3KT1esFNQsaGokSYtBL4a1ciChIy3ZuO9FNM1S pW14LBCN9wQwZGyPE/u08f0m/G7+y4oODkPUr1/z9FaFxQIb7ewTkzjRJwzwjl4LPfFO8pFnK imLMhnHV2d8548TGs0SdcNnBy35Ij0vYko2hzXlZPyCVXujVg8tphAWm6fRaJHYgzaG5HGFz6 IwXbF+DGGOcmxnjQuv9Yy+2/dKJrTlhNC3PDvVBh4aNypvOQOSJUg8M9AAbXMJWNC3ZOW2lAf 5ne+Kmk/USdxjrU4ShKjNzBLE9DcgOtp29R/2UWDrjZDGgMUwDa+LHzAadgFaDqvilM4q6+f5 a4P0js8dL6p9u5N28ZTG0xW/6QKKdEv/6v07lmHUOIpm9B/2YYg2xYphMtdE77/Rqa+RTP0TB w0jelI+CtMoU9Or4C/Z+ys4M3fHBUrweaOB+7ndQKAkweiv88uSCgUHZ9Ib4cQCCf1UCo9KI2 50VXGPz4LqFCcIGB0GAzLC7M1lURA8ZVK7f5Sn4TkxaizWxAYFggUjMxtjxfy66STncp1loh 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:236451 Archived-At: Eli Zaretskii writes: > You mean, the display will no longer match the actual situation on > disk? Then I think an unwind-protect or condition-case form that > resyncs the display in case of a signal is in order, since preventing > the user from aborting in that place would be wrong -- what if the > user realizes, too late, that some of the changes mean trouble? The question is how to unwind. I guess the only sensible action would be to revert the dired buffer, since we can't revert partial file changes, and the situation could look differently in many different ways. Michael.