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: Fri, 23 Dec 2022 07:55:03 +0300 [thread overview]
Message-ID: <Y6U0p9vm6yDvGHe4@protected.localdomain> (raw)
In-Reply-To: <83edssa4z3.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-12-21 23:17]:
> > and I use switches:
> >
> > -gohl --group-directories-first
>
> Tried that, still cannot reproduce.
>
> > Tell me directions on how to find what is happening the next time it
> > happens.
>
> 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.
I got now the buffer that does not refresh and I can inspect it if you
provide me guidance.
;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
n ;; dired-next-line
p ;; dired-previous-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
p ;; dired-previous-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
p ;; dired-previous-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
C-c l ;; rcd-async-last-buffers
C-x l ;; count-lines-page
C-x b ;; switch-to-buffer
<return> ;; minibuffer-complete-and-exit
C-h l ;; view-lossage
p ;; dired-previous-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
C-h l ;; view-lossage
C-1 ;; digit-argument
0 ;; digit-argument
0 ;; digit-argument
C-h l ;; view-lossage
p ;; dired-previous-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
C-h l ;; view-lossage
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-p ;; dired-previous-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
C-n ;; dired-next-line
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
d ;; dired-flag-file-deletion
d ;; dired-flag-file-deletion
d ;; dired-flag-file-deletion
d ;; dired-flag-file-deletion
d ;; dired-flag-file-deletion
x ;; dired-do-flagged-delete
y ;; self-insert-command
s ;; self-insert-command
<backspace> ;; delete-backward-char
e ;; self-insert-command
s ;; self-insert-command
<return> ;; exit-minibuffer
C-h l ;; view-lossage
C-x o ;; other-window
C-x o ;; other-window
g ;; revert-buffer
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
p ;; dired-previous-line
n ;; dired-next-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
C-p ;; dired-previous-line
B ;; dired-do-byte-compile
y ;; y-or-n-p-insert-y
C-h l ;; view-lossage
[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-23 4:55 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
2022-12-23 4:55 ` Jean Louis [this message]
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=Y6U0p9vm6yDvGHe4@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).