zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: /usr/local/bin/perl
Date: Wed, 15 Aug 2001 15:54:20 +0100	[thread overview]
Message-ID: <20010815155420.A14031@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <20010327151711.94655.qmail@web9306.mail.yahoo.com>; from okiddle@yahoo.co.uk on Tue, Mar 27, 2001 at 04:17:11PM +0100

Dragging up an old topic ...

Oliver Kiddle (okiddle@yahoo.co.uk) wrote:
> --- Adam Spiers <adam@spiers.net> wrote:
> > The following scripts hardcode binary locations (excluding /bin/sh
> 
> > Can we avoid this?  Is env(1) common to enough platforms, for
> > instance, or maybe we could add something to configure?
> 
> I'd agree that this is something which would be nice to clean up. I'd
> have thought that it would be fine to use env for these.

I'm not so sure env is any use now, as it appears to break if you
specify any switch, e.g.

  #!/usr/bin/env perl -w

breaks with

  env: perl -w: No such file or directory

Pretty remarkably braindead IMHO, but there we go.

> Setting the #! lines would be quite simple from configure but I'm not
> sure it is worth it for the extra complexity and potential for things
> to break.

Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> The only reason that I've added #! lines anywhere is so that emacs will
> start up in shell script mode and select the correct syntax.
> 
> }    Util/helpfiles           :   #!/usr/bin/perl -- -*-perl-*-
> 
> The -*- perl -*- is extraneous there, at least in newer versions of emacs.
> It'll figure it out from the tail of the #! path.

Yep.

> }    Test/ztst.zsh            :   #!/usr/local/bin/zsh -f
> 
> That should be ".../zsh -f +Z".

Indeed, and I believe that I've had tests misleadingly fail through
running `make test' before `make install' as a result of that.  Shall
I change it then?

> If you put env in the #! line -- or put the #! line anywhere but as the
> first line in the script -- it foils emacs' algorithm for figuring out
> which mode to start in.  Same issue if you put some kind of @...@ thing
> for configure there.  Not that this should be the primary reason for any
> decision that we make, but at least consider it.

We can persuade emacs to use the right mode using the other method:

  # Local Variables:
  # mode:cperl
  # End:

should do it.

If we use configure, presumably that would mean having (say)
Utils/helpfiles auto-generated from Utils/helpfiles.in?  My vote is
for that option.


  reply	other threads:[~2001-08-15 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 13:28 /usr/local/bin/perl Adam Spiers
2001-03-27 15:17 ` /usr/local/bin/perl Oliver Kiddle
2001-08-15 14:54   ` Adam Spiers [this message]
2001-08-15 16:59     ` /usr/local/bin/perl Bart Schaefer
2001-08-16 14:12       ` /usr/local/bin/perl Adam Spiers
2001-08-16 20:52         ` /usr/local/bin/perl Bart Schaefer
2001-03-27 18:19 ` /usr/local/bin/perl Bart Schaefer

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=20010815155420.A14031@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).