ilisp: key-binding conflict with XEmacs

The latest changes to C-c C-f causes a conflict with xemacs as
explained by Aaron.

Kevin

Aaron M. Ucko wrote:
> Package: ilisp
> Version: 5.12.0+cvs.2003.05.19
> Severity: serious
> 
> ilisp's attempts to use C-c C-f as a prefix in the global map run into
> trouble on XEmacs, which evidently binds that combination to
> comint-find-source-code by default.
> 
> This ends up breaking the postinst, which is what led me to discover
> #194095 ;-):
> 
> emacs-package-install: /usr/lib/emacsen-common/packages/install/ilisp xemacs21 emacs20 emacs21 xemacs21 failed at /usr/lib/emacsen-common/emacs-package-install line 30, <TSORT> line 2.
> dpkg: error processing ilisp (--configure):
>  subprocess post-installation script returned error exit status 29
> 
> with /usr/share/xemacs21/site-lisp/ilisp/install.log ending in
> 
> Loading /usr/share/xemacs21/site-lisp/ilisp/ilisp-mnb.elc...
> Invalid prefix keys in sequence: ?\^F, "
"
> xemacs exiting
> .
> 
> and a backtrace of
> 
> Signaling: (error "Invalid prefix keys in sequence" ?\^F "
")
>   define-key(mode-specific-command-prefix "
" switch-to-lisp)
>   ilisp-safe-define-key(mode-specific-command-prefix "b" switch-to-lisp "
")
>   ilisp-bind-ilisp-key-for-map(#<keymap global-map size 606 0x2ff> "b" switch-to-lisp "
")
>   ilisp-bindings()
>   defkey-ilisp([menu-bar lisp] ("Lisp" . #<keymap "Lisp" size 0 0x43e0>))
>   byte-code("..." [lisp-general-menu-map defkey-ilisp [menu-bar lisp] "Lisp" [menu-bar lisp repair] ("Repair Connection" . repair-ilisp) [menu-bar lisp reset] ("Reset Connection" . reset-ilisp) [menu-bar lisp comment-region] ("Comment Region" . comment-region) [menu-bar lisp macroexpand] ("Macroexpand" . macroexpand-lisp) [menu-bar lisp macroexpand-1] ("Macroexpand 1" . macroexpand-1-lisp) [menu-bar lisp set-package] ("Set Lisp Package" . set-package-lisp) [menu-bar lisp set-buffer-package] ("Set Buffer Package" . set-buffer-package-lisp) [menu-bar lisp arglist] ("Arglist" . arglist-lisp) [menu-bar lisp documentation] ("Documentation" . documentation-lisp) [menu-bar lisp describe] ("Describe" . describe-lisp) [menu-bar lisp inspect] ("Inspect" . inspect-lisp) [menu-bar lisp eval-defun] ("Eval Defun" . eval-defun-and-go-lisp) [menu-bar lisp start-inferior-lisp] ("Start Lisp" "Starts an inferior lisp asking for a dialect name" . run-ilisp)] 4)
>   load-internal("/usr/share/xemacs21/site-lisp/ilisp/ilisp-mnb.elc" nil nil nil binary)
>   load("/usr/share/xemacs21/site-lisp/ilisp/ilisp-mnb.elc")
>   byte-compile-file("ilisp-mnb.el" 0)
> [...]
> 
> when I eval ilisp-mak.el by hand.
> 
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux tux 2.4.20 #1 Tue Mar 25 21:04:15 EST 2003 i686
> Locale: LANG=en_US, LC_CTYPE=en_US
> 
> Versions of packages ilisp depends on:
> ii  common-lisp-controller        3.62       This is a Common Lisp source and c
> ii  debconf                       1.2.35     Debian configuration management sy
> ii  emacsen-common                1.4.15     Common facilities for all emacsen.
> 
> * ilisp/fsf-compliant: Yes


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge