Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Gnus.tar.gz/.tex files
Date: 18 Apr 1998 18:55:10 -0700	[thread overview]
Message-ID: <m390p2d18h.fsf@org.com> (raw)
In-Reply-To: Alan Shutko's message of "18 Apr 1998 18:14:01 -0500"

Alan Shutko <ats@acm.org> writes:

> >>>>> "H" == Harry Putnam <reader@newsguy.com> writes:
> 
> H> Not too well versed in using Latex commands but have been able to
> H> make nice .dvi files from 'refcard.tex' that comes in the /etc
> H> directory of untarred gnus-5.6.4 .
> 
> refcard.tex is the only file you run latex on.  (Incidently, I think
> you mean the text directory of the untarred dist?)

Thanks

Actually 'texi' is what I meant to type.

> 
> gnusref.tex is loaded by refcard.tex.
> 
> postamble.tex is used in the DVI version of the manual.
> 
> H> It would be nice if a word or two of direction or instruction were
> H> included somewhere in the tar.gz, concerning making use of the
> H> files provided.
> 
> Well, make dvi in the texi directory should do it, but it doesn't do
> the refcard.  Any reason that refcard.dvi or refcard.ps aren't listed
> as targets for dvi or latexps?

Is there some way to tell which ones are stand alone files like
refcard.tex seems to be and which ones are part of something else.

I thought I remembered there being two versions of the gnusref one being
very brief and the other just brief, so I took these two files to be
those renditions.



-- 

Harry Putnam  reader@newsguy.com



  reply	other threads:[~1998-04-19  1:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-18 21:21 Harry Putnam
1998-04-18 23:14 ` Alan Shutko
1998-04-19  1:55   ` Harry Putnam [this message]
1998-04-24 20:34   ` Lars Magne Ingebrigtsen
1998-04-19 18:25 ` Mike McEwan
1998-04-19 19:02   ` Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m390p2d18h.fsf@org.com \
    --to=reader@newsguy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).