Document Classes ⇒ how to do acronyms/Glossaries in memoir?

[artimess]

the memoir class is not a resource hog, but the memoir manual IS.

If you insist of using that as a base for your document without knowing what it does or which parts of it you actually need, then that is your choice.

True, I am not an expert in this matter. memoir manual uses certain constructs that fits well with what I need, specially the environments that it has like lcode, lsyntax, etc. So for the ease of use I took the manual preambles and style to build the structure of my book without deeply going into taking out what I may not need in it. I am sure one can build acronyms with the features memoir provides, but I do not have what it takes to learn and do it, so I opted for your package, it is in my opinion very best thought one around.

[daleif]

You may be confusing a few things here. Memoir is not a package, it is a class. The memoir manual support files are packages (.sty files).

I would recommend that you simply made your own package, not that hard. And copy stuff from the memman support packages until you had what you needed.

In my own stuff I tend to use the listings package for showing code (much better features than memoir has). Though the lsyntax env can be useful.

memman also use several types of glossaries and indexes that you might not need.

So you should figure out exactly what you need, and then steal that code from the memman support files.

I you need help just post here.