ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jarimatti Valkonen <javalkon@hytti.uku.fi>
Subject: Re: Making a verbatim file for another language
Date: Sat, 30 Dec 2006 23:24:31 +0200	[thread overview]
Message-ID: <8D5DE4FB-9B7B-4D7E-906F-E1CA75146617@hytti.uku.fi> (raw)
In-Reply-To: <5BEB99A9-D3A1-46BD-ABF1-86765086161F@mac.com>

cormullion@mac.com kirjoitti 30.12.2006 kello 16.18:

>
> On 2006-12-30, at 09:22.0, Jarimatti Valkonen wrote:
>
>> Works fine here. System: Mac OS 10.4.8, using default Vim (6.2:
>> yikes, thats old!).
>> ConTeXt  ver: 2006.08.08 21:51  fmt: 2006.11.1
>
> Thanks Jarimatti for sharing that. It suggests that my week-old
> installation isn't the most up to date one:
>
>> ConTeXt  ver: 2005.01.31  fmt: 2006.7.23  int: english  mes: english
>
> I obviously chose a suboptimal option when I started i-Installer.
> (Not difficult, really - it felt like a first attempt to hot-wire a
> Boing 747... :-)

That is odd, as I haven't updated my ConTeXt in a while. My ConTeXt  
updater i-Package (context-update.ii2) is dated 2006/10/06 meaning  
that it's almost three months old. And I'm still using the teTeX  
installation that is apparently no longer available (tex.ii2).

Anyway, I use ConTeXt from the shell (Terminal.app) and have defined  
the following aliases:
---
# ConTeXt stuff
alias texmfstart="ruby /usr/local/teTeX/share/texmf.local/scripts/ 
context/ruby/texmfstart.rb"
alias context="texmfstart texexec"
---
You could try those, just change the name and path to texmfstart.rb  
so that it matches your installation. After adding the aliases you  
can just issue command 'context myfile.tex' and the file gets processed.

-- 
Jarimatti Valkonen
javalkon@hytti.uku.fi

  reply	other threads:[~2006-12-30 21:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-25  9:24 cormullion
2006-12-25 10:38 ` Taco Hoekwater
2006-12-25 15:22   ` cormullion
2006-12-26 16:59   ` Henning Hraban Ramm
2006-12-26 18:47     ` Mojca Miklavec
2006-12-26 21:25       ` cormullion
2006-12-27 21:41         ` Aditya Mahajan
2006-12-28  8:15           ` cormullion
2006-12-28 17:09             ` Aditya Mahajan
2006-12-28 18:05               ` cormullion
2006-12-28 23:47                 ` Mojca Miklavec
2006-12-29  8:46                   ` cormullion
2006-12-29 13:09                     ` Mojca Miklavec
2006-12-29 15:37                       ` Aditya Mahajan
2006-12-29 15:42                       ` cormullion
2006-12-29 15:59                         ` Aditya Mahajan
2006-12-29 16:36                           ` cormullion
2006-12-29 18:39                         ` Mojca Miklavec
2006-12-30  9:22               ` Jarimatti Valkonen
2006-12-30 14:18                 ` cormullion
2006-12-30 21:24                   ` Jarimatti Valkonen [this message]
2006-12-31 11:51                     ` cormullion
2006-12-31 13:40                       ` Mojca Miklavec
2006-12-31 16:57                         ` cormullion
2006-12-25 18:12 ` Mojca Miklavec
2006-12-25 19:37   ` Aditya 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=8D5DE4FB-9B7B-4D7E-906F-E1CA75146617@hytti.uku.fi \
    --to=javalkon@hytti.uku.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).