From: "Patrick Gundlach" <pg@levana.de>
Subject: Re: \startlinenumbering and \starttyping
Date: 11 Jun 2004 19:27:23 +0200 [thread overview]
Message-ID: <m21xkmqa2s.fsf@levana.de> (raw)
In-Reply-To: <20040611170504.GD3196@puritan.pcp.ath.cx> (Nikolai Weibull's message of "Fri, 11 Jun 2004 19:05:04 +0200")
Hello Nikolai,
> Argh, should have sticked to the original example - copy and pasted...
>
> Anyway, it is equivalent to
[...]
Sorry, your file works fine here, except that there is no
\starttext...\stoptext pair. No error/overfull box/...
...
systems : begin file test at line 1
[1.1{/opt/texlive/8/texmf/fonts/map/pdftex/updmap/pdftex.map}{/opt/local/texmf/
dvips/config/dolly.map}{/opt/local/texmf/dvips/config/typedesign.map}]
systems : end file test at line 12
...
Please post a minimal file that is *complete* (!!) and shows the error
/warning you get.
Patrick
next prev parent reply other threads:[~2004-06-11 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 16:22 Nikolai Weibull
2004-06-11 16:52 ` Patrick Gundlach
2004-06-11 17:05 ` Nikolai Weibull
2004-06-11 17:27 ` Patrick Gundlach [this message]
2004-06-11 19:36 ` Nikolai Weibull
2004-06-14 11:52 ` Hans Hagen
2004-06-17 12:02 ` Nikolai Weibull
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=m21xkmqa2s.fsf@levana.de \
--to=pg@levana.de \
--cc=ntg-context@ntg.nl \
/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).