From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: \appliedfigure...
Date: Wed, 16 Nov 2005 19:38:15 +0100 [thread overview]
Message-ID: <437B7C97.2030404@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0511161928100.19446@gaston.free.fr>
Peter Münster wrote:
> On Wed, 16 Nov 2005, Taco Hoekwater wrote:
>
>
>>Peter Münster wrote:
>>
>>>On Wed, 16 Nov 2005, Taco Hoekwater wrote:
>>>
>>>Yes and no, \appliedfigureoptions seems to be empty:
>>
>>It contains only the value of the option= key from
>>\externalfigure, so it will be empty in this case.
>
> Is there any possibility to get "width=1cm" ?
Not using \appliedfigure.... , but if you are willing
to mess with \unprotect:
\unprotect
\appendtoks
\writestatus{figures}{@@efwidth=\@@efwidth}
\writestatus{figures}{figurewidth=\figurewidth}
\to\externalfigurepostprocessors
\protect
Not sure if Hans is all that happy with that, though, because
the use of low-level \@@ef... stuff is precisely what the
\applied .. macros were supposed to hide.
Taco
next prev parent reply other threads:[~2005-11-16 18:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 19:46 new feature / manual Hans Hagen
2005-09-15 10:13 ` Thomas A. Schmitz
2005-09-15 11:35 ` Hans Hagen
2005-09-15 12:31 ` Thomas A. Schmitz
2005-09-15 12:38 ` Hans Hagen
2005-09-15 12:52 ` Thomas A. Schmitz
2005-09-15 16:54 ` Peter Münster
2005-09-15 18:30 ` Hans Hagen
2005-09-16 18:06 ` Peter Münster
2005-09-18 18:05 ` Hans Hagen
2005-09-20 7:51 ` Peter Münster
2005-09-21 8:33 ` Hans Hagen
2005-09-21 12:21 ` \appliedfigure... (was: new feature / manual) Peter Münster
2005-09-21 14:17 ` \appliedfigure Hans Hagen
2005-09-21 20:03 ` \appliedfigure Peter Münster
2005-11-16 12:40 ` \appliedfigure Taco Hoekwater
2005-11-16 17:45 ` \appliedfigure Peter Münster
2005-11-16 17:53 ` \appliedfigure Taco Hoekwater
2005-11-16 18:29 ` \appliedfigure Peter Münster
2005-11-16 18:38 ` Taco Hoekwater [this message]
2005-11-16 22:29 ` \appliedfigure Hans Hagen
2005-11-17 21:49 ` \appliedfigure Peter Münster
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=437B7C97.2030404@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).