From xemacs-m  Fri Jul 25 03:36:20 1997
Received: from inf.enst.fr (pQxvT/tDhW6QNi/Ht7s1E0uAwOkHhAfP@inf.enst.fr [137.194.2.81])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id DAA10328
	for <xemacs-beta@xemacs.org>; Fri, 25 Jul 1997 03:36:14 -0500 (CDT)
Received: from metheny.enst.fr (metheny.enst.fr [137.194.160.27])
          by inf.enst.fr (8.8.4/8.8.4) with ESMTP
	  id KAA28286 for <xemacs-beta@xemacs.org>; Fri, 25 Jul 1997 10:36:10 +0200 (MET DST)
Received: (from verna@localhost)
          by metheny.enst.fr (8.8.4/8.8.4)
	  id KAA24162; Fri, 25 Jul 1997 10:36:07 +0200 (MET DST)
Date: Fri, 25 Jul 1997 10:36:07 +0200 (MET DST)
Message-Id: <199707250836.KAA24162@metheny.enst.fr>
From: Didier Verna <verna@inf.enst.fr>
MIME-Version: 1.0
To: xemacs-beta@xemacs.org
Subject: Re: b14 -- Mule: Symbol func def void: set-config-priority
In-Reply-To: message <m2vi1zsha8.fsf@altair.xemacs.org> from SL Baur
References: <199707250259.WAA25266@cs.sunysb.edu>
	<m2vi1zsha8.fsf@altair.xemacs.org>
X-Mailer: VM 6.33 under 20.3 "Vienna" XEmacs  Lucid (beta14)
Reply-To: verna@inf.enst.fr
X-Attribution: Did
X-Url: http://www-inf.enst.fr/~verna/
X-Face: 6o|eiKqaHN.ANh8HXDzntcWUOCg\]RsOd.ctvm~*y}Y^R&*a+Co,\s#=HWsw3x$b_n2kJ#g
 (7u?J^@^xP)f,jUF|0Z'J:|G/bMA5O12*b,7`-Q`=pKsCRIpso07.Y>YB2H{7`?u&yh;C_ZtLHfj<!
 $J=.i&Al'?,ax]MZd4tcm)_wF3$n*:f/lgS.;?Jr3T;Fl^q<qP**'tw
X-Face: |j}\)O|k##MrRz#VK$Jy=0r=3Qc,,a/Tr6*JQbE73dy17]<u3$*$]4O\1|h\|O\EDT9d$n+
 MTB{U&>2YcmW$9Z&H21e}#~#pgc>dn(is5Bv1l!{1re+Q9suKIOUmOqZs2>QMxHlR;;}kaGYA@HR3D
 C6
Content-Type: text/plain; charset=US-ASCII


[ before anything: would it be possible that all the mails directed to the
  list get a Reply-To: <the list> header from the list server ? 
  I think it would be preferable that replies go to the list and followup
  to the list (with author in Cc) rather than the opposite. ]



---- From SL Baur's message of July 25 (Re: b14 -- Mule: Symbol func def void: set-config-priority):
> Michael Kifer <kifer@CS.SunySB.EDU> writes:
> 
> > I am sure somebody has already reported this, but just in case:
> > When I select Mule."Set language environment"
> 
> > I am getting the error: 
> 
> > Symbol func def void: set-config-priority
> 
> I don't get that, perhaps you mistyped `set-coding-priority'.  The
> whole menu is broken. :-(
> 
-- 

	Besides, it seems that `set-coding-priority' is
no more defined. All I can find is `set-coding-priority-list'.

	I tried to replace the function name in `setup-japaneese-environment',
but that's not enough to make it work :-(, after that xemacs complains about
almost all the coding priorities given in this alist: 

        `	coding-category-iso-7 ....
       / |		
      /  /	
      `||	I'm not yet very familiar with all the coding-priority stuff
       ||	and I didn't have time to investigate.
       ||
       ||
   _   ||		Did.
  //|  ||
  || \_||
   \\           Didier Verna
   //  __
  //  {__}   E.N.S.T. INF C-214        http://www-inf.enst.fr/~verna/
 ||    __      46 rue Barrault            mailto:verna@inf.enst.fr
 \\   {__}   75634 Paris  cedex 13       Tel.   (33) 01 45 81 80 72
  \\
   ``----         France

