> Your statement about browsing to find a file "should not be required
> if the file is in the path somewhere" is not correct.
Several replies pointed you to the command sequence -insert
=, a the age-old method of redefining a block with
respect to an external file. One suggestion gave a variant, namely -insert
=~ which will bring up a dialog to browse for the external file.
If the external file is on the search path, then it can be inserted by
entering its name alone, as in the first syntax. Since you know the name of
the block that needs to be updated, and you presumably know it's on your
path if it's part of a standard block library, then manually browsing to
identify the file, as in the second syntax, isn't necessary. Like I said.
And like you did. I note that you didn't do this in your "initial" pass at
the code, and stated "I'm not dealing with the browse step." In fact, my
statement was and is correct, and your code reflects it.
> As for your comment about ^c^c having no meaning in lisp I shall refrain
> from embarrasing you publicly.
Go ahead, I can take it! Hint: if you want to know the "meaning" of a thing
in lisp, you can use the evaluation function, as in (eval ^c).
It evaluates to the same thing as %#$& or any other symbol which has not
been bound to a value, namely nil, which is about as close as you can come
to "having no meaning" in lisp. Using an explicit nil as in (command nil)
would be better coding practice than using a random series of characters
which evaluates to nil, for clarity if nothing else. Calling (command) with
no arguments, however, is a more conventional way of cancelling a command
sequence in lisp.