public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: #! magic for finding Cygwin Tcl shell
Date: Tue, 06 Jan 2009 19:13:00 -0000	[thread overview]
Message-ID: <4963AD4C.9000704@dallaway.org.uk> (raw)
In-Reply-To: <4963A830.6090600@eCosCentric.com>

Hi Jifl

Jonathan Larmour wrote:

>> Rather than increase the complexity of the #! magic still further, I
>> think it now makes sense to revert to a simple "#! /usr/bin/tclsh"
>> within our Tcl scripts. However, this would break compatibility with old
>> Cygwin installations providing only tclsh8*.exe or cygtclsh80.exe.
>>
>> Any objections?
> 
> Yes, it may not be in /usr/bin. I don't mind the cygwin-specific cygpath
> bits being dropped, but I'd still want it to be found from the PATH by some
> means.

Have you ever encountered a Linux system where tclsh is not accessible
at /usr/bin/tclsh? Or were you thinking of portability to other
operating systems?

I note your (old) post to the Cygwin list which implies that
/usr/bin/tclsh is usual for UNIX-like operating systems:

  http://cygwin.com/ml/cygwin/2003-02/msg00007.html

John Dallaway

  parent reply	other threads:[~2009-01-06 19:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 18:02 John Dallaway
2009-01-06 18:51 ` Jonathan Larmour
2009-01-06 19:10   ` Gary Thomas
2009-01-06 19:44     ` Jonathan Larmour
2009-01-07  9:44       ` John Dallaway
2009-01-07 13:39         ` Jonathan Larmour
2009-01-07 17:06           ` John Dallaway
2009-01-06 19:13   ` John Dallaway [this message]
2009-01-06 19:37     ` Jonathan Larmour
2009-01-06 20:04       ` Sergei Gavrikov
2009-01-06 20:01 ` Bart Veer
2009-01-07 11:10 ` Tarmo Kuuse
2009-01-07 11:53   ` Gary Thomas

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=4963AD4C.9000704@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=jifl@eCosCentric.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).