Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!lll-crg!qantel!hplabs!hp-pcd!uoregon!meyer
From: meyer@uoregon.UUCP (meyer)
Newsgroups: net.emacs
Subject: autoload confusion
Message-ID: <136700001@uoregon.UUCP>
Date: Fri, 10-Jan-86 11:07:00 EST
Article-I.D.: uoregon.136700001
Posted: Fri Jan 10 11:07:00 1986
Date-Received: Fri, 17-Jan-86 06:35:46 EST
Organization: Univ of Oregon - Eugene, OR
Lines: 38
Nf-ID: #N:uoregon:136700001:000:1297
Nf-From: uoregon!meyer    Jan 10 08:07:00 1986



	This may not be a *real* bug, but I'm confused about
	the philosphy of "autoload". Specifically, I would like
	to load my own scheme-mode (lisp-mode, prolog-mode,...),
	but since scheme-mode (for example) is already defined, (i.e., 
    	!EQ (XSYMBOL (function)->function, Qunbound), where "function"
	is scheme-mode), one cannot define a new scheme-mode. That is,
	autoload returns nil and does nothing if the symbol (function name,
	e.g., 'scheme-mode) is already bound.  Apparently, this will be 
	true for any function name loaded out of loaddefs.el.

	Further, we can't use the scheme entries in auto-mode-alist
	(since we can't autoload a different scheme-mode). To get
	around this, I had to call my scheme-mode something
	different, and cons the appropriate stuff onto the front
	of auto-mode-alist. A terrible hack, at best.

	Is there a way to get around this (e.g., unbind a symbol;
	I noticed there isn't much in the way of oblist handling
	functions), or should autoload always set up the autoload
	(like Gosling's)?

	Thanks for the time,


	David Meyer	

	Department of Computer and Information Science
	University of Oregon
	Eugene, OR 97403
	
	usenet:		{decvax, allegra}!tektronix!uoregon!meyer
	csnet:		meyer@uoregon.csnet
	arpanet:	meyer%uoregon.csnet@csnet-relay.arpa