From: "Zhichu Chen" <zhichu.chen@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Weird behavior about metafun
Date: Mon, 7 Jan 2008 23:15:38 +0800 [thread overview]
Message-ID: <769ba7780801070715m3e508452rea39e3271b723407@mail.gmail.com> (raw)
In-Reply-To: <47822C12.8010607@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1893 bytes --]
On Jan 7, 2008 9:41 PM, Hans Hagen <pragma@wxs.nl> wrote:
> Zhichu Chen wrote:
> > Oh, by the way, if I put \fpos at the beginning of a paragraph,
> > it adds an extra blank line. I have to force it to the
> > horizontal mode like:
> > \leavevmode\fpos{A-1} . . . \tpos{A-1}
>
> \dontleavehmode \fpos ...
>
> > So is it safe to change the definition of \fpos to add
> > \leavevmode at the beginning of the macro?
>
> no, that could happen in the macro that uses \fpos, not in \fpos itself
Cool, then I'll define my own macro to do that.
Thanks.
>
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
--
Best Regards
Chen
----------------------------------------------------------------
Zhi-chu Chen | Shanghai Synchrotron Radiation Facility
No. 2019 | Jialuo Rd. | Jiading | Shanghai | P.R. China
tel: 086 21 5955 3405 | zhichu.chen.googlepages.com
| www.sinap.ac.cn
----------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 3477 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-07 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 2:45 Zhichu Chen
2008-01-07 11:50 ` Zhichu Chen
2008-01-07 13:41 ` Hans Hagen
2008-01-07 15:15 ` Zhichu Chen [this message]
2008-01-07 15:52 ` Aditya Mahajan
2008-01-08 1:43 ` Zhichu Chen
2008-01-08 14:45 ` Zhichu Chen
2008-01-08 15:00 ` Arthur Reutenauer
2008-01-08 17:04 ` Hans Hagen
2008-01-09 1:20 ` Zhichu Chen
2008-01-09 12:01 ` Wolfgang Schuster
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=769ba7780801070715m3e508452rea39e3271b723407@mail.gmail.com \
--to=zhichu.chen@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).