From: "Jeff Smith" <ascarel@gmail.com>
Subject: Re: Working with environments and projects
Date: Wed, 17 Jan 2007 14:27:49 -0500 [thread overview]
Message-ID: <2e8813a0701171127g63238334ob28f4464ca2eaeb3@mail.gmail.com> (raw)
In-Reply-To: <45AD584C.1090402@elvenkind.com>
On 1/16/07, Taco Hoekwater <taco@elvenkind.com> wrote:
> TeXExec normally say this if there is not any file mentioned
> on the command line, or if it cannot find any file based on the
> name supplied on that commandline.
Okay. As a verification I processed my document manually with the
command line instead of using my editor (not scite), and what do you
know, it worked!
I just had to adjust my compiler information in my editor settings,
since my component files were now placed a folder further down in the
tree. Oopsie.
Glad to know I had the ConTeXt part okay first, this time. :-)
So thanks Taco, and all!
JFS
JF
next prev parent reply other threads:[~2007-01-17 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 16:14 Jeff Smith
2007-01-16 19:15 ` Henning Hraban Ramm
2007-01-16 19:35 ` Jeff Smith
2007-01-16 22:57 ` Taco Hoekwater
2007-01-17 19:27 ` Jeff Smith [this message]
2007-01-17 13:02 ` Sanjoy Mahajan
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=2e8813a0701171127g63238334ob28f4464ca2eaeb3@mail.gmail.com \
--to=ascarel@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).