Re: del command and auto-named file disaster
- From: "Pegasus [MVP]" <news@xxxxxxxxxxxxx>
- Date: Thu, 6 Aug 2009 07:36:45 +0200
"Deniz" <deniz.turkmen@xxxxxxxxx> wrote in message
news:f00e3721-1378-427a-8878-adcba865d67d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
OK maybe I should have known better, but I still believe this should
be avoidable in OS/FS level.
As you know Windows file system names the copy of a file as "Copy of
FILENAME" by default. When I need to update an important file, I
simply create a copy and work on the original. If anything goes bad, I
still have the original file "Copy of FILENAME". If everything works,
I don't need the duplicate so I delete the copy. This works perfectly
until I delete the file in command line without quotes!
dirFILENAME
Copy of FILENAME
del Copy of FILENAME
Can you guess which file has been deleted? Hint: Delete command looked
for 3 files, not one. (hand-palm)
Lesson learned in a hard way. To avoid future disasters, is there
anything I can do e.g. a Windows tweak that allows Delete command to
send the file to Recycle Bin instead of wiping completely? Or making
Delete prompt me by default? Or even more hardcore, changing the
default auto-naming convention?
Thanks in advance.
Windows Explorer has a GUI. It is designed for users and has the safety net
of the Recycle Bin.
The console is for administrators, not for users. It has no safety net. When
you delete a file then it gets well and truly deleted. If you need a safety
net then you must use Windows Explorer.
.
- References:
- del command and auto-named file disaster
- From: Deniz
- del command and auto-named file disaster
- Prev by Date: del command and auto-named file disaster
- Next by Date: fixing key for windows xp
- Previous by thread: del command and auto-named file disaster
- Next by thread: fixing key for windows xp
- Index(es):
Relevant Pages
|
Loading