Mercurial > hg > xemacs-beta
view etc/toolbar/news-cap-xx.xpm @ 4942:46f0df723e09
(for main branch) Indent all `with-*' expressions correctly
-------------------- ChangeLog entries follow: --------------------
lisp/ChangeLog addition:
2010-01-22 Ben Wing <ben@xemacs.org>
* lisp-mode.el:
* lisp-mode.el (lisp-indent-function):
If the function begins with `with-', assume it is a macro or
special form whose last argument is a body. Call
`lisp-indent-specform' with a flag indicating that it should indent
all arguments as a body instead of with normal (full) indent.
* lisp-mode.el (lisp-indent-specform):
Add an optional flag argument indicating that all non-distinguished
arguments, not just the first, should be indented as a body. This
is useful when the number of distinguished (i.e. pre-body) arguments
isn't known, and is used for this purpose by `lisp-indent-function'.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Fri, 22 Jan 2010 04:18:20 -0600 |
parents | 376386a54a3c |
children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * news_xpm[] = { "33 33 5 1", "X c Gray75 s backgroundToolBarColor", "o c Gray60", "O c white", "+ c gray60", "@ c gray", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXooooooooooXXXXXXXX", "XXXXXooooooooooOOOoOOOoOOoXXXXXXX", "XXXXoooOOOoOoooOoOoOoOOoOo++XXXXX", "XXXXo@oOOooOOooOooOooOooOOo++XXXX", "XXoo@o@oOOOOOOOOOOOOOOOOOOOo+XXXX", "XXo@@o@oOooooooooooooooOooOo++XXX", "XXoo@o@oOOOOOOOOOOOOOOOOOOOOo++XX", "XXoo@@o@oOoOoOoOoooOoOoooooOo++XX", "XXo@o@o@oOOoOooOOOOOOoOooOooOo+XX", "XXooo@@o@oOoooooOoOOooOoooooOo+XX", "XXXo@o@o@oOOooooOOOOOOOOoOooOo++X", "XXXXoo@@o@oOoooooOOooooOoooooo++X", "XXXXo@o@o@oOOooOooOooOoOoooOOo++X", "XXXXXoo@@o@oOoOoooOooooOooOooo+XX", "XXXXXoXo@o@oOoooOoOooooOoooo+++XX", "XXXXXXoXoo@oOoOooooooooo++++++XXX", "XXXXXXXooooooooo++++++++++++++XXX", "XXXXXXXXX++++++++++++++++++XXXXXX", "XXXXXXXXXX+++++++++XXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXoXXXoXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXooXXoXXoXXoXoXoXXooXXXXXXX", "XXXXXXXoXoXoXoXoXoXoXoXoXXXXXXXXX", "XXXXXXXoXoXoXoooXoXoXoXXooXXXXXXX", "XXXXXXXoXXooXoXXXXoXoXXXXoXXXXXXX", "XXXXXXXoXXXoXXooXXoXoXXooXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};