From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 60562@debbugs.gnu.org, lx@shellcodes.org
Subject: bug#60562: [PATCH] Fix split-string error if there is a space in the filename.
Date: Sat, 07 Jan 2023 13:37:54 +0200 [thread overview]
Message-ID: <83pmbqshgt.fsf@gnu.org> (raw)
In-Reply-To: <87r0w6h9w8.fsf@gmail.com> (message from Robert Pluim on Sat, 07 Jan 2023 12:16:55 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: lx@shellcodes.org, 60562@debbugs.gnu.org
> Date: Sat, 07 Jan 2023 12:16:55 +0100
>
> >>>>> On Sat, 07 Jan 2023 11:29:58 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> >> (which is annoyingly
> >> hard to remember, since the obvious search leads to
> >> `list-directory'. Perhaps we should add `list-directory-recursively'
> >> as an alias?)
>
> Eli> How did you search for it?
>
> I use helm, which does subword searching, so
>
> C-h f list dir
I was about to suggest "M-x apropos-documentation RET list dir RET",
but I see now that for some strange reason (bug?) it doesn't catch
directory-files-recursively, although its doc string does match.
next prev parent reply other threads:[~2023-01-07 11:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 22:56 bug#60562: [PATCH] Fix split-string error if there is a space in the filename lux
2023-01-06 9:48 ` Robert Pluim
2023-01-07 9:29 ` Eli Zaretskii
2023-01-07 11:16 ` Robert Pluim
2023-01-07 11:37 ` Eli Zaretskii [this message]
2023-01-07 13:56 ` Eli Zaretskii
2023-01-07 14:52 ` lux
2023-01-07 23:00 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-08 7:23 ` lux
2023-01-09 14:28 ` Robert Pluim
2023-01-09 14:55 ` lux
2023-01-14 9:12 ` Eli Zaretskii
2023-01-07 9:42 ` lux
2023-01-07 10:48 ` Eli Zaretskii
2023-01-15 12:33 ` Andy Moreton
2023-01-15 14:07 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pmbqshgt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60562@debbugs.gnu.org \
--cc=lx@shellcodes.org \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.