unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "63557@debbugs.gnu.org" <63557@debbugs.gnu.org>
Subject: bug#63557: 26.3; Doc string of `find-file-run-dired'
Date: Thu, 18 May 2023 15:35:03 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488C5061A38705F73FB7B46F37F9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83v8gqw6ut.fsf@gnu.org>

> > Instead of just saying that non-nil allows `find-file' to visit
> > directories, say also (as does (emacs) `Visiting') that otherwise (i.e.,
> > nil) raises an error when the arg is a directory name.
>
> How would you interpret "allows" in any other sense?  What could "does
> not allow" mean when the value is nil?
> IOW, I don't see why would we need to spoon-feed the user in this
> case.  The meaning of nil is crystal clear to me.

That you can't visit a directory is one thing.
That trying to do that raises an error is a
different thing.  Another possible behavior
that doesn't visit a directory is to do nothing.
A third is to show a message, without raising
an error.

Not being able to do something is not the same
as having an error raised if you try to do it.





  reply	other threads:[~2023-05-18 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 19:43 bug#63557: 26.3; Doc string of `find-file-run-dired' Drew Adams
2023-05-18  5:23 ` Eli Zaretskii
2023-05-18 15:35   ` Drew Adams [this message]
2023-05-18 15:46     ` Eli Zaretskii
2023-05-18 16:06       ` Drew Adams

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=SJ0PR10MB5488C5061A38705F73FB7B46F37F9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=63557@debbugs.gnu.org \
    --cc=eliz@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).