From: "Meer H. van der" <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upto current
Date: Wed, 20 Mar 2013 09:05:59 +0100 [thread overview]
Message-ID: <426BD0E4-2BA5-4101-AED6-D5E9FB4365D8@uva.nl> (raw)
In-Reply-To: <918676C5-3AD6-456C-B75D-3A4F130D1CBD@gmail.com>
On 20 mrt. 2013, at 07:05, Otared Kavian <otared@gmail.com>
wrote:
>
> On 19 mars 2013, at 19:47, Aditya Mahajan <adityam@umich.edu> wrote:
>
>> […]Although most active users use ConTeXt standalone and are willing to update frequently, TL still plays an important role in introducing new users to ConTeXt. An experienced TeX user who wants to try ConTeXt is more likely to try ConTeXt distributed as part of TL rather than ConTeXt standalone. When there are serious bugs with ConTeXt TL, it gives the impression that ConTeXt is not a mature macro package.
>
> Hi,
>
>
> 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.
>
Being a fan of ConTeXt, I strongly agree with the above plea to make ConTeXt a painless experience for most users. I think of myself as someone who knows a bit of computers and programming. But even then I can feel sometimes something of what others must experience when nothing seems to work and no idea why.
The best advocate for ConTeXt is an "invisible" ConTeXt for all those out there who just want their stuff made printer ready without hassles. ConTeXt deserves a wider use.
Hans van der Meer
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-20 8:05 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 [this message]
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
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=426BD0E4-2BA5-4101-AED6-D5E9FB4365D8@uva.nl \
--to=h.vandermeer@uva.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).