unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58286@debbugs.gnu.org
Subject: bug#58286: 29.0.50; (dired-toggle-read-only) should verify if file names changed
Date: Wed, 5 Oct 2022 22:11:49 +0300	[thread overview]
Message-ID: <Yz3W9ZASFQP/JP1q@protected.localdomain> (raw)
In-Reply-To: <87zgeb3lwr.fsf@gnus.org>

* Lars Ingebrigtsen <larsi@gnus.org> [2022-10-04 13:48]:
> Jean Louis <bugs@gnu.support> writes:
> 
> > I have noticed that C-x C-q does not verify if file names changed.
> >
> > If file name was:
> >
> > my-file.ext.part
> >
> > once C-x C-q is invoked, it does not refresh buffer. In my opinion it
> > shall refresh buffer or warn that file name does not exist any more, if
> > it does not, so that editing of file names makes sense.
> 
> I don't understand what you mean here -- editing file names in wdired
> works fine for me.
> 
> Do you have a step-by-step recipe, starting from "emacs -Q", that
> demonstrates the problem?

It is explained above. The file my-file.ext.part was edited, but then
at some point the file named changed during editing, or file may be
removed. After editing, the buffer was not refreshed. I could see new
file name in the buffer while that file did not exist.

With emacs -Q I see that it refreshes.

I can't understand why and how, that is what happened. I do not change
dired myself in anyway, even if not used with emacs -Q.

-- 
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-10-05 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  1:14 bug#58286: 29.0.50; (dired-toggle-read-only) should verify if file names changed Jean Louis
2022-10-04 10:47 ` Lars Ingebrigtsen
2022-10-05 19:11   ` Jean Louis [this message]
2022-10-06 11:59     ` Lars Ingebrigtsen
2023-09-03  9:26       ` Stefan Kangas

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=Yz3W9ZASFQP/JP1q@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=58286@debbugs.gnu.org \
    --cc=larsi@gnus.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).