unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Harald Judt <h.judt@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57565@debbugs.gnu.org
Subject: bug#57565: 28.1; dired cons bug
Date: Sat, 3 Sep 2022 21:46:49 +0200	[thread overview]
Message-ID: <cd51a0c6-2508-7c3e-8374-8c3543c4d6c7@gmx.at> (raw)
In-Reply-To: <83ilm4mhsb.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 2225 bytes --]

Hi Eli,

Am 03.09.22 um 20:31 schrieb Eli Zaretskii:
>> Date: Sat, 3 Sep 2022 20:21:38 +0200
>> From: Harald Judt <h.judt@gmx.at>
>>
>> Say I do the following call to open a dired buffer and insert the files:
>>
>> (dired (cons "/home/user" '("/home/user/tmp/test/a/a"
>> "/home/user/tmp/test/b/b" "/home/user/tmp/test/c/c")))
>>
>> It works fine, I get a nice listing and can move around like expected, mark
>> files and try to delete them. Now it gets interesting: Usually after hitting
>> "x" to execute, then confirming the deletion, the buffer will refresh. But not
>> in this case, not when I open dired using the cons above. I can revert the
>> buffer using "g".
>>
>> Note that when I simply do (dired "/home/user/tmp/test"), then insert the
>> subdir to show the files and delete them, this is not reproducible. The buffer
>> will be refreshed immediately after the delete operation completes.
>>
>> I am reporting this bug because I have been advised to do so. Reference:
>> https://lists.gnu.org/archive/html/help-gnu-emacs/2022-08/msg00097.html
>>
>> A patch has been posted which fixes this problem:
>> https://lists.gnu.org/archive/html/help-gnu-emacs/2022-08/msg00102.html
>>
>> It would be nice to see this bug fixed.
> 
> I will install the change when the person who reported it will tell me
> that it caused no problems.  I'm still waiting for that final
> feedback.

Thank you for your patch and your fast response.

In fact, that was me. Testing all actions I could think of regarding deletions 
(locally and remotely via TRAMP scp), I have not encountered any issues so 
far. If I understand correctly, only deletions are affected by this, so there 
shouldn't be any side-effects regarding other features. Maybe there could be 
similar problems in other parts of the code, but so far I didn't experience 
anything hinting to that, and if there are, then probably they need a separate 
fix.

I apologize for replying so late, but I somehow missed I have been asked to 
report this as a bug here.

Best regards,
Harald

-- 
`Experience is the best teacher.'

PGP Key ID: 4FFFAB21B8580ABD
Fingerprint: E073 6DD8 FF40 9CF2 0665 11D4 4FFF AB21 B858 0ABD

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-09-03 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03 18:21 bug#57565: 28.1; dired cons bug Harald Judt
2022-09-03 18:31 ` Eli Zaretskii
2022-09-03 19:46   ` Harald Judt [this message]
2022-09-04  5:42     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cd51a0c6-2508-7c3e-8374-8c3543c4d6c7@gmx.at \
    --to=h.judt@gmx.at \
    --cc=57565@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).