ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: global cross file refs
Date: Wed, 11 Oct 2000 10:38:02 +0200	[thread overview]
Message-ID: <3.0.6.32.20001011103802.019c4c90@pop.wxs.nl> (raw)
In-Reply-To: <39E37B3A.1AFF9E2F@pobox.com>

At 10:25 PM 10/10/00 +0200, Berend de Boer wrote:
>Hans Hagen wrote:
>
>> the next release will have an option \setupreferencing[global=yes] which
>> permits you to omit the somefile:: prefix, but of course at the cost of
>> conflicting refs in multiple loaded files. Nevertheless, sometimes this
>> feature canbe handy.
>
>I've used \useexternaldocument heavily, so this is handy.
>
>Is it possible to limit what is global? I.e. I seldom need figures or
>chapters, but often I refer to class definitions, or data models. So a
>kind of selective global, perhaps based on prefix or something like
>that.

Local and prefixed things have a higher priority anyway. I will implement a
more advanced prefix mechanism [nested] some day soon, since in etex the
penalty is not that high as in normal tex. Btw, if you say
\setuphead[chapter][prefix=+] you get auto prefixing, and when you say
\chapter[someref]{...} the someref becomes the prefix, which can safe you
some troubles. 

Hans 
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  parent reply	other threads:[~2000-10-11  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-10 16:36 Hans Hagen
     [not found] ` <39E37B3A.1AFF9E2F@pobox.com>
2000-10-11  8:38   ` Hans Hagen [this message]
2000-10-12 12:49     ` Berend de Boer

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=3.0.6.32.20001011103802.019c4c90@pop.wxs.nl \
    --to=pragma@wxs.nl \
    --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).