unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 08:23:10 +0300	[thread overview]
Message-ID: <Y6U7PnrJTDZwzdNr@protected.localdomain> (raw)
In-Reply-To: <Y6U0p9vm6yDvGHe4@protected.localdomain>

Hello Eli,

Now I can reproduce the bug "why Dired buffer does not update" with
`emacs -Q'.

The new video for those who can see it is here: 
https://gnu.support/images/tmp/2022-12-23/2022-12-23-07:56:46.ogv

Conditions that Dired buffer will not update is related to default
directory being changed, being something else than what is the Dired
buffer. 

To reproduce it in `emacs -Q' you please do following:

- go into any Dired buffer;

- M-x cd RET and change default directory to something else than Dired
  buffer

- key B will inject new lines of a byte-compiled file without
  refreshing, delete by moving to Trash will delete without refreshing
  the Dired buffer.

I can only assume that variable `default-directory' shall remain local
to Dired buffer even if user invokes `M-x cd' or programmatically `cd'.

And I never invoke `M-x cd' in Dired buffers, but I may invoke it in
other functions such as below:

(defun cf-send-sms (id)
  "Sends the SMS by using default SMS function"
  (cd (getenv "HOME"))

And the reason to `cd' to HOME directory is to escape programs to try
external commands within Tramp directories. I will try using
`executable-find' for external programs, but again I think that when
my functions get Tramp directory as default directory then they don't
find either executables or directories, that is why I am changing to
$HOME.

For Dired updating, I think that M-x cd shall not change the
default-directory for Dired buffer -- and again -- I am not using it
interactively but in functions.

Now I can't remember how I invoked a function that uses `cd' but I can
focus on it next time. Maybe I just launched some of functions.

--
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/







  reply	other threads:[~2022-12-23  5:23 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
2022-12-23  5:23         ` Jean Louis [this message]
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=Y6U7PnrJTDZwzdNr@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).