> Isn't that backwards-incompatible?

This is an interactive function, I think, so backward compatibility is a loose concept here. I can add a configuration variable if you think this matters.

> similar features in other completion frameworks

I don't know if `ivy` has this, but anyway, I try to keep this kind of hotkeys to a minimum; They are easy to forget, they are not ergonomic, and I have only five fingers from birth, which doesn't help. Why would I want a hotkey when I can perfectly achieve what I need without one, and without losing any functionality?

Besides, the point is moot, as dired already exposes `dired-create-destination-dirs', so it is not delegating this feature. So it might as well do it right.

On Tue, Sep 28, 2021 at 9:47 PM Stefan Kangas <stefankangas@gmail.com> wrote:

Rudi C <rudiwillalwaysloveyou@gmail.com> writes:

> With this patch, we can move directories into new directories if we
> explicitly end the new name with a trailing slash.
>
> So `/new_name` renames `/old_name` to `/new_name`, while `/new_name/`
> renames `/old_name` to `/new_name/old_name`.

Isn't that backwards-incompatible?

> Without this feature, one has to first create the new directory and then
> move the old directory into it, which is so unpleasant I currently just
> copy the path and use my shell's move functions.

IIRC, if you use e.g. `ido', you can create a directory from the prompt
with M-m. I'm not sure about the default completion, but there are
similar features in other completion frameworks. Isn't that a better
way to go about this?