[3408] in SIPB bug reports
xrn kill files
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed Jan 6 15:41:20 1993
Date: Wed, 6 Jan 93 15:40:47 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: jfc@Athena.MIT.EDU
Cc: bug-sipb@Athena.MIT.EDU
In-Reply-To: John Carr's message of Wed, 06 Jan 1993 15:26:59 EST <9301062027.AA02670@Achates.MIT.EDU>
Date: Wed, 06 Jan 1993 15:26:59 EST
From: John Carr <jfc@Athena.MIT.EDU>
>> Not convinced. If it can't do both the "=" and the "j", then doing
>> just the "j" may be worse than not doing anything at all.
Good point. There should be an option to ignore the '=', but I won't
complain if the default is to choke on it.
I'm still not sure this is a good idea.
Right now, the only format that is supported "/foo/opts:x". The
"opts" are ignored, and the "x" can be tierh 'j', 'm', or 's'. If 's'
is specified, it doesn't take a filename.
If it starts noticing commands like '=' and such, should it also start
noticing multiple commands separated by colons? Wht about the options
before the colons? What about file names and such?
The KILl files that xrn supports are much more limited than the rn
functionality. I think it's a mistake to imply otherwise, so I think
it's a mistake to make the code understand more than it does now,
unless it's going to understand *all* the rn kill commands and
options, which I doubt.
If you want rn, use rn :-). Otherwise, perhaps you can tell xrn to
use a different KILL file with just the xrn-understandable commands in
it.
jik
