* bug#63557: 26.3; Doc string of `find-file-run-dired'
@ 2023-05-17 19:43 Drew Adams
2023-05-18 5:23 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Drew Adams @ 2023-05-17 19:43 UTC (permalink / raw)
To: 63557
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.
In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.19045
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#63557: 26.3; Doc string of `find-file-run-dired'
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
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2023-05-18 5:23 UTC (permalink / raw)
To: Drew Adams; +Cc: 63557
> From: Drew Adams <drew.adams@oracle.com>
> Date: Wed, 17 May 2023 19:43:17 +0000
>
> 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#63557: 26.3; Doc string of `find-file-run-dired'
2023-05-18 5:23 ` Eli Zaretskii
@ 2023-05-18 15:35 ` Drew Adams
2023-05-18 15:46 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Drew Adams @ 2023-05-18 15:35 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 63557@debbugs.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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#63557: 26.3; Doc string of `find-file-run-dired'
2023-05-18 15:35 ` Drew Adams
@ 2023-05-18 15:46 ` Eli Zaretskii
2023-05-18 16:06 ` Drew Adams
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2023-05-18 15:46 UTC (permalink / raw)
To: Drew Adams; +Cc: 63557-done
> From: Drew Adams <drew.adams@oracle.com>
> CC: "63557@debbugs.gnu.org" <63557@debbugs.gnu.org>
> Date: Thu, 18 May 2023 15:35:03 +0000
>
> > > 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.
The doc string says "allows", not "can".
> 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.
You are splitting hair for no good reason.
Closing.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#63557: 26.3; Doc string of `find-file-run-dired'
2023-05-18 15:46 ` Eli Zaretskii
@ 2023-05-18 16:06 ` Drew Adams
0 siblings, 0 replies; 5+ messages in thread
From: Drew Adams @ 2023-05-18 16:06 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 63557-done@debbugs.gnu.org
> > That you can't visit a directory is one thing.
>
> The doc string says "allows", not "can".
That you're not allowed to visit a directory is
one thing. That an error is raised is another.
> > 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.
>
> You are splitting hair for no good reason.
Tell that to the manual, which rightfully makes
clear that an error is raised.
Ask yourself if you're perhaps refusing a simple
doc fix for no good reason.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-05-18 16:06 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2023-05-18 15:46 ` Eli Zaretskii
2023-05-18 16:06 ` Drew Adams
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).