From: Kip Warner <kip@thevertigo.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Adam Reviczky <reviczky@gmail.com>
Subject: Re: Issue with 2013.04.30 00:31
Date: Mon, 06 May 2013 14:31:41 -0700 [thread overview]
Message-ID: <1367875901.2646.50.camel@rommel> (raw)
In-Reply-To: <1367822177.2646.23.camel@rommel>
[-- Attachment #1.1: Type: text/plain, Size: 2664 bytes --]
On Sun, 2013-05-05 at 23:36 -0700, Kip Warner wrote:
> Hey list,
>
> I am experiencing two issues in compiling my document. The first is a
> non-fatal warning during compilation of my book:
>
> ...
> (/usr/share/texmf/tex/context/base/s-abr-02.tex
> resolvers > modules > 'abr-01' is loaded
> (/usr/share/texmf/tex/context/base/s-abr-01.tex))tr: invalid
> option -- '
> '
> Try 'tr --help' for more information.
>
> publications > wrote a new auxiliary file \jobname.aux
> This is BibTeX, Version 0.99d (TeX Live 2012/Debian)
> The top-level auxiliary file: Handbook.aux
> The style file: cont-au.bst
> Database file #1: References/References.bib
> (/usr/share/texmf/tex/context/bib/bibl-apa.tex)
> ...
So I managed to solve this problem with an additional space between the
tr command and its parameter as a macro in my environment file.
> The second issue is a fatal error:
>
> ...
> references > unknown reference '[Leitmotifs][Resources For
> Everyone]'
> pages > flushing realpage 9, userpage 9, subpage 2
> ! LuaTeX error [string "\directlua "]:1: invalid escape sequence
> near '\#'.
> \ctxcommand #1^^@-\directlua {commands.#1}
>
> \bibgotoURL #1#2\-\useURL [#1][#2][][#1]
> \from [#1]
> <argument> ...ded {\bibgotoURL {\@@pb@title }{\@@pb@biburl }}
> .\egroup
> \space
> \firstoftwoarguments #1#2o-#1
>
> \@@pv:l:misc ...{\bgroup \it }{.\egroup \space }{}
> \insertpubname
> {}{. }{}\in...
> \dotypesetapublication ...ative {\bibgetvart {#1}}
>
> \removeunwantedspaces \egr...
> ...
> l.37 ...olumn to sort demand by vote.}][occupy_poll]
> This should
> not discourag...
> E
> ? You want to edit file Leitmotifs/Leitmotifs.tex at line 1
> ...
This was solved as well by removing an escaped pound sign in one of my
bibtex references. It shouldn't have choked on it, because as I said, it
was escaped, but removing it made it appear to compile ok.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-05-06 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 6:36 Kip Warner
2013-05-06 21:31 ` Kip Warner [this message]
2013-05-07 8:46 ` Hans Hagen
2013-05-07 8:57 ` luigi scarso
2013-05-07 23:35 ` Kip Warner
2013-05-07 23:38 ` Kip Warner
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=1367875901.2646.50.camel@rommel \
--to=kip@thevertigo.com \
--cc=ntg-context@ntg.nl \
--cc=reviczky@gmail.com \
/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).