Re: xft xemacs & x resources

Ar an chéad lá de mí Márta, scríobh giacomo boffi: I’m not sure of this--I get configure.ac:1052: error: possibly undefined macro: AC_DEFINE_UNQUOTED If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. with autoconf 2.59 . With the old configure file, no, you couldn’t configure the name of the executable to be installed--in this case, that shouldn’t really be an issue. An install of the latest trunk will overwrite xemacs, but only with a symbolic link to xemacs-21.5-b19; xemacs-21.5-b18, the XFT build, should still be there. Index: x-init.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/x-init.el,v retrieving revision 1.13 diff -u -u -r1.13 x-init.el --- x-init.el2002/06/20 21:18:051.13 +++ x-init.el2005/03/01 11:41:36 ＠＠ -41,7 +41,7 ＠＠ ;; If you want to change this variable, this is the place you must do it. ;; Do not set it to a string containing periods. X doesn't like that. -;(setq x-emacs-application-class "Emacs") +(setq x-emacs-application-class "XFTEmacs") (defgroup x nil "The X Window system." recompile, and then run xemacs-21.5-b18 -name XFTXEmacs. All the XFT branch resources will have to start with XFTXEmacs instead of XEmacs. XFT probably won’t ever receive the status of b19, if I understand it correctly; by the time it’s merged into the trunk, we’ll have another beta version. That said, yes, there’s a distinct possibility for conflict there. -- “I, for instance, am gung-ho about open source because my family is being held hostage in Rob Malda’s basement. But who fact-checks me, or Enderle, when we say something in public? No-one!” -- Danny O’Brien