Re: Font-bug?

Jeff> What needs to happen to make a package? 1. Get a volunteer. 2. Volunteer decides whether file fits into existing package (eg, generalize edict.el -- not a good idea though, edict requires Mule). If so, check with maintainer, if none, volunteer to be maintainer, if too lazy :), ask Steve Y. Add file(s) to package in CVS, update Makefile. 3. If need new package, pick non-conflicting name, mkdir, put files in there, steal Makefile from similar package, file off identifying marks of other package, insert relevant details for own, get Steve Y's approval (a formality if the volunteer intends to be maintainer), check in. Of course, all steps require sanity checking to make sure package builds, still works, etc, but the basic operations are that simple. Refinements include improving customize support, adding autoload cookies so that auto-autolads eliminates the need to `require' in init files, etc. But that can come later. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."