Mithrandir the Wizard wrote:
> David Kastrup wrote:
>> Are you thinking of something like Emacs autoloaded macros?  So one
>> would want to have things be autoloaded upon first macro use or so?
> No, I think he's thinking of a more rational approach to package
> loading syntax. For example, if you want to set spanish as the
> document language you say:
> \language{spanish}
> instead of
> \usepackage{spanish}
> That is, you say what you want to do instead of how you want it to
> done. I think this is the philosophy behind LaTeX. For example when
> you want to write a chapter heading you use the \chpater command
> instead of using commands for changing the type, inserting an entry
> on the index ...
> I've allways thought that writing something like:
> \usepackage[latin1]{inputenc}
> \usepackage[spanish]{babel}
> \usepackage[dvips]{graphicx}
> \usepackage{parskip}
> \usepackage{lscape}
> \usepackage{moreverb}
> at the beginning of your document is not the way things should be
> done in LaTeX.

Yes, I agree. And then go one step further and design a new
user/designer interface so that a (book) designer don't need to delve
into the latex.ltx source. ((with all implications ...))

Best regards,
Ulrich Dirr