From: "Peter Münster" <pmlists@free.fr>
Subject: Re: treat framed and externalfigure as characters
Date: Wed, 10 May 2006 17:37:22 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0605101735150.24389@gaston.pm> (raw)
In-Reply-To: <4461048A.9020801@wxs.nl>
On Tue, 9 May 2006, Hans Hagen wrote:
> > There is a fundamental difference between
> > bla \framed{bla} bla
> > and
> > \framed{bla} bla bla
> > that is not understandable.
> >
> this is the case for many more things and a tex speciality which takes
> while to get accustomed to; a similar case is
>
> {\bf whatever} rest of par
Hello Hans,
I tried this:
\setupindenting[big,yes]
\starttext
\input tufte
{\bf whatever} rest of par
\input tufte
\stoptext
But I don't see the problem... ?
> btw, there is \inframed for inline usage, or one could define a symbol
Thanks, I'll take a look at it.
Cheers, Peter
--
http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2006-05-10 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 16:11 Peter Münster
2006-05-09 19:22 ` Taco Hoekwater
2006-05-09 20:19 ` Peter Münster
2006-05-09 21:07 ` Hans Hagen
2006-05-10 15:37 ` Peter Münster [this message]
2006-05-10 18:35 ` Hans Hagen
2006-05-09 20:53 ` Hans Hagen
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.LNX.4.58.0605101735150.24389@gaston.pm \
--to=pmlists@free.fr \
--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).