From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typesetting documentation
Date: Mon, 24 Mar 2008 20:29:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0803242019100.11443@nqv-yncgbc> (raw)
In-Reply-To: <335E60C8-AEA3-4DED-AD01-9552C1DF0B53@science.uva.nl>
On Mon, 24 Mar 2008, Hans van der Meer wrote:
> I looked up what Aditya said can be found in the wiki and did:
>
> texmfstart texexec --module kpse:mult-ini.tex
>
> I get the following output on my console:
> 108 ~/Temp/tex: texmfstart texexec --module kpse:mult-ini.tex
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:641:in
> `initialize': Permission denied -
> /usr/local/texlive/texmf-context/tex/context/base/mult-ini.ted
> (Errno::EACCES)
> from
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:641:in
> `open'
> from
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:641:in
> `documentation'
> from
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:629:in
> `each'
> from
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:629:in
> `documentation'
> from
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:2778:in
> `send'
> from
> /usr/local/texlive/texmf-context/scripts/context/ruby/ctxtools.rb:2778
>
> The permissions of the directory involved can be seen from:
> ls -l /usr/local/texlive/texmf-context/tex/context
> ==>
> drwxr-xr-x 767 sysop staff 26078 11 mrt 18:31 base
>
> That is, texexec tries to write into a directory for which has no write
> access. I operate normally as myself and only for the installation of
> software assume the role of system operator (to hinder rogue programs and
> protect myself from stupid deletes, for example).
>
> Do I understand correctly from this, that unless one has write access to the
> tex installation directories one cannot typeset the module source?
> If so, I urge Hans Hagen to change this and let texexec and friends write
> into tmp directories or in the users current directory.
Sometimes I want to run texexec on a file in the different directory. In
that case, I find it useful that texexec is run on the directory in which
the file lies (otherwise things like \input and \component will not work
properly)
> But I might be wrong and having something other amiss.
You can just copy the file to a local directory and create the
documentation.
Aditya
___________________________________________________________________________________
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-03-25 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 14:01 Hans van der Meer
2008-03-24 14:42 ` Aditya Mahajan
2008-03-24 15:04 ` luigi scarso
2008-03-24 19:16 ` Hans van der Meer
2008-03-25 0:29 ` Aditya Mahajan [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-24 1:34 Typesetting documentation David Arnold
1999-11-24 8:09 ` 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=alpine.DEB.1.00.0803242019100.11443@nqv-yncgbc \
--to=adityam@umich.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).