From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Bug in Ange-FTP with renaming files
Date: Sun, 06 Jul 2003 16:56:34 +0200 [thread overview]
Message-ID: <84isqfsnz1.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 84n0frsobv.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> kai.grossjohann@gmx.net (Kai Großjohann) writes:
>
>> I shall try to investigate further, but I thought it would be good to
>> let you know -- more eyes find more bugs...
>
> Here is something fishy I found: after the last `R' command in dired,
> dired-rename-file calls dired-rename-subdir, but the args specified
> are not directories
Right. This always happens:
(defun dired-rename-file (file newname ok-if-already-exists)
(dired-handle-overwrite newname)
(rename-file file newname ok-if-already-exists) ; error is caught in -create-files
;; Silently rename the visited file of any buffer visiting this file.
(and (get-file-buffer file)
(with-current-buffer (get-file-buffer file)
(set-visited-file-name newname nil t)))
(dired-remove-file file)
;; See if it's an inserted subdir, and rename that, too.
(dired-rename-subdir file newname))
Shouldn't dired-rename-subdir be conditioned on either file or newname
being a directory? Or perhaps both? Or shouldn't dired-rename-subdir
take care to do the right thing with non-directories?
I'm getting confused now.
--
~/.signature
next prev parent reply other threads:[~2003-07-06 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 14:30 Bug in Ange-FTP with renaming files Kai Großjohann
2003-07-06 14:48 ` Kai Großjohann
2003-07-06 14:56 ` Kai Großjohann [this message]
2003-07-06 15:10 ` Kai Großjohann
2003-07-06 16:00 ` Kai Großjohann
2003-07-07 3:39 ` Richard Stallman
2003-07-07 5:58 ` Kai Großjohann
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=84isqfsnz1.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).