unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 17 Nov 2020 17:05:03 +0200	[thread overview]
Message-ID: <83wnykqb1c.fsf@gnu.org> (raw)
In-Reply-To: <X7K9nR7FHstHyRvY@protected.rcdrun.com> (message from Jean Louis on Mon, 16 Nov 2020 20:57:49 +0300)

> Date: Mon, 16 Nov 2020 20:57:49 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 44682@debbugs.gnu.org
> 
> > 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.
> 
> The buffer is on the above /scp:root@room:/home/study/Movies:
> 
> At first line there is folder indented for one space to the
> right. Cursor is on that line.
> 
> If I press RET on that line I got that error:
> 
> dired-get-file-for-visit: File no longer exists; type ‘g’ to update Dired buffer
> 
> Typing g does does not help.
> 
> Space is at beginning of file, not in the middle of file.

Thanks, I think now we have enough details to investigate.





  reply	other threads:[~2020-11-17 15:05 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
2020-11-16 17:57   ` Jean Louis
2020-11-17 15:05     ` Eli Zaretskii [this message]
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=83wnykqb1c.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).