From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Jean-Pierre Delange via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: paragraph notes when located in text
Date: Thu, 6 Jan 2022 17:23:56 +0100 [thread overview]
Message-ID: <0dcaac0d-0f38-38c8-d07b-9dc9f2070c41@gmx.es> (raw)
In-Reply-To: <F2377C5D-B01C-4D25-B9DA-B6952FB20586@free.fr>
On 1/5/22 7:46 PM, Jean-Pierre Delange via ntg-context wrote:
> AMHO, there is no text with dorecurse …
Jean-Pierre,
many thanks for your reply.
The second line is the content of \dorecurse:
\dorecurse{25}
{a\footnote{b} }
> Then the buffer is empty !
No on my computer. Have you pasted the code and did you get an empty file?
> And if I remember the buffer setup should be placed before the
> starttext command. Am I wrong ?
As far as I know, buffer contents can be defined before or after \starttext.
If I comment out the only commented line (in the original sample), I
cannot get paragraph notes. I thought this could be a bug.
Could anyone confirm whether this is the intended behaviour?
Many thanks for your help,
Pablo
___________________________________________________________________________________
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:[~2022-01-06 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 18:23 Pablo Rodriguez via ntg-context
2022-01-05 18:46 ` Jean-Pierre Delange via ntg-context
2022-01-06 16:23 ` Pablo Rodriguez via ntg-context [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=0dcaac0d-0f38-38c8-d07b-9dc9f2070c41@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).