6 Jun
2023
6 Jun
'23
12:34 a.m.
On Fri, Jun 2, 2023, at 19:04, segaloco via TUHS wrote:
Finally, this page plainly spells out the history of
the command in the
bugs section:
"This command was written in 2 minutes to delete a particular file that
managed to get an 0200 bit in its name. It should work by printing the
name of each file in a specified directory and requestion a 'y' or
'n'
answer. Better, it should be an option of rm(1). The name is
mnemonic, but likely to cause trouble in the future."
One thing this makes me wonder is why the solution chosen wasn't to make a command
that could *rename* the offending directory entry [which, then, with problematic
characters removed, could be examined before deleting normally].