Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!smithln
From: smithln@rochester.arpa (Neil Smithline)
Newsgroups: comp.emacs
Subject: Re: Improvement Suggestion for Gnu Emacs online documentation
Message-ID: <827@sol.ARPA>
Date: Tue, 28-Jul-87 15:42:13 EDT
Article-I.D.: sol.827
Posted: Tue Jul 28 15:42:13 1987
Date-Received: Thu, 30-Jul-87 01:18:39 EDT
References: <588@hplabsz.HPL.HP.COM>
Reply-To: smithln@rochester.UUCP (Neil Smithline)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 30

In article <588@hplabsz.HPL.HP.COM> mayer@hplabsz.UUCP (Niels Mayer) writes:
#
#It would be really nice if the help-function documentation in gnuemacs
#would show the list of parameters to a function in addition to a
#description of the parameters.... When I called up documentation on
#"call-process" I got the following:
# ....
#The above documentation would've been made much more useful f it had been
#prefixed with
#   usage: (call-process <PROGRAM> <INFILE> <BUFFER> <DISPLAY> <arg1 ... argN>)
#since nothing in the documentation explicitly tells me what the order of
#the arguments are. (<BUFFER>, for example, is mentioned twice in the
#documentation text above, before <DISPLAY>)

I have to disagree with you.  This comment does provide full
information on the order of the arguments.  The first one mentioned is
the first argument, the second *unique* argument is the second one and
so on.  It is obvious that there are not two arguments called 
<BUFFER> - if there were then one would be called <BUFFER1> and the
other <BUFFER2> or something like that.

Neil Smithline
ARPA:    smithln@cs.rochester.edu
UUCP:    ..!{allegra,decvax,seismo}!rochester!smithln 
Mail:    CS Dept., University of Rochester, Rochester NY 14627
-- 
Neil Smithline
ARPA:    smithln@cs.rochester.edu
UUCP:    ..!{allegra,decvax,seismo}!rochester!smithln 
Mail:    CS Dept., University of Rochester, Rochester NY 14627