From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Concatenate buffers without newline
Date: Tue, 22 Jun 2021 20:29:29 +0200 [thread overview]
Message-ID: <a3f0a4fe-10b7-d2dc-990e-4159f2955891@gmail.com> (raw)
In-Reply-To: <6229081.MhkbZ0Pkbq@mapagari-lifebook-e754>
Pascal Pascali schrieb am 22.06.2021 um 20:21:
> Hello!
>
> Is there a way to concatenate predefined blocks or buffers without ConTeXt printing newlines between them?
>
> I'd like to have something like:
>
> \startBitOfData [name1]
> Some part of paragraph here.
> \stopBitOfData
>
> \startBitOfData [name2]
> Some more going on here.
> \stopBitOfData
>
>
> And then:
>
> \getBitOfData [name1]
> \getBitOfData [name2]
>
> Outputting:
> Some part of paragraph here. Some more going on here.
>
> Not outputting:
> Some part of paragraph here.
> Some more going on here.
>
>
> Thank you for any tip!
Please send a *working* minimal example next time.
\starttext
\startbuffer[first]
First paragraph.
\stopbuffer
\startbuffer[second]
Second paragraph.
\stopbuffer
\start
\setupbuffer[before=,after=]
\getbuffer[first]%
\getbuffer[second]
\stop
\blank
\getbuffer[first,second]
\stoptext
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2021-06-22 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 18:21 Pascal Pascali
2021-06-22 18:29 ` Wolfgang Schuster [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=a3f0a4fe-10b7-d2dc-990e-4159f2955891@gmail.com \
--to=wolfgang.schuster.lists@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).