From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: RE: footnote placement
Date: Tue, 29 Mar 2005 08:30:24 -0700 [thread overview]
Message-ID: <428794CC@webmail.colostate.edu> (raw)
>===== Original Message From Hans Hagen <pragma@wxs.nl> =====
> \starttext
>> \startbuffer[tufte]
>> \input tufte
>> \stopbuffer
>> \startbuffer[knuth]
>> \input knuth
>> \stopbuffer
>> \dorecurse{100}{test \footnote{\typebuffer[knuth]} \endnote{eee}\endgraf}
>
>it's \getbuffer else you indeed get a verbatim buffer (which is what type
does);
>
>\dorecurse{100}{test \footnote{\input knuth } \endnote{eee}\endgraf}
So \endgraf (or \par) is needed here; I should have guessed-)
>also works; put a space or \relax after \input, else tex keeps scanning;
>alternatively use \ReadFile{knuth} or \readfile{knuth}{}{}
I definitely prefer the \ReadFile option. I could not find it (or
\readfile{}{}{}) in ConTeXt Commands or texshow; must be new...
What's the difference between these two commands?
Also: given the ConTeXt philosophy, shouldn't there be a non-cryptic
replacement for \par or \endgraf, something like \paragraph or \endparagraph?
Best
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-03-29 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 15:30 Idris Samawi Hamid [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-20 9:16 Meer, Hans van der
2017-07-20 18:28 ` Pablo Rodriguez
2017-07-20 19:14 ` Meer, Hans van der
2017-07-20 19:33 ` Hans Hagen
2017-07-20 20:06 ` Meer, Hans van der
2017-07-21 5:00 ` Pablo Rodriguez
2017-07-21 6:28 ` Meer, Hans van der
2005-03-29 15:31 Idris Samawi Hamid
2005-03-21 15:34 Idris Samawi Hamid
2005-03-21 16:42 ` Hans Hagen
2005-03-21 20:12 ` Gerben Wierda
2005-03-28 23:26 ` Hans Hagen
2005-03-28 23:30 ` Hans Hagen
2005-03-18 4:24 ishamid
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=428794CC@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).