Mercurial > hg > xemacs-beta
view etc/toolbar/info-def-cap-xx.xpm @ 5076:d555581e3cba
fix issues with display of argument docstrings
-------------------- ChangeLog entries follow: --------------------
lib-src/ChangeLog addition:
2010-02-25 Ben Wing <ben@xemacs.org>
* make-docfile.c:
* make-docfile.c (write_c_args):
Convert newlines to spaces so that argument lists are always on one
line, because that's what function-documentation-1 expects.
lisp/ChangeLog addition:
c2010-02-25 Ben Wing <ben@xemacs.org>
* autoload.el (make-autoload):
Call cl-function-arglist with one arg.
* cl-macs.el (cl-function-arglist):
* cl-macs.el (cl-transform-lambda):
Make cl-function-arglist take only one arg, the arglist; no
function name passed. Also make sure to print () instead of nil
when empty arglist, or function-documentation-1 won't recognize
the arguments: line.
* help.el (function-arglist): If empty arg, don't display extra
space after function name.
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Thu, 25 Feb 2010 04:10:52 -0600 |
| parents | 376386a54a3c |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * info[] = { "33 33 2 1", "X c Gray75 s backgroundToolBarColor", "o c Gray60", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXoXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXoooooooXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXoXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXooooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXoooooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoooooXXXXXXXXXXXXXX", "XXXXXXXXXXXXXoooooooXXXXXXXXXXXXX", "XXXXXXXXXXXXoooooooooXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXoXXXXXXXXXXXXX", "XXXXXXXXXXoXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXoXoooXXoooXooXXXXXXXXXX", "XXXXXXXXXXoXoXXoXXoXoXXoXXXXXXXXX", "XXXXXXXXXXoXoXXoXXoXoXXoXXXXXXXXX", "XXXXXXXXXXoXoXXoXXoXoXXoXXXXXXXXX", "XXXXXXXXXXoXoXXoXXoXXooXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};