You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Move to: /path/to/directory/where/cursor/is
Currently the prompt is set the current working directory.
I noticed this the other day. This prompt is inconsistent with other operations e.g. paste and is not very useful.
Options:
Set the path based on the node as above
Just move without a prompt
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 ?
But if we are breaking do we want to do anything else as well? Do we maybe want to add path that will move files to that directory. Not sure how useful it is. Actually, adding it later wouldn't really be a breaking change, would it?
Do we maybe want to add path that will move files to that directory. Not sure how useful it is.
That would be rather useful.
opts can always be added to later without breaking, however it would be convenient to just do it now.
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
Activity
alex-courtis commentedon Sep 2, 2023
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:
It's a break, but I think it's a reasonable one. What do you reckon @gegoune ?
gegoune commentedon Sep 2, 2023
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
path
that will move files to that directory. Not sure how useful it is. Actually, adding it later wouldn't really be a breaking change, would it?alex-courtis commentedon Sep 3, 2023
That would be rather useful.
opts
can always be added to later without breaking, however it would be convenient to just do it now.alex-courtis commentedon Sep 3, 2023
It may be possible to add a
path
tofs.paste
however I think I'm feature creeping here.feat(nvim-tree#2395): changes bulk_move to allow users to add custom …
feat(nvim-tree#2395): changes bulk_move to allow users to add custom …
feat(nvim-tree#2395): extends default bulk.move functionality with pr…
feat(nvim-tree#2395): extends default bulk.move functionality with pr…
fix(nvim-tree#2395): marks.bulk.move defaults to directory at cursor
fix(nvim-tree#2395): marks.bulk.move defaults to directory at cursor
fix(nvim-tree#2395): adds check if node_at_cursor.parent is nil
fix(#2395): marks.bulk.move defaults to directory at cursor (#2688)
1 remaining item