Mercurial > hg > xemacs-beta
view etc/toolbar/folder-up.xpm @ 5070:b0f4adffca7d
fix so that CL docstrings (with &key, etc.) handled properly
-------------------- ChangeLog entries follow: --------------------
lisp/ChangeLog addition:
2010-02-23 Ben Wing <ben@xemacs.org>
* autoload.el:
* autoload.el (make-autoload):
* cl-macs.el (cl-function-arglist):
* cl-macs.el (cl-transform-lambda):
Don't add argument list with the tag "Common Lisp lambda list:";
instead add in "standard" form using "arguments:" and omitting the
function name. Add an arg to `cl-function-arglist' to omit the
name and use it in autoload.el instead of just hacking it off.
* help.el:
* help.el (function-arglist):
* help.el (function-documentation-1): New.
Extract out common code to recognize and/or strip the arglist from
documentation into `function-documentation-1'. Use in
`function-arglist' and `function-documentation'. Modify
`function-arglist' so it looks for the `arguments: ' stuff in all
doc strings, not just subrs/autoloads, so that CL functions get
recognized properly. Change the regexp used to match "arguments: "
specs to allow nested parens inside the arg list (happens when you
have a default value specified in a CL arglist).
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Tue, 23 Feb 2010 01:12:13 -0600 |
| parents | 376386a54a3c |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * folder[] = { "28 28 4 1", "X c Gray75 s backgroundToolBarColor", "o c black", "O c white", "+ c Gray60", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXoXXXXXXXooXXXXXooXXX", "XXXXXoooOoXXXoooOoXXooo+oXXX", "XXXooOOOOooooOOOoooo++++oXXX", "XXXoOOOOOOOOOooo+++++++oXXXX", "XXXXoOOOOOOoo++++++++++oXXXX", "XXXXoOOOOOOo++++ooo+++oXXXXX", "XXXXoOOOOOOo+ooo++++++oXXXXX", "XXXXXoOOOOo+++++++++++oXXXXX", "XXXXXoOOOOo+++oo+++++oXXXXXX", "XXXXXXoOOo++oo+++++oooXXXXXX", "XXXXXXoOOo++++++oooXXXXXXXXX", "XXXXXXoOOo+++oooXXXXXXXXXXXX", "XXXXXXXoo+oooXXXXXXXXXXXXXXX", "XXXXXXXoooXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};