-
-
Notifications
You must be signed in to change notification settings - Fork 618
When bulk moving, set destination based on the directory under cursor #2395
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I noticed this the other day. This prompt is inconsistent with other operations e.g. paste and is not very useful. Options:
We could combine the two with an option: marks.bulk.move({opts}) *nvim-tree-api.marks.bulk.move()*
Move all marked nodes to the folder under the cursor.
Uses the parent folder when the cursor is on a file.
Parameters: ~
• {opts} (table) optional parameters
Options: ~
• {prompt} (boolean) prompt for a directory before moving It's a break, but I think it's a reasonable one. What do you reckon @gegoune ? |
I don't mind breaking changes. But if we are breaking do we want to do anything else as well? Do we maybe want to add |
That would be rather useful.
marks.bulk.move({opts}) *nvim-tree-api.marks.bulk.move()*
Move all marked nodes to the folder under the cursor.
Uses the parent folder when the cursor is on a file.
Parameters: ~
• {opts} (table) optional parameters
Options: ~
• {prompt} (boolean) prompt for a directory before moving
• {path} (string) absolute or relative destination path, overriding the node's |
It may be possible to add a |
…logic to the default path resolution; adds bulk_move_get_default_path option
…logic to the default path resolution; adds bulk_move_get_default_path option
Describe the solution you'd like
When using bulk move (
bmv
) to move files, it would be great if the directory on the line where cursor is located would be set automatically in the prompt that appears when initiating bulk move:Currently the prompt is set the current working directory.
Would be awesome, thanks.
The text was updated successfully, but these errors were encountered: