From: Hans van der Meer <hansm@science.uva.nl>
Subject: Re: texmfstart texutil
Date: Fri, 9 Jun 2006 20:20:37 +0200 [thread overview]
Message-ID: <510BCEE6-061E-44F5-AEF1-FA13517E8688@science.uva.nl> (raw)
In-Reply-To: <44899201.2080804@wxs.nl>
On Jun 9, 2006, at 17:21, Hans Hagen wrote:
> Hans van der Meer wrote:
>> On Jun 9, 2006, at 12:49, Hans Hagen wrote:
>>
>>
>>> Hans van der Meer wrote:
>>>
>>>> In order to purge the temporary context files I did (throught an
>>>> alias)
>>>> texutil --purge
>>>> This worked fine.
>>>>
>>>>
>>
>>
>>> texutil will go away (i.e. be a wrapper only); the functionality
>>> has been moved to texexec.rb, ctxtools.rb, pdftools.rb, rlxtools.rb
>>> etc
>>>
>>> it's now:
>>>
>>> ctxtools --purge
>>>
>>
>> For those on UNIX(-like) systems that have only texmfstart.rb enabled
>> as executable (chmod a+x texmfstart.rb) this will not work as none
>> the ruby scripts in the distribution seem to have their execution
>> bits set.
>> The next seems mandatory if only texmfstart is enabled: texmfstart
>> ctxtools --purge
> on unix, one needs to copy texmfstart.rb to texmfstart and copy it to
> some bin path
>
Copying is imho not necessary. As long as the execution bits are set
any file can be made to execute by a shell. What to do is determined
by the shebang line.
I am working in MacOSX which is UNIX under the hood and
"texmfstart.rb" is excuted without the need for copying.
Hans van der Meer
next prev parent reply other threads:[~2006-06-09 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 9:30 Hans van der Meer
2006-06-09 10:49 ` Hans Hagen
2006-06-09 12:32 ` Hans van der Meer
2006-06-09 12:51 ` Taco Hoekwater
2006-06-09 15:21 ` Hans Hagen
2006-06-09 18:20 ` Hans van der Meer [this message]
2006-06-09 9:43 Richard Gabriel
2006-06-09 10:50 ` Hans Hagen
2006-06-09 12:25 ` Hans van der Meer
2006-06-09 11:38 Richard Gabriel
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=510BCEE6-061E-44F5-AEF1-FA13517E8688@science.uva.nl \
--to=hansm@science.uva.nl \
--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).