From: Mica Semrick <paperdigits@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with context in windows
Date: Sun, 18 Aug 2013 12:55:06 -0700 [thread overview]
Message-ID: <CABkomp+Vo3fkuwBQ4N96e6FHPokGFbDHxJPro=V5HEZiCJAXkw@mail.gmail.com> (raw)
In-Reply-To: <40DEBB8914D88242B1236EC1BB2680837465AB@CAHIER.gst.uqam.ca>
[-- Attachment #1.1: Type: text/plain, Size: 2107 bytes --]
Try running:
mktexlsr
texexec --make --all
mktexlsr
texexec --make --xtx --all
mtxrun --selfupdate
mtxrun --generate
luatools --generate
context --make
You may not need to run all of them... but it is easier this way.
Best,
Mica
On Fri, Aug 16, 2013 at 12:29 PM, Oualkacha, Karim
<oualkacha.karim@uqam.ca>wrote:
> Hi,****
>
> ** **
>
> I installed conTeXt in windows following the steps in the website ****
>
>
> http://wiki.contextgarden.net/Windows_Installation:_ConTeXt_Suite_with_SciTe#Install_SciTe
> ****
>
> ** **
>
> I have a PC with windows 7, ruby is already installed, and I have MikeTex
> 2.9 already installed and as text editor WinEdt. To test if everything
> work, I created a file Test.tex ****
>
> ** **
>
> \starttext****
>
> ** **
>
> Test****
>
> ** **
>
> \stoptext****
>
> ** **
>
> ** **
>
> When I executed it in WinEdt I didn’t have any error message, however,
> there is no PDF file created for the Test.tex file [ConTeXt Compilation
> Report (Pages: 0), Errors : 0]. ****
>
> ** **
>
> In a command-line window (cmd) I tried the command context to see what is
> the problem: I got the following message: ****
>
> warnings no lua configuration files found****
>
> no texmf paths are defined <using TEXMF> ****
>
> ** **
>
> I tried also texexec command and I got the following message:****
>
> mtxrun ! kpse fallback with programme `context` initialized in 0.062
> seconds ****
>
> ** **
>
> Any Help Please!****
>
> ** **
>
> Karim****
>
> ** **
>
> ** **
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 4674 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-08-18 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 19:29 Oualkacha, Karim
2013-08-18 19:55 ` Mica Semrick [this message]
2013-08-19 14:42 ` Oualkacha, Karim
2013-08-19 16:37 ` Mica Semrick
2013-08-19 21:44 ` Oualkacha, Karim
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='CABkomp+Vo3fkuwBQ4N96e6FHPokGFbDHxJPro=V5HEZiCJAXkw@mail.gmail.com' \
--to=paperdigits@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).