ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [***SPAM***] File access for sourc, graphic, and pictures
Date: Mon, 11 Mar 2013 08:30:30 +0100	[thread overview]
Message-ID: <0F644AF8-33F1-4ED7-B2D9-207E92560C72@web.de> (raw)
In-Reply-To: <20130308080258.GY29684@homerow>

Hi All,


Am 08.03.2013 um 09:02 schrieb Marco Patzer <homerow@lavabit.com>:

> On 2013–03–08 hwitloc@gmail.com wrote:
> 
>> I am just learning ConTeXt, so please bare with me.  In all of the
>> documentation that I've read so far, it shows the names of
>> imported photographs, graphs, blocks, etc as a simple filename
>> without any filename extensions or pathnames.
> 
> Avoid hard coded path names in your files, it makes them less
> portable. ConTeXt adds the file name extension automatically,
> there's usually no need to specify it manually.

IMHO, I would disagree. That is, using hardcoded full paths breaks portability.
The trick is using relative paths! In other words using paths "./dir/file" or "../dir/file"
is very portable. 

Furthermore, using relative paths helps finding the files, especially for larger
projects or with collaborative work. Thats is for editing.

Please, do not get me wrong, using the theproject environments does have 
its caveats.

regards
	Keith.


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


      parent reply	other threads:[~2013-03-11  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  5:14 hwitloc
2013-03-08  8:02 ` Marco Patzer
2013-03-08  7:22   ` d.henman
2013-03-11  7:30   ` Keith J. Schultz [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=0F644AF8-33F1-4ED7-B2D9-207E92560C72@web.de \
    --to=keithjschultz@web.de \
    --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).