Am 12.12.2012 um 19:27 schrieb Guy Stalnaker :

Wolfgang,

With the same context headers in the document as are in the 'real' document, yes, same error. I've modified the image to different images in the same directory and a different image in another directory and still get the same error.

I checked and the only changes made to my system this week were some ruby packages I installed yesterday, so there should have been no changes to the context environment itself.

The only other thing I can think of is something awry with Dropbox, which is where all of these files reside. Except I can edit/view images and documents. It's just context that seems to have an issue.

Is there also a error when you have only the \externalfigure line in your document without additional setups? Wolfgang

Wolfgang, Sorry for the delay -- forgot I have the list emails filtered to a Context mail folder. DOH! But I'm seeing sporadic behavior. In more testing just now, I had an image work while other images do not work. This is odd. But, they are on Dropbox and I wonder now if that may be an issue--hence the 'nil' response for the image path, perhaps? I'm going to unlink and relink Dropbox and see if that helps. More later. Regards, Guy On 12/12/2012 12:44 PM, Wolfgang Schuster wrote:

Am 12.12.2012 um 19:27 schrieb Guy Stalnaker :

...

Wolfgang,

With the same context headers in the document as are in the 'real' document, yes, same error. I've modified the image to different images in the same directory and a different image in another directory and still get the same error.

I checked and the only changes made to my system this week were some ruby packages I installed yesterday, so there should have been no changes to the context environment itself.

The only other thing I can think of is something awry with Dropbox, which is where all of these files reside. Except I can edit/view images and documents. It's just context that seems to have an issue.

Is there also a error when you have only the \externalfigure line in your document without additional setups?

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 ___________________________________________________________________________________

-- "There is only love, and then oblivion. Love is all we have to set against hatred." (paraphrased) Ian McEwan Guy Stalnaker, I^2@DOIT, 1210 West Dayton Street, Room 3209 CSS, Madison WI 53719-1220, jstalnak@wisc.edu, work 608.263.8035, cell 608.235.4718, fax 608.265.6681,

Am 15.12.2012 um 23:44 schrieb Guy Stalnaker :

In case anyone was following this thread -- nothing I have been able to do has eliminated the context error.

I have:

1. Unlinked/relinked Dropbox 2. Moved image files to new directories. 3. Renamed image files. 4. Used a test snippet of regular document headers with only the \starttext \externalfigure \stoptext 5. Used a test snippet of only the \starttext \externalfigure \stoptext

The compile 'nil' response error persists. After four days of continued errors I have had to seek an alternate method for creating the print document.

My thanks to those of you on this list who responded to my questions.

The last thing you can try is to remove your context installation and to reinstall it. Can you also provide one of your figures which causes problems. Wolfgang

I'm willing to give you an image, but it cannot be the images. I have edited the file and put systematically % before the /externalfigure lines then run context against the file. As I added the % the nil error shifted to the next /externalfigure. I stopped this after five times. I have confirmed, by the way, file/directory ownership with chown and privileges with chmod. They are set as they should be, so whatever is awry is not owner/privilege related. Another reason it cannot be the images is that I used context with the same document and the same images to successfully create a document. They were unchanged, to my knowledge, the next day when context started throwing the error. While it's conceivable that some agent might have modified the documents and/or my office Linux install overnight without my knowledge, that must be considered a very remote possibility. That said, I'm hard-pressed to figure out what can possibly have changed, overnight, such that context would suddenly begin throwing the errors. That is why I unlinked/relinked Dropbox. They could change something on their end. But that had no affect on the error. Nor did moving all the images that are in the document from multiple directories into one directory. I think Wolfgang may be correct that I should remove/purge my context installation. But I have to say that is not an encouraging course of action. Guy On 12/16/2012 08:17 AM, Hans Hagen wrote:

On 12/16/2012 10:22 AM, Wolfgang Schuster wrote:

...

Am 15.12.2012 um 23:44 schrieb Guy Stalnaker :

...

In case anyone was following this thread -- nothing I have been able to do has eliminated the context error.

I have:

1. Unlinked/relinked Dropbox 2. Moved image files to new directories. 3. Renamed image files. 4. Used a test snippet of regular document headers with only the \starttext \externalfigure \stoptext 5. Used a test snippet of only the \starttext \externalfigure \stoptext

The compile 'nil' response error persists. After four days of continued errors I have had to seek an alternate method for creating the print document.

My thanks to those of you on this list who responded to my questions.

The last thing you can try is to remove your context installation and to reinstall it.

Can you also provide one of your figures which causes problems.

indeed. it would be interesting to know what picture triggers a nil (i.e. a non picture) someplace in the pipeline

Hans

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________

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 ___________________________________________________________________________________

-- "There is only love, and then oblivion. Love is all we have to set against hatred." (paraphrased) Ian McEwan Guy Stalnaker, I^2@DOIT, 1210 West Dayton Street, Room 3209 CSS, Madison WI 53719-1220, jstalnak@wisc.edu, work 608.263.8035, cell 608.235.4718, fax 608.265.6681,

On 12/19/2012 9:38 PM, Guy Stalnaker wrote:

I'm willing to give you an image, but it cannot be the images. I have edited the file and put systematically % before the /externalfigure lines then run context against the file. As I added the % the nil error shifted to the next /externalfigure. I stopped this after five times. I have confirmed, by the way, file/directory ownership with chown and privileges with chmod. They are set as they should be, so whatever is awry is not owner/privilege related.

Another reason it cannot be the images is that I used context with the same document and the same images to successfully create a document. They were unchanged, to my knowledge, the next day when context started throwing the error. While it's conceivable that some agent might have modified the documents and/or my office Linux install overnight without my knowledge, that must be considered a very remote possibility.

That said, I'm hard-pressed to figure out what can possibly have changed, overnight, such that context would suddenly begin throwing the errors. That is why I unlinked/relinked Dropbox. They could change something on their end. But that had no affect on the error. Nor did moving all the images that are in the document from multiple directories into one directory.

There has been some cleanup of filename constructors but nor that drastic. Maybe some are (temporary) More sensitive so nil arguments but that is then an indication of some issue earlier in the chain. The comment and next one being a problem is weird. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------