From: Jesse Alama <alama@stanford.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: AUCTeX and ConTeXt
Date: Sat, 28 Jun 2008 11:25:41 -0700 [thread overview]
Message-ID: <m263rtju1m.fsf@stanford.edu> (raw)
In-Reply-To: <1214676504.7122.36.camel@elbereth> (Charles P. Schaum's message of "Sat, 28 Jun 2008 13:08:24 -0500")
"Charles P. Schaum" <verbo.solo@sbcglobal.net> writes:
> I really like the support that AUCTeX gives for ConTeXt. Actually, in
> general it does well with any flavor. I'll have to RTFM to see what I
> can do to start a new file specifically in ConTeXt, plain, or whatever,
> not just LaTeX.
>
> The weird thing is that it reports unspecified "problems" at the end of
> running context but no such problems really exist.
>
> The trivial snippet:
>
> \starttext
> Hello, world!
> \stoptext
>
> yields the message buffer:
>
> Updating define menu...
> Updating setup menu...
> Updating other macro's menu...
> Updating project structure menu...
> Updating section block menu...
> Updating section menu...
> Updating...done
> Type `C-c C-l' to display results of compilation.
> ConTeXt: problems after {1} page.
>
> The pdf generated is, however, entirely satisfactory, as are all texted
> documents.
>
> My strategy is to ignore it. This appears specific to AUCTeX, in this
> case running on GTK Emacs 22 / Ubuntu 8.04. By contrast, I have minimal
> to no problems on my OS X installation.
What are the exit codes for texexec? Perhaps these are different from
what auctex is expecting.
Jesse
--
Jesse Alama (alama@stanford.edu)
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-28 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 18:08 Charles P. Schaum
2008-06-28 18:25 ` Jesse Alama [this message]
2008-06-29 10:34 ` Thomas A. Schmitz
2008-06-30 6:10 ` Jean Magnan de Bornier
2008-06-30 22:29 ` Charles P. Schaum
2008-07-01 6:04 ` Patrick Gundlach
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=m263rtju1m.fsf@stanford.edu \
--to=alama@stanford.edu \
--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).