RE: Making `interactive' conditional

[Herring, Davis]

> (and (not read-only) visiting-file)

So now you can't invoke it in *scratch*?

Of course, you can come up with another refinement to the condition (e.g., 
mode-class).  My point is merely that writing these predicates is very subtle 
when the standard is not "is this command likely to work when invoked" (in 
which case you wouldn't be bothering with "visiting-file") but rather "is the 
user plausibly looking for this command in the list".

Davis