From: Arthur Miller <arthur.miller@live.com>
To: Marco Centurion - URI <mcenturion@fing.edu.uy>
Cc: 47058@debbugs.gnu.org
Subject: bug#47058: 28.0.50; Dired Z: insert-directory: Reading directory: No such file or directory, CrossLine_linux_x86
Date: Wed, 01 Sep 2021 18:06:45 +0200 [thread overview]
Message-ID: <AM9PR09MB4977E97EC0750F431A1BEDD196CD9@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <pk635qoflck.fsf@crusher.fing.edu.uy> (Marco Centurion's message of "Wed, 01 Sep 2021 10:59:07 -0300")
Marco Centurion - URI <mcenturion@fing.edu.uy> writes:
> Arthur Miller <arthur.miller@live.com> writes:
>
>> Marco Centurion <mcenturion@fing.edu.uy> writes:
>>
>>> I can confirm that this bug is present and pretty easy to reproduce.
>>> Steps to reproduce:
>>>
>>> ----
>>> $ touch test1
>>> $ tar czf test.tar.gz test1
>>> $ rm test1
>>>
>>> In dired, press Z (`dired-do-compress`) when the point is on test.tar.gz
>>> ----
>> I just did all those steps in emacs -Q, and I can not confirm any errors. I
>> named files exactly as you show there, and decompressed file is correctly named
>> 'test1'.
>>
>> I tested in two different directories, you three shell commands from terminal
>> (st in my case), and Z from dired created correctly test1.
>>
Ahh, sorry, I saw just the mail I answered and thought the bug was about that.
> Yes, the file is correctly decompressed. The original report is about
> an error message that shows up in the minibuffer "Reading directory: No
> such file or directory, test". And that's what I was able to reproduce
> without having to download the file linked in the report, something that
> I guess a lot of people wouldn't want to do.
>
>> Press 'g'.
>
> I do that, I just thought that it's a bit of a weird behaviour that
> sometimes after pressing Z the dired buffer is consistent with what's
> actually in the directory and sometimes it's not. That is all.
> Personally I wouldn't be opposed to reverting the buffer after every
> operation that modifies files, but I'm sure most would and with good
> reason.
Yes, it would be more consistent if all changes were reflected immidiately. I
have global-auto-revert-mode on, so it helps a bit, but I still have to
sometimes press 'g' to refresh the dired view.
next prev parent reply other threads:[~2021-09-01 16:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 20:26 bug#47058: 28.0.50; Dired Z: insert-directory: Reading directory: No such file or directory, CrossLine_linux_x86 Jean Louis
2021-08-31 21:33 ` Marco Centurion
2021-08-31 22:12 ` Arthur Miller
2021-09-01 13:59 ` Marco Centurion - URI
2021-09-01 16:06 ` Arthur Miller [this message]
2021-09-20 22:12 ` Michalis V.
2021-09-21 4:32 ` Lars Ingebrigtsen
2021-09-21 8:24 ` Eli Zaretskii
2021-09-21 9:18 ` Michalis V.
2021-09-21 9:32 ` Eli Zaretskii
2021-09-21 17:10 ` Lars Ingebrigtsen
[not found] ` <83a6k5yfrb.fsf@gnu.org>
2021-09-21 17:58 ` Lars Ingebrigtsen
2021-09-21 18:38 ` Gregory Heytings
2021-09-21 18:43 ` Eli Zaretskii
2021-09-21 19:19 ` Gregory Heytings
2021-09-21 20:11 ` Michalis V.
2021-09-21 20:48 ` Gregory Heytings
2021-09-22 5:40 ` Eli Zaretskii
2021-09-22 7:15 ` Gregory Heytings
2021-09-22 7:54 ` Eli Zaretskii
2021-09-22 8:07 ` Gregory Heytings
2021-09-21 17:07 ` Lars Ingebrigtsen
2021-09-21 20:43 ` Michalis V.
2021-09-22 6:00 ` Eli Zaretskii
2021-09-21 8:25 ` Michael Albinus
2021-09-21 9:24 ` Michalis V.
2021-09-21 12:06 ` Michael Albinus
2022-03-11 8:29 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM9PR09MB4977E97EC0750F431A1BEDD196CD9@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=47058@debbugs.gnu.org \
--cc=mcenturion@fing.edu.uy \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.