From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: Re: the right way to do \ref?
Date: Fri, 15 Apr 2005 10:49:11 +0200 [thread overview]
Message-ID: <20050415084911.GA5982@puritan.pcp.ath.cx> (raw)
In-Reply-To: <20050414233151.GB8532@localhost.localdomain>
Paul Tremblay, April 14:
> see \ref[r][mark1] \par
Why not \at[mark1]?,
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
prev parent reply other threads:[~2005-04-15 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 23:31 Paul Tremblay
2005-04-15 8:49 ` Nikolai Weibull [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=20050415084911.GA5982@puritan.pcp.ath.cx \
--to=mailing-lists.context-users@rawuncut.elitemail.org \
--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).