From: "Peter Jander" <pj@orc.soton.ac.uk>
Subject: Re: how to define another part of a document
Date: Wed, 21 Mar 2001 15:25:25 GMT [thread overview]
Message-ID: <3AB8C909.3850.17F4420@localhost> (raw)
In-Reply-To: <3AB87E1F.6226.5A923C@localhost>
>
> What exactly do you want to achieve, maybe you're looking for heading
> clones and not for section blocks.
>
I was looking for a clean way to typeset in landscape mode a
chapter containing wide tables (plus change in interlinespace).
Probably localenvironments are more appropriate, but I couldn't
make them work.
Thanks for any advice,
Peter
next prev parent reply other threads:[~2001-03-21 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <From thanh at "Feb 20, 1 09:44:26 pm">
2001-02-21 13:12 ` Han The Thanh
2001-02-23 10:52 ` Hans Hagen
2001-02-23 15:54 ` Han The Thanh
2001-02-23 16:13 ` Hans Hagen
2001-03-21 10:05 ` Peter Jander
2001-03-21 14:32 ` Hans Hagen
2001-03-21 15:25 ` Peter Jander [this message]
2001-03-21 15:55 ` Hans Hagen
2001-03-21 17:59 ` Peter Jander
2001-03-22 6:32 ` Hans Hagen
2001-02-20 20:44 Han The Thanh
2001-02-20 21:15 ` Berend de Boer
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=3AB8C909.3850.17F4420@localhost \
--to=pj@orc.soton.ac.uk \
/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).