Mercurial > hg > xemacs-beta
view etc/toolbar/replace-up.xpm @ 5693:4d15e903800b
Be more careful about erroring with probable GNU-syntax keysyms, keymap.c
src/ChangeLog addition:
2012-11-06 Aidan Kehoe <kehoea@parhasard.net>
* keymap.c (define_key_check_and_coerce_keysym):
When worrying about GNU Emacs-like keysym syntax, if the symbol
name starts with c-whatever (or s-whatever, or m-whatever), check
for a function binding for that before erroring. Otherwise command
remapping and C mode interact badly, since most of the C mode
commands are regarded as GNU Emacs-style keysyms.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Tue, 06 Nov 2012 22:33:58 +0000 |
| parents | 7910031dd78a |
| children |
line wrap: on
line source
/* XPM */ /* This file is part of XEmacs. XEmacs is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. XEmacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with XEmacs. If not, see <http://www.gnu.org/licenses/>. */ static char * replace[] = { "28 28 2 1", "X c Gray75 s backgroundToolBarColor", "o c black s foregroundToolBarColor", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXooXXXXooooXXXXXXXXXXXX", "XXXXXXooXXXXooXXoXXXXXXXXXXX", "XXXXXoXooXXXooXXoXXXXXXXXXXX", "XXXXXoXooXXXoooooXXXXXXXXXXX", "XXXXoXXXooXXooXXXoXXoooXXXXX", "XXXXooooooXXooXXXoXXooXXXXXX", "XXXoXXXXXooXooXXXoXXoXoXXXXX", "XXXoXXXXXooXoooooXXXXXXoXXXX", "XXXXXXXXXXXXXXXXXXXXXXXoXXXX", "XXXXXXXXXXXXoXXXXXXXXXXoXXXX", "XXXXXXXXXXXoXXXXXXXXXXXoXXXX", "XXXXXXXXXXXoXXXXXXXXXXoXXXXX", "XXXXXXXXXXoXXXXXXXXXXoXXXXXX", "XXXXXXXXXoXXXXXXXXXXXXXXXXXX", "XXXXXXXXXoXXXXXXooooXXXXXXXX", "XXXXXXXXoXXXXXXooXXXoXXXXXXX", "XXXXXoXoXXXXXXXooXXXXXXXXXXX", "XXXXXooXXXXXXXXooXXXXXXXXXXX", "XXXXXooooXXXXXXooXXXXXXXXXXX", "XXXXXooXXXXXXXXooXXXXXXXXXXX", "XXXXXXXXXXXXXXXooXXXoXXXXXXX", "XXXXXXXXXXXXXXXXooooXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};