From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \starbuffer in own macros
Date: Sun, 18 Oct 2009 11:14:19 +0200 [thread overview]
Message-ID: <8CACE944-2B73-4387-90CE-1351EE13B8F4@googlemail.com> (raw)
In-Reply-To: <E44B65BA-BA56-41E8-9EEC-6A2F54C0D7B2@uni-koblenz.de>
Am 17.10.2009 um 22:29 schrieb Andreas Harder:
> Hi all,
>
> now that \inline[ref] etc. work—whereas in the case of \someline
> [ref] \inline[ref] always jumps to the else-branch of its definition
> and outputs the same line twice—I tried, obviously naive, to realize
> the following functionality (attachment).
>
> It seems that the (wrong?) use of \starbuffer in a macro is the
> cause of the error: ! File ended while scanning use of
> \dododowithbuffer.
>
> Can someone provide a correction?
1. This \doifelsesamelinereference macro in page-lin.mkiv should be
changed to:
\def\doifelsesamelinereference#1#2#3%
{\doifreferencefoundelse{lr:b:#1}
{\edef\fline{\currentreferencedefault}% was \currentreferencetext
\doifreferencefoundelse{lr:e:#1}
{\edef\tline{\currentreferencedefault}% was
\currentreferencetext
\ifx\fline\tline#2\else#3\fi}
{\unknownreference{#1}#2}}
{\unknownreference{#1}#2}}
2. You can't hide start/stopbuffer.
Before I help you provide us with more information, e.g. should the
text in the buffer
appear also in the complete text or do you it only in the snippet?
Wolfgang
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-18 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 17:05 Section setup Martin Scholz
2009-10-16 19:06 ` Mojca Miklavec
2009-10-16 23:22 ` Martin Scholz
2009-10-17 7:38 ` Mojca Miklavec
2009-10-17 14:58 ` Janneman
2009-10-17 15:40 ` Wolfgang Schuster
2009-10-17 15:46 ` Janneman
2009-10-17 15:54 ` Wolfgang Schuster
2009-10-17 16:12 ` Aditya Mahajan
2009-10-17 20:29 ` \starbuffer in own macros Andreas Harder
2009-10-18 9:14 ` Wolfgang Schuster [this message]
2009-10-18 10:02 ` Andreas Harder
2009-10-18 22:50 ` Wolfgang Schuster
2009-10-19 14:13 ` Andreas Harder
2009-10-19 15:53 ` Wolfgang Schuster
2009-10-19 16:01 ` Andreas Harder
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=8CACE944-2B73-4387-90CE-1351EE13B8F4@googlemail.com \
--to=schuster.wolfgang@googlemail.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).