unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 53524@debbugs.gnu.org
Subject: bug#53524: 27.2; No error for creation of Dired listing with nonexistent files/dirs
Date: Tue, 25 Jan 2022 16:03:41 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488958D93A25C092E3A7824F35F9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)

Bug #18836 was fixed in a minimal way: just raising an error for a
nonexistent file or directory when you try to create a Dired buffer
listing that contains it.

As mentioned in that bug report, it would be more user-friendly and more
useful to let you create the Dired buffer, and raise the error only
if/when you later try to access the file or directory, if it still does
not exist.  Better yet (if it still doesn't exist) is to ask if you want
to create it then, instead of just raising an error.

IOW, late binding, please.  There's no reason to just error out because
a single file or dir in the requested listing doesn't exist yet.  You
should be able to create the listing, and later (with or without Dired)
create the missing file or dir.

As stated in bug #18836:

  Let user attempts to actually access it raise an error, and let
  no error be raised if the file is created after creating the
  Dired buffer but before the user tries to access the file.

In GNU Emacs 27.2 (build 1, x86_64-w64-mingw32)
 of 2021-03-26 built on CIRROCUMULUS
Repository revision: deef5efafb70f4b171265b896505b92b6eef24e6
Repository branch: HEAD
Windowing system distributor 'Microsoft Corp.', version 10.0.19043
System Description: Microsoft Windows 10 Pro (v10.0.2009.19043.1466)






                 reply	other threads:[~2022-01-25 16:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=SJ0PR10MB5488958D93A25C092E3A7824F35F9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=53524@debbugs.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).