Mercurial > hg > xemacs-beta
view etc/toolbar/folder-cap-xx.xpm @ 4367:69e6352406f0
Handle macros, autoloads correctly in symbol-file. Add an incomplete TYPE arg.
src/ChangeLog addition:
2007-12-30 Aidan Kehoe <kehoea@parhasard.net>
* doc.c (Fbuilt_in_symbol_file):
Take a new TYPE argument, specifying whether the function or
variable definition of the symbol should be searched for.
Handle built-in macros correctly.
lisp/ChangeLog addition:
2007-12-30 Aidan Kehoe <kehoea@parhasard.net>
* loadhist.el (symbol-file):
Accept a new TYPE argument, compatible with GNU, saying
whether function or variable definitions should be searched for.
Implement the functionality for autoloads, handling TYPE
correctly.
Pass the TYPE argument to built-in-symbol-file correctly.
Document that TYPE is not implemented for non-autoloaded Lisp
definitions. Our load-history doesn't have the relevant metadata.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Sun, 30 Dec 2007 15:33:13 +0100 |
| parents | 376386a54a3c |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * folder[] = { "33 33 4 1", "X c Gray75 s backgroundToolBarColor", "o c Gray60", "O c white", "+ c Gray60", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXoXXXXXXXooXXXXXooXXXXX", "XXXXXXXXoooOoXXXoooOoXXooo+oXXXXX", "XXXXXXooOOOOooooOOOoooo++++oXXXXX", "XXXXXXoOOOOOOOOOooo+++++++oXXXXXX", "XXXXXXXoOOOOOOoo++++++++++oXXXXXX", "XXXXXXXoOOOOOOo++++ooo+++oXXXXXXX", "XXXXXXXoOOOOOOo+ooo++++++oXXXXXXX", "XXXXXXXXoOOOOo+++++++++++oXXXXXXX", "XXXXXXXXoOOOOo+++oo+++++oXXXXXXXX", "XXXXXXXXXoOOo++oo+++++oooXXXXXXXX", "XXXXXXXXXoOOo++++++oooXXXXXXXXXXX", "XXXXXXXXXoOOo+++oooXXXXXXXXXXXXXX", "XXXXXXXXXXoo+oooXXXXXXXXXXXXXXXXX", "XXXXXXXXXXoooXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXoXXXXXXXXXXXoXXXXXX", "XXXXXXXXooooXXXXXXXXXXXXXXoXXXXXX", "XXXXXXXXoXXXoXoXoXoXoXXXoooXXXXXX", "XXXXXXXXoXXXoXoXooXoXoXoXXoXXXXXX", "XXXXXXXXoXXXoXoXoXXoooXoXXoXXXXXX", "XXXXXXXXoXXXoXoXoXXoXXXoXXoXXXXXX", "XXXXXXXXooooXXoXoXXXooXXoooXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};