ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Minimals (solved)
Date: Thu, 29 Oct 2009 14:51:07 +0100	[thread overview]
Message-ID: <6faad9f00910290651p75f481c0i6497eaa5067e73a6@mail.gmail.com> (raw)
In-Reply-To: <4AE2EBF2.5080408@wxs.nl>

On Sat, Oct 24, 2009 at 12:58, Hans Hagen wrote:
> Mojca Miklavec wrote:
>
>> The reason for this weird behavior is that we removed almost all the
>> variables from setuptex back in May 2009.
>>
>> This is just the contrary of what Hans tried to achieve several years
>> ago to overwrite the tetex's pollution with variables. Now that hardly
>> anyone uses tetex ... we didn't bother about that any more, but it is
>> still a problem if one sets up an old distribution in .bashrc and then
>> tries to use a new one. (In that case the old ConTeXt behaves just as
>> impolitely as tetex and hinders the ability to use the latest one.)
>
> so, maybe we can add an extra script that resets these variables?

I would prefer to leave an option to users to set those variables
themselves (at least to those who know what they are doing).

Mojca
___________________________________________________________________________________
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:[~2009-10-29 13:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 14:59 Minimals Jörg Hagmann
2009-10-06 11:46 ` Minimals Hans Hagen
2009-10-06 12:58 ` Minimals Aditya Mahajan
2009-10-06 13:10   ` Minimals Jörg Hagmann
2009-10-06 13:21     ` Minimals Aditya Mahajan
2009-10-06 13:57       ` Minimals Jörg Hagmann
2009-10-06 14:06         ` Minimals luigi scarso
2009-10-06 14:12           ` Minimals Jörg Hagmann
2009-10-06 14:25             ` Minimals luigi scarso
2009-10-06 14:51               ` Minimals Jörg Hagmann
2009-10-06 14:56                 ` Minimals luigi scarso
2009-10-06 15:00                   ` Minimals Jörg Hagmann
2009-10-06 15:01                     ` Minimals luigi scarso
2009-10-06 15:08                       ` Minimals luigi scarso
2009-10-06 15:46                         ` Minimals Mojca Miklavec
2009-10-06 15:54                           ` Minimals luigi scarso
2009-10-06 17:00                       ` Minimals Hans Hagen
2009-10-09  7:24                         ` Minimals Jörg Hagmann
2009-10-21 14:54                         ` Minimals (solved) Jörg Hagmann
2009-10-21 15:24                           ` Mojca Miklavec
2009-10-24 11:58                             ` Hans Hagen
2009-10-29 13:51                               ` Mojca Miklavec [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=6faad9f00910290651p75f481c0i6497eaa5067e73a6@mail.gmail.com \
    --to=mojca.miklavec.lists@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).