From: Patrick Gundlach <pg@levana.de>
Subject: Re: inmargin text problems remain
Date: Fri, 31 Oct 2003 17:52:06 +0100 [thread overview]
Message-ID: <m2znfh2vux.fsf@levana.de> (raw)
In-Reply-To: <6.0.0.22.1.20031016145612.01b92ff8@digitpaint.nl> (Willi Egger's message of "Thu, 16 Oct 2003 14:57:12 +0200")
Willi Egger <w.egger@boede.nl> writes:
Hello Willi and others,
> Does anybody see the clue, how to tell Context to use the full marginwidth?
I strongly believe that this is a bug. left/right should change to
inner/outer on doublesided layout. But it does not (really):
\showframe
\setuppagenumbering [alternative=doublesided]
\setuplayout[backspace=1cm,leftmargin=.5cm]
\starttext
\dorecurse{4}{\input tufte \inleft{\the\hsize}\inright{\the\hsize} \page}
\showsetups
\stoptext
I have no idea what is going on.
Patrick
--
You are your own rainbow!
prev parent reply other threads:[~2003-10-31 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 12:57 Willi Egger
2003-10-16 13:26 ` Bill McClain
2003-10-16 18:36 ` Willi Egger
2003-10-31 16:52 ` 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=m2znfh2vux.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).