RE: Suppress user-prompting when calling commands in programs

[Drew Adams]

> > What's wrong with them pushing the read into the interactive spec?
> >
> > (defun foo (&optional arg bar)
> >   (interactive (list current-prefix-arg
> >                      (org-icompleting-read ...))))
> >   ...)
> 
> A quick side-question: Everyone here is using &optional for the prefix
> arg name.

I used &optional because that is what was used in the original `foo'.
Presumably there is existing code that uses `foo' and expects that
signature, e.g., tries to evaluate `(foo)'.

> I have several functions lying around that use the "P"
> interactive spec but don't specify arg as &optional, and seem to work
> fine. My understanding is that, if there is no prefix arg, arg will
> simply be nil, as it should be.

Correct.

> Apart from style/code clarity, are there other reasons for specifying
> &optional?

See above.  Use &optional if you want to be able to call the function
without passing that argument.