Mercurial > hg > xemacs-beta

view etc/toolbar/compile-up.xpm @ 5069:14f0dd1fabdb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
move test-harness to lisp/ directory so it gets byte-compiled -------------------- ChangeLog entries follow: -------------------- etc/ChangeLog addition: 2010-02-22 Ben Wing <ben@xemacs.org> * dbxrc.in: test-harness.el is in lisp directory now. lisp/ChangeLog addition: 2010-02-22 Ben Wing <ben@xemacs.org> * test-harness.el: * test-harness.el (test-harness-from-buffer): * test-harness.el (batch-test-emacs): Move file from tests/automated into lisp/ so it gets byte-compiled. This significantly reduces the amount of extra crap in outputted backtraces. Delete hack in batch-test-emacs to look for test-harness.el in the test directory since it's not there any more. Also, in `Check-Message', incorporate call to `Skip-Test-Unless' in the macro output rather than its body, to avoid problems byte- compiling the file -- `Skip-Test-Unless' isn't available in the environment during byte-compilation so we can't call it then. src/ChangeLog addition: 2010-02-22 Ben Wing <ben@xemacs.org> * .gdbinit.in.in: * Makefile.in.in (batch_test_emacs): test-harness.el is in lisp directory now so change how we call it.
author Ben Wing <ben@xemacs.org>
date Mon, 22 Feb 2010 22:04:55 -0600
parents 376386a54a3c
children 7910031dd78a
line wrap: on
line source

/* XPM */
static char * makefile[] = {
"28 28 6 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c black",
"O	c white",
"+	c Gray40",
"@	c Gray90",
"#	c white",
"XXXXXXXXXoooXXXXXXXXXXXXXXXX",
"XXXXXXXoooOoooXXXXXXXXXXXXXX",
"XXXXXXXo++o++oXXXXXXXXXXXXXX",
"XXXXXXoo+ooo+ooXXXXXXXXXXXXX",
"XXXXXXo++o++++oXXXXXXXXXXXXX",
"XXXXXXoo++o++ooXXXXXXXXXXXXX",
"XXXXXXXo+++++ooooXXXXXXXXXXX",
"XXXXXXXooo+oooo@oXXoXXXXXXXX",
"XXXXXXXXXooo@o@@@oo@oXXXXXXX",
"XXXXXXXXXo@@@@@@@@@@ooXXXXXX",
"XXXXXXXXXXo@@@ooo@@@oXXXXXXX",
"XXXXXXXXXXo@@o@o#o@@oXXXXXXX",
"XXXXXXXXoo@@o@o###o@@ooXXXXX",
"XXXXXXXXo@@@oo####o@@@oXXXXX",
"XXXXXXXXooo@o@o###o@oooXXXXX",
"XXXXXXXXXXo@@o@o#o@@oXXXXXXX",
"XXXXXXXXXXo@@@ooo@@@oXXXXXXX",
"XXXXXXXXXo@@@@@@@@@@@oXXXXXX",
"XXXXXXXXXoo@oo@@oooooXXXXXXX",
"XXXXXXXoooXooo@@oXXoXXXXXXXX",
"XXXXXXXo++o++ooooXXXXXXXXXXX",
"XXXXXXoo+ooo+ooXXXXXXXXXXXXX",
"XXXXXXo++o++++oXXXXXXXXXXXXX",
"XXXXXXoo++o++ooXXXXXXXXXXXXX",
"XXXXXXXo+++++oXXXXXXXXXXXXXX",
"XXXXXXXooo+oooXXXXXXXXXXXXXX",
"XXXXXXXXXoooXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};