Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add copy and move to the list of features #5

Closed
GabeDuarteM opened this issue Sep 18, 2019 · 4 comments 路 Fixed by #7
Closed

Add copy and move to the list of features #5

GabeDuarteM opened this issue Sep 18, 2019 · 4 comments 路 Fixed by #7

Comments

@GabeDuarteM
Copy link

Hey 馃憢馃憢馃憢

It would be good to have also the possibility to move and copy multiple nodes into a new location, that way, we would be able to do most of the important operations that you could do with multiple items (at the moment, you can only open and delete them)

What do you think?

@PhilRunninger
Copy link
Owner

I like the idea. Here are my initial thoughts.

  1. Since we are dealing with multiple items, the destination should be just a single directory.
  2. Each file or folder moved/copied should be confirmed. That way you can, for example, select 5 consecutive nodes and copy all but the 3rd.
  3. Add a way to pre-select the destination folder, or at least most of it.

Here is an example of how I see all of this playing out.

  1. Navigate to destination folder.
  2. D This is the plugin's keystroke for marking the Destination. I plan no visual indicator for this.
  3. V5j (Navigate to and) select six source file/folders.
  4. m Move files/folders.
  5. Plugin presents a prompt with pre-selected destination folder (or if a file was pre-selected, its path). This allows the user to add subfolders if necessary. If the destination wasn't preselected, show the folder of the first node.
  6. Enter Start moving the files.
  7. Answer the [Y]es, (N)o, (A)ll, (C)ancel: prompt for each file/folder.

@GabeDuarteM
Copy link
Author

  1. Yeah, sounds reasonable
  2. Initially, I thought about only one confirmation, but this use case sounds reasonable too, especially when we have an (A)ll option...
  3. My initial idea was to just follow what NERDTree is doing today when you move/copy a single item, showing you an Enter the new path for the node:, passing the parent of the selected files as the default, and letting you use the autocomplete to select the final destination (automatically creating the parts that do not exist, if you want to move to a new inexistent folder). I think the D mapping could be useful when you want to move the file to somewhere far from where it currently is, but when it's close, I think nerdtree's behavior is probably faster than preselecting with D, so I think it would be nice to have both behaviors available, so on step 5 of your example, you would have the option to change the default path (which is either the folder of the first node, or the selected folder with the D map), and allowing to use autocomplete, as it currently happens with nerdtree

image

@Nnoerregaard
Copy link

Any progress on this issue? I would love the ability to move and copy multiple files at a time in NerdTREE

@PhilRunninger
Copy link
Owner

Not yet. I haven't had the time to look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants