From: Patrick Gundlach <pg@levana.de>
Subject: Re: Again: \indenting[*hang*] ?!
Date: Wed, 24 Sep 2003 09:31:39 +0200 [thread overview]
Message-ID: <m2llse7ick.fsf@levana.de> (raw)
In-Reply-To: <5.2.0.9.1.20030923234203.02335b48@localhost> (Hans Hagen's message of "Tue, 23 Sep 2003 23:42:59 +0200")
Hans Hagen <pragma@wxs.nl> writes:
Hi,
> so ... write a one page YourWay doc with experiences (using the
> portal) and post it -)
you mean that I should actually *use* ConTeXt? Not just playing with
it? Hmm, sounds ok to me.
Patrick
--
Silent is the goldfish in its bowl
prev parent reply other threads:[~2003-09-24 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 14:27 Steffen Wolfrum
2003-09-22 15:06 ` Patrick Gundlach
2003-09-22 15:24 ` Thomas A.Schmitz
2003-09-23 20:42 ` Again: \indenting[*hang*] ?! + Re: critical editions in context Steffen Wolfrum
2003-09-23 21:25 ` *-nnt, *-lnt, c!, v! and multi-lingual interface Patrick Gundlach
2003-09-22 15:41 ` Again: \indenting[*hang*] ?! Steffen Wolfrum
2003-09-22 16:16 ` reading the source Patrick Gundlach
2003-09-23 21:41 ` Re: Again: \indenting[*hang*] ?! Hans Hagen
2003-09-23 21:42 ` Hans Hagen
2003-09-24 7:31 ` 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=m2llse7ick.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).