ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Yanrui Li <liyanrui.m2@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bugs in beta
Date: Fri, 8 May 2009 17:46:38 +0800	[thread overview]
Message-ID: <c3f901470905080246s57fc8692n2a7659fd6273d161@mail.gmail.com> (raw)
In-Reply-To: <4A03DD9C.8010205@wxs.nl>

On Fri, May 8, 2009 at 3:22 PM, Hans Hagen <pragma@wxs.nl> wrote:
> Yanrui Li wrote:
>>
>> On Fri, May 8, 2009 at 5:17 AM, Hans Hagen <pragma@wxs.nl> wrote:
>>>
>>> Alan BRASLAU wrote:
>>>>
>>>> I still get a major sectioning bug using the new beta mkiv
>>>> 1. minimals from the garden
>>>> 2. beta from http://pragma-ade.nl/context/beta/cont-tmf.zip
>>>>
>>>> Am I alone in seeing this?
>>>
>>> i'm still strugling with defaults (it's not so much a matter of not
>>> working
>>> but more of how to set up the defaults with reasonable inheritance) so it
>>> will take a while before things stabelize
>>>
>>> i uploaded a beta with a (temp) fix
>>>
>>
>> I failed to update the latest beta and got the following error message:
>
> ok, will be fixed in 10 min
>

Recently I have found some environment variables in setuptex script
are commented out sometimes, such as TEXMFLOCAL, TEXMFCONTEXT and so
on. Is this be done deliberately?

-- 
Best wishes,
Li Yanrui
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-05-08  9:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 19:58 Thomas A. Schmitz
2009-05-06 20:12 ` Wolfgang Schuster
2009-05-06 20:25   ` Thomas A. Schmitz
2009-05-06 20:33     ` Wolfgang Schuster
2009-05-07  8:31 ` Henning Hraban Ramm
2009-05-07  8:41   ` Thomas A. Schmitz
2009-05-07 10:47     ` Henning Hraban Ramm
2009-05-07 11:31       ` Hans Hagen
2009-05-07 12:44       ` Hans Hagen
2009-05-07 13:11         ` Henning Hraban Ramm
2009-05-07 13:27           ` Hans Hagen
2009-05-07 13:51             ` Alan BRASLAU
2009-05-07 13:56               ` Wolfgang Schuster
2009-05-07 14:21                 ` Alan BRASLAU
2009-05-07 11:38   ` Wolfgang Schuster
2009-05-07 13:08     ` Henning Hraban Ramm
2009-05-07 13:28       ` Wolfgang Schuster
2009-05-07 14:32         ` Henning Hraban Ramm
2009-05-07 14:43           ` Wolfgang Schuster
2009-05-07 16:34   ` Hans Hagen
2009-05-07 17:21     ` Henning Hraban Ramm
2009-05-07 18:04       ` Hans Hagen
2009-05-07 20:01         ` Alan BRASLAU
2009-05-07 21:17           ` Hans Hagen
2009-05-07 23:06             ` Yanrui Li
2009-05-07 23:12               ` Yanrui Li
2009-05-08  7:22               ` Hans Hagen
2009-05-08  9:46                 ` Yanrui Li [this message]
2009-05-08 19:36             ` Alan BRASLAU
2009-05-08 19:42               ` Hans Hagen
2009-05-10 16:44         ` bugs in beta (footnotes) Henning Hraban Ramm
2009-05-12 17:07           ` Henning Hraban Ramm
2009-05-13 16:00             ` Wolfgang Schuster
2009-05-14 14:08               ` 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=c3f901470905080246s57fc8692n2a7659fd6273d161@mail.gmail.com \
    --to=liyanrui.m2@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).