From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60233@debbugs.gnu.org
Subject: bug#60233: 30.0.50; Dired buffer not updating sometimes
Date: Thu, 22 Dec 2022 10:18:59 +0300 [thread overview]
Message-ID: <Y6QE4wHXe8NinwOf@protected.localdomain> (raw)
In-Reply-To: <83edssa4z3.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-12-21 23:16]:
> > Date: Wed, 21 Dec 2022 21:54:24 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: 60233@debbugs.gnu.org
> >
> > It creates new file, it does insert the file in Dired buffer, but the
> > file is double to previous one. It starts appearing as following:
> >
> > -rw-r--r-- 1 22K Dec 21 09:54 rcd-org-export.el
> > -rw-r--r-- 1 22K Dec 21 21:50 rcd-org-export.elc
> > -rw-r--r-- 1 22K Dec 21 21:50 rcd-org-export.elc
> > -rw-r--r-- 1 22K Dec 21 21:50 rcd-org-export.elc
> > -rw-r--r-- 1 22K Dec 21 21:50 rcd-org-export.elc
>
> Just by pressing B? I cannot reproduce this here. Please tell how to
> reproduce in "emacs -Q". (Btw, byte-compile-file is not bound to b,
> it is bound to B, upper-case, at least by default.)
Yes, it was my mistake when writing bug report.
> > I also use dired-x
>
> How?
I just load that library every time, as I use it's functions.
> Type "C-h l" and post everything that pops up in a buffer, I guess.
> I'm really in the dark here. You need to try to note what you were
> doing that is somewhat special in those cases.
OK I am sure it will come again, then I will use C-h l and report back.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-12-22 7:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 5:20 bug#60233: 30.0.50; Dired buffer not updating sometimes Jean Louis
2022-12-21 12:38 ` Eli Zaretskii
2022-12-21 18:54 ` Jean Louis
2022-12-21 20:15 ` Eli Zaretskii
2022-12-22 7:18 ` Jean Louis [this message]
2022-12-23 4:55 ` Jean Louis
2022-12-23 5:23 ` Jean Louis
2022-12-23 8:05 ` Michael Albinus
2022-12-23 8:46 ` Jean Louis
2022-12-24 12:23 ` Eli Zaretskii
2022-12-24 13:03 ` Jean Louis
2022-12-24 16:50 ` Eli Zaretskii
2022-12-22 21:48 ` Gregory Heytings
2022-12-23 5:03 ` Jean Louis
2022-12-23 8:30 ` 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=Y6QE4wHXe8NinwOf@protected.localdomain \
--to=bugs@gnu.support \
--cc=60233@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).