From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: \startcomment...\stopcomment with XML processing
Date: Sun, 25 Jun 2017 15:00:21 +0200 [thread overview]
Message-ID: <704ef898-8a64-44ba-ebe0-a1c90c353d94@gmx.es> (raw)
In-Reply-To: <348d7e15-0cb5-0a31-3945-b642b8d6e5a9@wxs.nl>
On 06/25/2017 12:18 PM, Hans Hagen wrote:
> On 6/24/2017 10:53 PM, Pablo Rodriguez wrote:
>> [...]
>> I don’t know why I cannot get \startcomment...\stopcomment with
>> \xmlpure{#1}.
>>
>> This is the only way I have to get lines and spaces in comments.
>>
>> Which is the right way to do it?
>
> \startxmlsetups xml:copy:code
> \xmltobufferverbose{#1}{.}{whereever}
> \comment[location=inmargin,color=yellow,buffer=whereever]{}
> \stopxmlsetups
Many thanks for your reply, Hans.
I’m using this for a class. I mean, I have a document with many code
snippets and (from what I get) I’m using the same name for all buffers.
It seems to work fine for me, but I wonder whether this is a safe
practice. Or it might break in some scenarios.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2017-06-25 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 20:53 Pablo Rodriguez
2017-06-25 10:18 ` Hans Hagen
2017-06-25 13:00 ` Pablo Rodriguez [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=704ef898-8a64-44ba-ebe0-a1c90c353d94@gmx.es \
--to=oinos@gmx.es \
--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).