🚀 go-pugleaf

In article <1992Oct2.133603.28087@linus.mitre.org> djb@bambam.ai.mit.EDU (David J. Braunegg) writes:
>In article <1adeseINNnig@early-bird.think.com> barmar@think.com (Barry Margolin) writes:
>>>In the definition of insert-buffer in simple.el, I suggest replacing
>>>  (interactive "*bInsert buffer: ")
>>>with
>>>  (interactive "*BInsert buffer: ")

>>The interactive "B" code will allow you to specify a nonexistent buffer,

>Or, insert-buffer could be re-written in C instead of elisp.  Then the
>default could be the previous buffer and nonexistent buffers could be
>handled correctly.  The C programming for this is a little beyond me,
>though.

Well, you certainly don't have to go *that* far!  You could also do:

(interactive '(progn
		(barf-if-buffer-read-only)
		(list (read-buffer "Insert buffer: " (other-buffer) t))))

In fact, even without this feature of "interactive", I don't see how
recoding in C would make things any easier than recoding in Lisp to prompt
for the buffer itself (instead of using "interactive").  There are only a
few things in Emacs that you can only do in C code, and prompting for
buffers is not one of them.
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar