From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: spaces in file names
Date: Wed, 13 Jan 2010 12:16:49 +0100 [thread overview]
Message-ID: <fe8d59da1001130316o5126ce1as95455e248ef3a72b@mail.gmail.com> (raw)
In-Reply-To: <CE0BC213-A240-4D56-A663-280A072EF005@uva.nl>
On Wed, Jan 13, 2010 at 12:12 PM, Hans van der Meer <H.vanderMeer@uva.nl> wrote:
>> what about
>> \setupexternalfigures[directory={\DATADIRECTORY}]
>> ?
>
> Tried it but NO. That didn't work. Without a space in the directory name I
> can find the picture. But as soon as a space gets in the directory name then
> the picture file is not found.
:-(
the last one...
\setupexternalfigures[directory={"\DATADIRECTORY"}]
--
luigi
___________________________________________________________________________________
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:[~2010-01-13 11:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 10:51 Hans van der Meer
2010-01-13 10:55 ` luigi scarso
2010-01-13 11:12 ` Hans van der Meer
2010-01-13 11:16 ` luigi scarso [this message]
2010-01-13 11:26 ` Hans van der Meer
2010-01-13 11:30 ` luigi scarso
2010-01-13 11:32 ` Wolfgang Schuster
2010-01-13 11:38 ` Hans van der Meer
2010-01-13 11:42 ` Wolfgang Schuster
2010-01-13 13:23 ` Peter Rolf
2010-01-13 15:35 ` Otared Kavian
2010-01-13 16:30 ` Hans van der Meer
2010-01-13 17:59 ` Hans Hagen
2010-01-13 19:34 ` Hans van der Meer
2010-01-13 19:46 ` Hans van der Meer
2010-01-13 20:39 ` Hans Hagen
2010-01-14 20:16 ` Text backgrounds once again Matthias Weber
2010-01-14 20:55 ` Text backgrounds once again (follow-up) Matthias Weber
2010-01-14 21:39 ` Willi Egger
2010-01-14 21:45 ` Matthias Weber
2010-01-14 22:15 ` Aditya Mahajan
2010-01-15 12:58 ` Matthias Weber
2010-01-14 21:48 ` NOT reusing figures Matthias Weber
2010-01-14 22:36 ` Hans Hagen
2010-01-15 0:58 ` Matthias Weber
2010-01-15 15:26 ` reusing figures ok - problem with hiding blocks in MKIV Matthias Weber
2010-01-18 9:00 ` Hans Hagen
2010-01-22 15:19 ` More questions about hiding/reusing blocks Matthias Weber
2010-01-22 15:55 ` Calligraphic letters in Mark IV Matthias Weber
2010-01-22 17:29 ` Hans Hagen
2010-01-22 17:49 ` Matthias Weber
2010-01-22 17:53 ` Wolfgang Schuster
2010-01-22 18:14 ` Matthias Weber
2010-01-22 18:20 ` Wolfgang Schuster
2010-01-24 13:34 ` Hans Hagen
2010-01-24 21:17 ` Aditya Mahajan
2010-01-24 22:45 ` Hans Hagen
2010-01-24 16:57 ` More questions about hiding/reusing blocks Hans Hagen
[not found] ` <A4C3BD19-AAE4-4033-AA0E-A2C2DB586BFB@indiana.edu>
2010-01-25 0:15 ` Hans Hagen
2010-01-14 2:00 ` spaces in file names Vladimir Lomov
2010-01-13 19:59 ` Thomas A. Schmitz
2010-01-13 20:32 ` 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=fe8d59da1001130316o5126ce1as95455e248ef3a72b@mail.gmail.com \
--to=luigi.scarso@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).