ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Otared Kavian <otared@gmail.com>,
	Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: upto current
Date: Wed, 20 Mar 2013 10:37:56 +0100	[thread overview]
Message-ID: <51498374.6070904@wxs.nl> (raw)
In-Reply-To: <CALBOmsaM7axYKNZf9y7xyYHj_gJLwcT7fhxZN3zcmFO00SNRuQ@mail.gmail.com>

On 3/20/2013 10:27 AM, Mojca Miklavec wrote:
> On Wed, Mar 20, 2013 at 9:40 AM, Hans Hagen wrote:
>> On 3/20/2013 7:05 AM, Otared Kavian wrote:
>>
>>> So my pledge is this: make any stable version of ConTeXt in TeXLive so
>>> that it works and typesets a tex-file « out of the box », without needing to
>>> issue any command other than:
>>>          context myfile.tex
>>> This is the case with LaTeX inside TeXLive, and so I cannot see any strong
>>> reason for ConTeXt not having the same behavior.
>>
>> if it doesn't work that way something is wrong ... mtxrun (to which context
>> is an alias) is selfcontained and will generate its own file database and
>> then context will generat eits own format (even after an update) so ...
>
> Yes, this seems a bit weird. ConTeXt in TeX Live 2012 might have had
> bugs, but it should have at least worked out of the box.
>
> It is possible that your copy actually became problematic *after*
> issuing those few commands. In particular, running "texexec --make en"
> would create a new format at a different location than the system
> would put it. As a consequence all further updates become shadowed by
> the old manually created format and you would need to run "texexec
> --make en" manually for every update, else MKII becomes broken (not
> that there were many updates, but this could serve as an example).

this is indeed an issue ... recently I spend a few hours tracking down 
an issue just to find out that for whatever reason a file had ended up 
in a local path .. hard to track down .. one should also keep in mind 
that tds is set up in a way that more or less assumes that there are no 
files in the tree with the same name (at least not in the same category) 
because at some point the order of dir entries start to matter

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
___________________________________________________________________________________

  reply	other threads:[~2013-03-20  9:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 18:16 Hans Hagen
2013-03-19 18:47 ` Aditya Mahajan
2013-03-19 19:05   ` Hans Hagen
2013-03-20  1:52     ` Aditya Mahajan
2013-03-20  6:05   ` Otared Kavian
2013-03-20  8:05     ` Meer H. van der
2013-03-20  8:19     ` Keith J. Schultz
2013-03-20  8:40     ` Hans Hagen
2013-03-20  9:27       ` Mojca Miklavec
2013-03-20  9:37         ` Hans Hagen [this message]
2013-03-20  8:12 ` Keith J. Schultz
2013-03-20  8:25   ` Marcin Borkowski
2013-03-20 17:54     ` Keith J. Schultz
2013-03-21 10:19       ` Mojca Miklavec
2013-03-21 10:32         ` Alan BRASLAU
2013-03-21 14:26           ` Marcin Borkowski
2013-03-22  7:31             ` Keith J. Schultz
2013-03-22  8:26               ` command reference (was: upto current) Peter Münster
2013-03-22 10:11                 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-03-22 10:25                   ` command reference Peter Münster
2013-03-22 12:04                   ` Hans Hagen
2013-03-22 14:42                   ` command reference (was: upto current) Sietse Brouwer
2013-03-22 16:07                     ` Sietse Brouwer
2013-03-22 17:21                       ` command reference Hans Hagen
2013-03-24 21:48                         ` Sietse Brouwer
2013-03-25  9:42                       ` command reference (was: upto current) Keith J. Schultz
2013-03-25  9:34                 ` Keith J. Schultz
2013-03-22 14:19               ` upto current Bill Meahan
2013-03-22 14:32                 ` Taco Hoekwater
2013-03-22 14:37                   ` luigi scarso
2013-03-22 14:47                 ` Hans Hagen
2013-03-25  8:02                 ` Keith J. Schultz
2013-03-20  8:49   ` 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=51498374.6070904@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    /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).