[emacs-wiki-discuss] Re: Autoloads

[Michael Olson]

Jim Ottaway <address@hidden> writes:

> In the absence of the current style of pre-defined projects [i.e.,
> specified somewhere such as ~/.emacs], the file extension would make
> it much easier to determine that a configuration file should be
> searched for.  Without a file extension, and without pre-defined
> projects, I think working out that a configuration file should be
> loaded for the file, and indeed that this was a muse file at all,
> would be complicated. I think that is the relationship that the two
> things share.

Yes, a file extension would make this easier.

Well, this isn't going to be one of my top priorities for the next
major release of Muse (3.03).  Perhaps if the merging of nested-list
support goes faster than I had anticipated, I would try implementing
this before the release.

I wonder if the JDE people would be interesting in having an
abstracted project-file.el file made from their jde-project-file.el
source.

But first, before I implement anything, what sort of format should
this file use?  Should it be automatically generated by a
muse-project-file-write function?  Should people be able to customize
it by hand easily?

-- 
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: manga, Debian, XHTML, wiki, Emacs Lisp
  /` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG
 |_] | \| |_| Jabber: mwolson_at_hcoop.net

pgpRolbmROY0j.pgp
Description: PGP signature