From: "Joshua Krämer" <joshua.kraemer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: ntg-context-wvrSQK3plZs@public.gmane.org
Subject: Re: A default editor for ConTeXt standalone?
Date: Sun, 16 Feb 2014 22:21:26 +0100 [thread overview]
Message-ID: <20140216222126.41d3c7fc@Klapprechner1.site> (raw)
In-Reply-To: <20140205074106.5ec80b2d@aga-netbook>
On 2014-02-05, 7:41, Marcin Borkowski wrote:
> Hi all,
>
> just a thought. Some time ago wise people decided to include TeXworks
> into TeXlive, so that newbies installing TeXlive can get a
> "batteries-included" package (not having to choose/install an editor).
> Would it be (a) reasonable and (b) not too much time-consuming to do a
> similar move with ConTeXt standalone?
I think, people who want a batteries-included distribution should
install TeXlive, which also includes ConTeXt. In my opinion, it's
great to have ConTeXt Standalone as a more lightweight package that
doesn't include all the stuff I don't need. There is also a Wiki page
with informations about editors and their ConTeXt support, which I think
should be enough for the strange users that don't have an editor yet
(or for users looking for an editor with better ConTeXt support).
Kind regards,
Joshua Krämer
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2014-02-16 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 6:41 Marcin Borkowski
2014-02-05 8:54 ` Keith J. Schultz
2014-02-05 9:49 ` Hans Hagen
2014-02-16 21:21 ` Joshua Krämer [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=20140216222126.41d3c7fc@Klapprechner1.site \
--to=joshua.kraemer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ntg-context-wvrSQK3plZs@public.gmane.org \
/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).