From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 44682@debbugs.gnu.org
Subject: bug#44682: 28.0.50; dired on file with space first: dired-get-file-for-visit: File no longer exists; type ‘g’ to update Dired buffer
Date: Mon, 16 Nov 2020 19:20:49 +0200 [thread overview]
Message-ID: <83zh3hrzf2.fsf@gnu.org> (raw)
In-Reply-To: <courier.000000005FB26EBC.00007261@static.rcdrun.com> (message from Jean Louis on Mon, 16 Nov 2020 15:21:15 +0300)
> Date: Mon, 16 Nov 2020 15:21:15 +0300
> From: Jean Louis <bugs@gnu.support>
>
> The directory folder has probably a space in the name. It is hard to
> know for me who made this directory and how. People are using their
> GUI.
>
> Error in Dired is:
> dired-get-file-for-visit: File no longer exists; type ‘g’ to update Dired buffer
>
> It should be possible to handle such directories.
>
> /scp:root@room:/home/study/Movies:
> total used in directory 879904 available 26.5 GiB
> drwxr-xr-x 2 study study 4096 Nov 14 14:47 folder
> drwxr-xr-x 4 study study 4096 Nov 16 15:17 .
> drwx------ 20 study study 4096 Nov 14 14:47 ..
> C -rw------- 1 study study 901000535 Nov 16 14:41 Ralph Breaks the Internet.mkv
> drwxr-xr-x 2 study study 4096 Sep 21 03:17 Zathura A Space Adventure (2005)
Please tell what you tried that triggered this error, and on which
name in the buffer. Without this information, I don't see how we can
begin investigating. FWIW, directories with embedded spaces work for
me in Dired, at least in general.
next prev parent reply other threads:[~2020-11-16 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 12:21 bug#44682: 28.0.50; dired on file with space first: dired-get-file-for-visit: File no longer exists; type ‘g’ to update Dired buffer Jean Louis
2020-11-16 16:31 ` Drew Adams
2020-11-16 17:45 ` Jean Louis
2020-11-17 17:14 ` Drew Adams
2020-11-16 17:20 ` Eli Zaretskii [this message]
2020-11-16 17:57 ` Jean Louis
2020-11-17 15:05 ` Eli Zaretskii
2020-11-17 9:06 ` Andreas Schwab
2020-11-17 9:46 ` Jean Louis
2020-11-17 20:11 ` Michael Albinus
2020-11-18 10:40 ` Michael Albinus
2020-11-18 13:03 ` Jean Louis
2020-11-18 15:40 ` Michael Albinus
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=83zh3hrzf2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44682@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).