ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <Gerben.Wierda@rna.nl>
Subject: Re: Bug in footnote mechanism when compiling per chapter
Date: Fri, 11 Nov 2005 16:06:16 +0100	[thread overview]
Message-ID: <79ba3db6d76541e43dbf59a65bd3f70b@rna.nl> (raw)
In-Reply-To: <6240682B-1D73-43C4-83FB-A47124F54A0A@rna.nl>

This one has not been fixed by the new release.

! Undefined control sequence.
\lastnotenumber ->\@@cvset 213

<argument> \lastnotenumber
                            \domovednote \v!previouspage \v!nextpage
\doattributes ...sname #1#2\@EA \endcsname \fi {#4
                                                   }\dostopattributes
\dohighlow ...\scratchdimen \hbox {\dodohighlow #5
                                                   }}\ht \scratchbox 
\struthe...
<argument> ...ednote \v!previouspage \v!nextpage }
                                                   }
\doifreferencefoundelse ...ferencefound #2\else #3
                                                   \fi \egroup 
\doresetgotowh...
...
l.919 ...plication is a valid one (true)\footnote{

G

On Oct 31, 2005, at 21:49, Gerben Wierda wrote:

> I had in my project file
>
> \definenote[endnote][location=none]
> \setupfootnotes[conversion=set 2,way=bypage]
>
> which I moved to my environment file. But wherever I have it, when I 
> compile per chapter, the footnote mechanism fails because it runs out 
> of symbols to use. When I compile the entire book. no such problem 
> occurs. Is this a ConTeXt bug?
>
> G
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

      reply	other threads:[~2005-11-11 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 20:49 Bug in footnote mechanism when compiling per chapter? Gerben Wierda
2005-11-11 15:06 ` Gerben Wierda [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=79ba3db6d76541e43dbf59a65bd3f70b@rna.nl \
    --to=gerben.wierda@rna.nl \
    --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).