From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: placefloat
Date: Thu, 19 Jan 2006 18:00:36 +0100 [thread overview]
Message-ID: <43CFC5B4.8080404@elvenkind.com> (raw)
In-Reply-To: <6D7F0999-7E76-4137-9495-1489C70F9BDA@science.uva.nl>
Hans van der Meer wrote:
> (1) My intention was to place some material into the left margin on the
> page, but did not succeed.
Added to the collector. I'm positive that there is at least a little
bug somewhere in your list of problems, but I have no time right now
to do research.
>
> (2) Second question. Is there a mechanism whereby one can force the
> float to at least the next page when there is no room for it below the
> current point on the page?
There is:
\startpostponing
<stuff with postponed floats>
\stoppostponing
I believe it is mentioned in a manual somewhere, but don't recall
off-hand which one. However, I'm not confident that that mechanism
does precisey what you want, and it is definately not automatic.
Cheers, Taco
next prev parent reply other threads:[~2006-01-19 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 13:33 placefloat Hans van der Meer
2006-01-19 17:00 ` Taco Hoekwater [this message]
2006-01-21 19:10 ` placefloat Hans van der Meer
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=43CFC5B4.8080404@elvenkind.com \
--to=taco@elvenkind.com \
--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).