From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 58364@debbugs.gnu.org
Subject: bug#58364: [PATCH] Add new function 'file-name-parent-p'
Date: Sat, 08 Oct 2022 11:01:56 +0300 [thread overview]
Message-ID: <83fsfylp57.fsf@gnu.org> (raw)
In-Reply-To: <87sfjy93xe.fsf@posteo.net> (message from Philip Kaludercic on Sat, 08 Oct 2022 07:21:01 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: 58364-done@debbugs.gnu.org
> Date: Sat, 08 Oct 2022 07:21:01 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Date: Fri, 07 Oct 2022 20:23:27 +0000
> >>
> >> Unless I am mistaken, there is no direct function to quickly test if a
> >> directory is a super-directory of file. As I have encountered this
> >> issue more than once the last few days of hacking, I would like to
> >> propose the below function.
> >
> > We have file-in-directory-p. Doesn't that fit the bill?
>
> I hive tried it out and yes that was the function I was looking for. My
> apologies for the noise.
No need to apologize: no one can know and remember everything. I only
remembered that because I recently fixed a bug in Dired which used
that function.
But perhaps our take from this is that file-in-directory-p is not
discoverable enough? Can you describe how and where you looked for
this functionality? Maybe if we know that, we could make some changes
to have this function pop up in similar searches.
next prev parent reply other threads:[~2022-10-08 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 20:23 bug#58364: [PATCH] Add new function 'file-name-parent-p' Philip Kaludercic
[not found] ` <handler.58364.B.16651742163752.ack@debbugs.gnu.org>
2022-10-07 20:46 ` bug#58364: Acknowledgement ([PATCH] Add new function 'file-name-parent-p') Philip Kaludercic
2022-10-07 21:10 ` bug#58364: [PATCH] Add new function 'file-name-parent-p' Drew Adams
2022-10-08 6:17 ` Eli Zaretskii
2022-10-08 7:21 ` Philip Kaludercic
2022-10-08 8:01 ` Eli Zaretskii [this message]
2022-10-08 9:23 ` Philip Kaludercic
2022-10-08 10:10 ` Eli Zaretskii
2022-10-08 10:29 ` Philip Kaludercic
2022-10-08 11:16 ` Eli Zaretskii
2022-10-08 17:20 ` 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=83fsfylp57.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58364@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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).