Some ideas for dired-ranger.

[jcguu95]

Hello,

Thanks for gathering hacks for dired. Here are some ideas for dired-ranger. Shouldn't be hard to implement, and I can also do it later if it's needed.

1. Functions to empty, save, and quickly inspect the copy rings and bookmark rings.
2. Functions to let the users select which bookmark to jump to, with shortcut and the path, by ivy-read or some helm technology.
3. While conflicts arise during moving/pasting files, as in ranger ask the users if auto-renaming to files with certain suffix. For example,

with ~/personal/note.md present,
~/note.md -> ~/personal  ==> ~/personal/note.md_

4. Add dired-ranger-symlink and dired-ranger-hardlink.
5. Add dired-ranger-undo and dired-ranger-redo.
6. (optional) Separate the copy-ring and the cut-ring.

[Fuco1]

TBH I've never actually used ranger program so I don't know how things work there. Having said that, I like your ideas.

1 and 2 definitely sound like a good idea, it should be possible to prepare some function to return the data which can then be plugged in into any of these completion frameworks. I'd do it in two steps, first create API on our end to get the data, and second implement the completions. I've actually probably never used the ring functionality myself because currently you just have to remember what is where which is just bad UX and hard to use efficiently.

3 sounds good and I think was suggested before (I have a strong feeling of deja vu).

4 would be extension of the copy/move mechanism, the question is if we want to use the same copy-ring for that.

5 how, would that work exactly? I.e. for a move operation, it would move files back, for copy, it would delete the target?

6 might be useful, but to me personally would probably be too confusing. It can exist as a configurable user option.

[jcguu95]

Glad you like some of them. Do you think it makes sense to rename copy-ring to kill-ring or maybe even just ring?

[Fuco1]

kill-ring already exists for the text, so we probably shouldn't use that as it might be confusing. Just ring seems not descriptive enough. Do you think copy-ring is problematic?

[jcguu95]

copy-ring is a little bit misleading. Currently, it's not just for copying's sake, but also moving's. It will become more confusing after we add more functionalities: symlink, hardlink, inspect.. etc.

How about dired-ranger-kill-ring?