ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re:  \at and \in woes with \startcomponent….\stopcomponent
Date: Fri, 7 Jun 2013 08:37:02 -0400	[thread overview]
Message-ID: <CAFMOkGWCHicP3onbOydc0K_iYWGN+t=YaqF8zg2r71VG8HszNg@mail.gmail.com> (raw)
In-Reply-To: <51AE3238.1020208@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]

Hi, Hans—

I reinstalled the ConTeXt standalone and still get links to null pages with
\at and \in using the latest version (ConTeXt  ver: 2013.06.07 12:25 MKIV
beta).

Alan


On Tue, Jun 4, 2013 at 2:30 PM, Hans Hagen <pragma@wxs.nl> wrote:

> On 6/4/2013 8:03 PM, Marco Patzer wrote:
>
>> On 2013–06–04 Hans Hagen wrote:
>>
>>  On 6/4/2013 2:06 PM, Alan Bowen wrote:
>>>
>>>> In my component files, the tools for cross-references work except for
>>>> \at and \in. These commands produce links that display properly but go
>>>> to a null page, i.e., nowhere.
>>>>
>>>
>>> it's more an side effect of duplicate flushing notes .. i fixed
>>> something, hopefully it didn't break something else
>>>
>>
>> ! I can't find file `scrp-ini.mkiv'.
>> <to be read again>
>> \relax
>> l.392 \loadmarkfile{scrp-ini}
>>
>
> weird ... i'll make a new zip
>
>
> 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 <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/<http://foundry.supelec.fr/projects/contextrev/>
> wiki     : http://contextgarden.net
> ______________________________**______________________________**
> _______________________
>

[-- Attachment #1.2: Type: text/html, Size: 3389 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2013-06-07 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 12:06 Alan Bowen
2013-06-04 17:55 ` Hans Hagen
2013-06-04 18:03   ` Marco Patzer
2013-06-04 18:30     ` Hans Hagen
2013-06-07 12:37       ` Alan Bowen [this message]
2013-06-07 13:13         ` Hans Hagen
2013-06-07 18:34           ` Alan Bowen

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='CAFMOkGWCHicP3onbOydc0K_iYWGN+t=YaqF8zg2r71VG8HszNg@mail.gmail.com' \
    --to=bowenalan03@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).