#OK, I was feeling bad.
severity 408185 wishlist
thanks
JC> If I shoot myself in the foot, I deserve to get hurt. If I use a random
JC> program without reading its documentation, there's no telling what will
JC> happen. I'd like to know why you think this is a bug, and why you think
JC> it is of severity "important", which means "a bug which has a major
JC> effect on the usability of a package, without rendering it completely
JC> unusable to everyone."
Well dumb me has actually done
# dexconf
several times over the years.
Maybe because every other debian team command
makes backups: xxx-old etc. In fact I can't think of a debian team
command that is as dangerous without any arguments. Even reboot(1) wouldn't
wipe out a (unopened) file.
Anyways
# dexconf --help
doesn't say what will happen if no -o is given.
It looks like it will go to stdout.
Indeed man dexconf doesn't mention the danger on its first page on my
terminal at least.
Indeed, on the first page I see only a little past
More experienced users should feel free to use dexconf-generated
configura‐
tion files as a starting point for their customizations, since
individual
preferences vary greatly.
So I probably felt too free...
Anyway, with no backup, they do
# dexconf
then carefully customize it like that paragraph says, then perhaps
accidentally hit ^P RET causing another
# dexconf
and all is lost.
Anyway, representing the dumber end of the spectrum, I say there
should be more seat belts.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
