From: Patrick Gundlach <pg@levana.de>
Subject: Re: newbie question-- reading source files
Date: 22 Jul 2002 08:39:31 +0200 [thread overview]
Message-ID: <87n0sks1uk.fsf@gundla.ch> (raw)
In-Reply-To: <000501c23112$4aa40230$b5d64ca5@MATTHEW>
"Matthew Huggett" <mhuggett@telusplanet.net> writes:
Hello,
> How can I get more readable source files?
Get a dutch dictionary ;)
> I want to look into the ConTeXt code, but the files aren't that
> readable (no line breaks).
Oh, that is the problem... the source files have \n as a line
break. (Which is ok on unix systems). You can either get a viewer that
supports \n (and not \n\r, what system are you using?) as a line break
or copy the files you want to read into a seperate directory and run
texexec --module file-nam.tex
and you get a dvi/pdf file with a nicely formatted source code and
perhaps some examples. Warning: sometimes this could fail. If so, please
report those files to Hans. Ok, before I forget: you need the `nl'
format.
Patrick, still preparing for his exam
--
I'll fade into the darkness
prev parent reply other threads:[~2002-07-22 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 23:56 Matthew Huggett
2002-07-22 6:39 ` Patrick Gundlach [this message]
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=87n0sks1uk.fsf@gundla.ch \
--to=pg@levana.de \
/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).