Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort out LaTeX .cls vs .sty (class vs style files) and what we use them for. #4

Open
kfogel opened this issue Apr 24, 2019 · 0 comments

Comments

@kfogel
Copy link
Member

kfogel commented Apr 24, 2019

As of right now, we have these files:

  otsletter.cls
  texMemo.cls
  contract.cls
                    ots.sty
  invoice.cls       invoice.sty
  otsreport.cls     otsreport.sty

Commit 7fa4dff brought to my attention that we're not that clear on what kinds of things should go into which ones, and which of the above should include which other of the above.

For example, should otsreport.cls just include ots.sty, so that (say) a document we're writing in the otsreport documentclass that happens to use the acronym environment doesn't have to explicitly have \usepackage{ots} in its header?

I think maybe the following is the state we want to get to:

  1. We have .cls files that just define what is necessary to distinctively define their respective classes;
  2. Each .cls file does \usepackage{ots} (this loads ots.sty).
  3. All the non-class-specific stuff we use, whether OTS-defined (e.g., \fullref) or not (e.g., the acronym env), goes into ots.sty.

This implies moving any non-class-specific stuff that currently happens to be defined in .cls files into ots.sty.

See What are .cls and .sty files? How are they different? and Classes and packages – what's the difference? for background on classes versus packages (style files).

@kfogel kfogel changed the title Sort out .cls vs .sty (class vs style files) and what we use them for. Sort out LaTeX .cls vs .sty (class vs style files) and what we use them for. Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant