Re: Deleting broken in Python, or why delete-key-deletes-forward sucks

Hrvoje> The standard XEmacs way of recognizing this can Hrvoje> look like this: Somewhere along the way (possibly b/w XEmacs 20 and 21, possibly after I unsub'd from the list ;-) the blessed way of doing this changed. I made the change in CC Mode, but never made it in python-mode. See the attached patch. Thanks for helping be uncover a bug in my Exceed setup, and Hrvoje, it's good to see you hacking Python! :-) If this patch works for you, I'll check it in and do a new release. -Barry -------------------- snip snip -------------------- Index: python-mode.el =================================================================== RCS file: /projects/cvsroot/python/dist/src/Misc/python-mode.el,v retrieving revision 3.91 diff -c -r3.91 python-mode.el *** python-mode.el 1999/01/09 17:22:38 3.91 --- python-mode.el 1999/01/15 01:41:57 *************** *** 1519,1528 **** \\[universal-argument] (programmatically, argument ARG) specifies the number of characters to delete (default is 1)." (interactive "*p") ! (if (and (boundp 'delete-key-deletes-forward) ! delete-key-deletes-forward) (funcall py-delete-function arg) - ;; else (py-electric-backspace arg))) ;; required for pending-del and delsel modes --- 1519,1529 ---- \\[universal-argument] (programmatically, argument ARG) specifies the number of characters to delete (default is 1)." (interactive "*p") ! (if (or (and (fboundp 'delete-forward-p) ;XEmacs 21 ! (delete-forward-p)) ! (and (boundp 'delete-key-deletes-forward) ;XEmacs 20 ! delete-key-deletes-forward)) (funcall py-delete-function arg) (py-electric-backspace arg))) ;; required for pending-del and delsel modes