ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: \parbox, \framed, ... (was: Strange behaviour of \bTABLE ... \eTABLE)
Date: Fri, 29 Jul 2005 13:25:42 +0200	[thread overview]
Message-ID: <6faad9f005072904253246f61a@mail.gmail.com> (raw)
In-Reply-To: <42E6B637.7070304@wxs.nl>

Hans Hagen wrote:
> Mojca Miklavec wrote:
> 
> >1.) I saw \hbox, \vbox, \vtop, \lbox, \cbox, \rbox, \sbox, \tbox,
> >\bbox on page 106 of cont-eni.pdf. But if I understand it properly,
> >there's no alternative to LaTeX \parbox command.
> >1.1.) After grep-ing the LaTeX tree for "\parbox", my disk ran out of space
> >1.2.) \bTABLE ... \eTABLE seems too complicated to me to be used for
> >such a simple thing as asking for a paragraph of a certain width,
> >centered with regard to the current line.
> >
> as always, it's \framed that does the trick:
> 
> \input tufte  \framed[location=middle,align=center]{what\\is a\\parbox}
> \input tufte

Thank you a lot. I didn't know the location=middle option (yupi, no
need for \vcenter any more :).

Without align=, \framed behaves pretty much like a \hbox. So once I
unsuccessfully tried \crlf and \\ inside \framed a couple of times, I
gave up, forgetting about some nice examples in the manual.

But how do I get rid of the blank line in this example:

\framed
	[align=flushleft]
	{\typefile{tufte.tex}}

Thank you,
    Mojca

  reply	other threads:[~2005-07-29 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 15:41 Mojca Miklavec
2005-07-26 20:29 ` \parbox, \framed, Patrick Gundlach
2005-07-26 22:16 ` \parbox, \framed, ... (was: Strange behaviour of \bTABLE ... \eTABLE) Hans Hagen
2005-07-29 11:25   ` Mojca Miklavec [this message]
2005-07-29 11:57     ` \parbox, \framed, Taco Hoekwater
2005-07-29 14:16       ` Mojca Miklavec

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=6faad9f005072904253246f61a@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.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).