Stephan Beal <[email protected]> wrote: > > IMO, duplicating the shell functionality is the wrong approach, mainly > because there will be behavioural differences between fossil's and the > shell's globbing. i agree it would be convenient for us users, but it > technically could not be guaranteed to behave the same as the user's shell, > and therefore could cause confusion or even data loss (e.g. accidental > removal or even purging by using an incompatible glob pattern). >
While I agree that we should not get into globbing and making the user do '*.c' I do think we should allow the option of making fossil mv and fossil rm actually move or remove the file. That is 'semi-shell' functionality added. Almost every single time I use fossil rm or fossil mv, I do: C:\Development\MyProject> fossil rm abc.c DELETED abc.c C:\Development\MyProject> del abc.c C:\Development\MyProject> If it were a config option, then there wouldn't be troubles like this (I don't think). The user should be able to override the default option via a command line argument, maybe: $ fossil rm --no-action abc.c def.xyz $ fossil mv --no-action abc.d 123.789 Jeremy _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
