From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Linux upgrade
Date: Wed, 5 Jul 2006 10:25:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0607051022240.1884@nqvgln> (raw)
In-Reply-To: <449C229D.2080002@wxs.nl>
On Fri, 23 Jun 2006, Hans Hagen wrote:
> Aditya Mahajan wrote:
>>
>> utilities. It also provides some useful things like ifchanged and
>> iftoughed. There is a texmfstart manual (bit out of date). Simply
>>
> the source is updated, but not yet the pdf -)
Had a look at the updated manual and learnt about some features of
texmfstart that I did not know. The front page is a nice example of
\sometxt.
Aditya
next prev parent reply other threads:[~2006-07-05 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 23:18 John R. Culleton
2006-06-23 1:37 ` Aditya Mahajan
2006-06-23 14:17 ` John R. Culleton
2006-06-23 15:54 ` Aditya Mahajan
2006-06-23 17:19 ` Hans Hagen
2006-07-05 14:25 ` Aditya Mahajan [this message]
2006-06-23 8:44 ` Taco Hoekwater
2006-07-05 23:56 ` gnwiii
2006-07-11 10:23 ` Taco Hoekwater
2006-06-23 9:39 ` luigi scarso
2006-06-23 16:34 ` Peter Münster
2006-06-23 22:00 ` John R. Culleton
2006-06-23 22:48 ` John R. Culleton
2006-06-24 7:46 ` Peter Münster
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=Pine.WNT.4.63.0607051022240.1884@nqvgln \
--to=adityam@umich.edu \
--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).