Re: byte-compile emu-mule.el

* "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp&gt; writes: Stephen> I have three different approaches in mind Stephen> o physically move the code to a separate package directory, Stephen> probably with the same name, under xemacs-packages/mule Stephen> o physically move the code to a mule subdirectory of the original Stephen> package Stephen> o physically move the code to a separate file with an extra Stephen> extension (.mule should do the trick) Stephen> In the former case, we'd need to create a separate package; that Stephen> probably is a distribution nightmare, so it probably hardly ever makes Stephen> sense. The last is probably the best idea; there actually is very Stephen> little code that really requires Mule. Then XEmacs.rules would get a Stephen> rule to make a .el file from a .el.mule file by renaming or copying Stephen> it. Approach 3 looks the best. But it will only help people who build from the CVS source. Anyone else is going to have all those *.mule files as *.el because I build with Mule-enabled XEmacs. -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: 59E4C4B2]---| | XEmacs - It's not just an editor... | | It's a way of life. | |----------------------------------<mailto:youngs＠xemacs.org>---|