ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: TeXworks or TeXItEasy as ConTeXt editors
Date: Sat, 5 Aug 2017 13:40:40 +0200	[thread overview]
Message-ID: <f2299716-fcd0-8bb2-5755-ee1b24503a67@gmx.es> (raw)

Dear list,

I’m writing an introduction to ConTeXt in Spanish.

Before any new user can start compiling ConTeXt sources, I realize that
I have to explain how to configure an editor for ConTeXt.

Since I plan to deal with the latest beta from the ConTeXt Suite, I need
to explain how to deploy it.

I use Geany in Linux and Notepad++ in Windows. But they are too complex
for newbies. TeXworks seems the best option to start with (and to
explain to newcomers).

I compile my documents with the following commands:

   source ~/context/tex/setuptex && contextjit document.tex

I had never problems with that. But as soon as I started to test Qt
applications, I cannot use this.

I mean, the commands above don’t work either with TeXworks or TexitEasy.

Does anyone know how to make the previous commands work with TeXworks?

Setting paths is something I want to avoid, since it is potentially
dangerous for newbies.

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2017-08-05 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05 11:40 Pablo Rodriguez [this message]
2017-08-05 11:50 ` Arthur Reutenauer
2017-08-05 15:08   ` Pablo Rodriguez
2017-08-05 13:36 ` Jean-Pierre Delange
2017-08-05 19:35   ` Pablo Rodriguez
2017-08-06  6:41     ` Jean-Pierre Delange

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=f2299716-fcd0-8bb2-5755-ee1b24503a67@gmx.es \
    --to=oinos@gmx.es \
    --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).