Mercurial > hg > xemacs-beta
view etc/toolbar/cut-cap-up.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 | 3ecd8885ac67 |
children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * cut[] = { "33 33 4 1", "X c Gray75 s backgroundToolBarColor", "o c black s foregroundToolBarColor", "O c Gray90", "+ c white", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXoooooXXXXXXXXXXXXXXXXXXXXX", "XXXXXXooXXXooXXXXXXXXXXXXXXXXXXXX", "XXXXXooXXXXXooXXXXXXXXXXoooXXXXXX", "XXXXXoXXXXXXXoXXXXXXXXooOOooXXXXX", "XXXXXooXXXXXoooXXXXXooOOooXXXXXXX", "XXXXXXooXXXoooooXXXoooooXXXXXXXXX", "XXXXXXXoooooXXXooooooXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXo+oXXXXXXXXXXXXXX", "XXXXXXXoooooXXXooooooXXXXXXXXXXXX", "XXXXXXooXXXoooooXXXoooooXXXXXXXXX", "XXXXXooXXXXXoooXXXXXooOOooXXXXXXX", "XXXXXoXXXXXXXoXXXXXXXXooOOooXXXXX", "XXXXXooXXXXXooXXXXXXXXXXoooXXXXXX", "XXXXXXooXXXooXXXXXXXXXXXXXXXXXXXX", "XXXXXXXoooooXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXoXXXXXXXXXXX", "XXXXXXXXXXXoooXXXXXXXoXXXXXXXXXXX", "XXXXXXXXXXoXXXoXoXoXoooXXXXXXXXXX", "XXXXXXXXXXoXXXXXoXoXXoXXXXXXXXXXX", "XXXXXXXXXXoXXXXXoXoXXoXXXXXXXXXXX", "XXXXXXXXXXoXXXoXoXoXXoXXXXXXXXXXX", "XXXXXXXXXXXoooXXXooXXoXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};