From: Mari Voipio <mari.voipio@iki.fi>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: ConTeXt in SciTe in Windows, non-working commands in Tools menu
Date: Tue, 23 Aug 2011 11:59:28 +0300 [thread overview]
Message-ID: <CAGbDsP2=b-CvFG7785EUT9BYie=E3SgFBx96O7iK+3L5NAgTCA@mail.gmail.com> (raw)
Hello!
While struggling with the prefixed referencing system, I found two
commands in the Tools menu that fail miserably. As the commands I
normally use (Ctrl+1/Process TeX file, Process and Arrange, Generate
Formats (luaTeX) work fine, the problem is fairly local and neither is
critical.
If I remember it correctly, the command Tools | Update ConTeXt has
never worked for me, but the error message has been different. What I
get now is
>mtxrun --autogenerate texshow --update --force
mtxrun | kpse fallback with progname 'context' initialized in
0.03 seconds>Exit code: 1
Updating per se works, because when I did it on the command line, i.e. ran
first-setup.bat --context=current
something definitely came in and there are changes in for example
directory texmf-modules (and yes, I did remember to generate formats
and that command really worked).
The other command that fails is Tools | Open Logfile (or Ctrl+E) and
I'm fairly sure this one worked on the W7 laptop that I installed in
August 2011 with the then up-to-date versions of SciTe and ConTeXt.
The error message is pretty interesting, too:
> Lua: error checking global scope for command
I can of course open the log file in SciTe via the File menu, so this
isn't a major problem, just an annoyance. I used to like my Ctrl+E
quite a bit...
The SciTe+ConTeXt combo I'm using now is on a 64-bit Windows7 laptop
and I installed it about 10 weeks ago onto a brand new computer. My
SciTe says it's version 2.26 of May 25, 2011. It is quite possible I'm
running a different version from what's in the ConTeXt package as I
fetch my SciTe separately from Scintilla so I get a civilised Windows
installer that sets Windows context menus and other goodies all at one
click. (Yes, I'm da lazy Windows user who doesn't want to bother her
brain with any tweaking if that can be avoided.)
From the world of Windows,
Mari
___________________________________________________________________________________
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 reply other threads:[~2011-08-23 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 8:59 Mari Voipio [this message]
2011-08-23 9:13 ` 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='CAGbDsP2=b-CvFG7785EUT9BYie=E3SgFBx96O7iK+3L5NAgTCA@mail.gmail.com' \
--to=mari.voipio@iki.fi \
--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).