ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Odd /externalfigure behavior
Date: Wed, 12 Dec 2012 19:12:02 +0100	[thread overview]
Message-ID: <567971B0-5AB4-47C4-9665-5F183E202545@gmail.com> (raw)
In-Reply-To: <50C8C2BF.1080200@wisc.edu>


Am 12.12.2012 um 18:45 schrieb Guy Stalnaker <jstalnak@wisc.edu>:

> All,
> 
> I've been working on a document for weeks and it's been compiling fine. I have a pdf copy from yesterday afternoon at 4p local time, the last time it compiled successfully. I was doing a search/replace on some /crlf to add space between text and an image. The search/replace with Gnome's gedit included \n in both search and replace string. Suddenly context will no longer successfully compile the document! What's very, very odd, is that the context document is an output file from pandoc of a markdown document that has had no issues until now. If I go back now to the original markdown doc and regenerate the context document the issue persists with or without subsequent edit!! Damned peculiar. Here's the workflow:
> 
> pandoc -s -f markdown -t context <file.md> -o <file.context.tex>
> gedit <file.context.tex> to add:
> 
> \defineexternalfigure[screenshot][frame=on]
> 
> and then add [screenshot] to all of the \externalfigure directives. Then find the /crlf that appear immediate before *all* of the \externalfigure directives and double them (unless someone who reads this can tell me how to easily modify the padding of an image when it's placed to increase the spacing between the image and the text above it).
> 
> I've been doing this for many days. Until late yesterday afternoon. Now context spits out this:
> 
> <quote>
> structure       > sectioning > subsubsubsection @ level 6 : 0.0.0.1.3.1 -> One URL for All Projects
> ! LuaTeX error /usr/share/texmf/tex/context/base/l-file.lua:219: bad argument #1 to 'find' (string expected, got nil)
> stack traceback:
>        [C]: in function 'find'
>        /usr/share/texmf/tex/context/base/l-file.lua:219: in function 'collapsepath'
>        /usr/share/texmf/tex/context/base/grph-inc.lua:373: in function 'forbiddenname'
>        /usr/share/texmf/tex/context/base/grph-inc.lua:387: in function </usr/share/texmf/tex/context/base/grph-inc.lua:385>
>        (tail call): ?
>        /usr/share/texmf/tex/context/base/grph-inc.lua:735: in function 'identifier'
>        /usr/share/texmf/tex/context/base/grph-inc.lua:753: in function 'identify'
>        <main ctx instance>:1: in main chunk.
> 
> system          > tex > error on line 330 in file v10TrainingGeneralClassEndUser.contex.tex: LuaTeX error  ...
> 
> 320       How You Get Access
> 321     \stopitemize
> 322
> 323     \subsubsubsection[one-url-for-all-projects]{One URL for All Projects}
> 324
> 325     A {\em project} in WiscWebCMS is the equivalent of a web site. You may
> 326     have access to multiple projects. For all projects you login at
> 327 \useURL[url2][https://wiscwebcms.wisc.edu][][https://wiscwebcms.wisc.edu]\from[url2].
> 328     With WiscWeb CMS you are logging into a web application to edit your
> 329     site.\crlf
> 330 >>  {\externalfigure[images/group54/26378/CMSLogin.jpg]}
> 331
> 332     \subsubsubsection[selecting-your-project]{Selecting Your Project}
> 333
> </quote>
> 
> That happens at the very first \externalfigure in the document. The specific error is:
> 
> ! LuaTeX error /usr/share/texmf/tex/context/base/l-file.lua:219: bad argument #1 to 'find' (string expected, got nil)
> 
> Wah? I can successfully use display from the commandline in the same dir as the context file on that path shown in the quoted output and it opens the image. So, it's not the image file or the path--they are both fine.
> 
> Any ideas anyone?


Do you get the same error message when you put this short example in the same directory as document?

\starttext
\externalfigure[images/group54/26378/CMSLogin.jpg]
\stoptext

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-12-12 18:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 17:45 Guy Stalnaker
2012-12-12 18:12 ` Wolfgang Schuster [this message]
2012-12-12 18:27   ` Guy Stalnaker
2012-12-12 18:44     ` Wolfgang Schuster
2012-12-12 19:26       ` Hans Hagen
2012-12-13 23:22       ` Guy Stalnaker
2012-12-15 22:44         ` Guy Stalnaker
2012-12-16  9:22           ` Wolfgang Schuster
2012-12-16 14:17             ` Hans Hagen
2012-12-19 20:38               ` Guy Stalnaker
2012-12-19 20:57                 ` luigi scarso
2012-12-21 21:51                 ` Hans Hagen

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=567971B0-5AB4-47C4-9665-5F183E202545@gmail.com \
    --to=wolfgang.schuster@gmail.com \
    --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).