From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: \setupframed[...][...=...]
Date: Wed, 12 Apr 2006 18:04:05 +0200 [thread overview]
Message-ID: <443D24F5.5000905@seznam.cz> (raw)
In-Reply-To: <443D0E08.5000606@wxs.nl>
Hans Hagen wrote:
> Vit Zyka wrote:
>
>>Hans Hagen wrote:
>>
>>
>>>Vit Zyka wrote:
>>>
>>>
>>>
>>>>Is there some simple solution? Or it has to be rewritten in a way like
>>>>other \definesomething[...] (storing every parameter/definition-instance
>>>>
>>>>
>>>
>>>btw, there is (beware: use some unique name):
>>>
>>>\presetlocalframed[myframed]
>>>\setuplocalframed[myframed][width=4cm,height=2cm]
>>>\localframed[myframed][framecolor=green]{oeps}
>>>
>>
>>localframed was a mysterious stuff for me.
>>
>>It seems do exactly what I wanted. In this perspective the
>>\setupframed[...][...=...] is not needed (only for not being suprised
>>since its absence is a bit against context filosofy).
>>
>>I just wanted to fill texshow web, but it is missing this stuff. So I
>>added \*localframed note in missing texshow items on wiki.
>>
>
> it actually is a low level command, also, there is \defineframedtext which is (1) configurable and (2) provided \myframed as well
>
> Hans
And the content of \framed and \framedtext is formated the same way?
Hmm I am a bit confused with \framed v. \localframed v. \framedtext. If
the difference is only in an interface or even in functionality. I will
have to study the code but not time for that now.
Thanks for this note.
Vit
prev parent reply other threads:[~2006-04-12 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 0:25 \setupframed[...][...=...] Vit Zyka
2006-04-12 8:56 ` \setupframed[...][...=...] Hans Hagen
2006-04-12 9:11 ` \setupframed[...][...=...] Hans Hagen
2006-04-12 9:39 ` \setupframed[...][...=...] Vit Zyka
2006-04-12 9:14 ` \setupframed[...][...=...] Hans Hagen
2006-04-12 13:29 ` \setupframed[...][...=...] Vit Zyka
2006-04-12 14:26 ` \setupframed[...][...=...] Hans Hagen
2006-04-12 16:04 ` Vit Zyka [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=443D24F5.5000905@seznam.cz \
--to=vit.zyka@seznam.cz \
--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).