Opened 12 years ago
Last modified 3 years ago
#16 accepted enhancement
MOVE command is not compatible and needs improvement
Reported by: | D Azarewicz | Owned by: | Gregg Young |
---|---|---|---|
Priority: | major | Milestone: | Version-3.10 |
Component: | Commands | Version: | 3.08 |
Keywords: | Cc: | david@… |
Description
The MOVE command is not compatible with the MOVE command in CMD.EXE.
move \dir1\dir2\dir3 \dir4
should move dir3 to \dir4\dir3 but it does not. It moves files instead of moving the directory.
Also the MOVE command should fail if any arguments are missing.
Change History (4)
comment:1 by , 12 years ago
Milestone: | → Version-3.09 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 6 years ago
Milestone: | Version-3.09 → Version-3.10 |
---|
Ticket retargeted after milestone closed
comment:4 by , 3 years ago
Owner: | changed from | to
---|---|
Status: | assigned → accepted |
Note:
See TracTickets
for help on using tickets.
As I read the command reference the ability of cmd.exe to move directories is an undocumented feature. That said, it might be useful to modify the move command to work like cmd.exe if it can be done without breaking too many existing scripts.
You can use the 4OS2 rename command to move directories. For example
Will do what you want.
It should be possible to define an alias that maps the move to a rename if there are only two arguments and the first argument is a directory.
The existing 4OS2 move command only requires one argument.