zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.dk
Subject: Re: /usr/local/bin/perl
Date: Thu, 16 Aug 2001 15:12:35 +0100	[thread overview]
Message-ID: <20010816151235.B20958@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1010815165958.ZM10425@candle.brasslantern.com>; from schaefer@brasslantern.com on Wed, Aug 15, 2001 at 04:59:58PM +0000

Bart Schaefer (schaefer@brasslantern.com) wrote:
> On Aug 15,  3:54pm, Adam Spiers wrote:
> }
> } > }    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.
> 
> You shouldn't have.  `make test' explicitly calls zsh by full path and
> passes it ztst.zsh by name.

Ahah.  Ignore that then; the failures have been fixed now anyway.

> } Shall I change it then?
> 
> I'm not sure it'll help,

Agreed, now that I know how make test works.

> as many OSs won't accept more than one argument after the command
> path when interpreting a #! line. (That's likely why you are having
> trouble with `env perl -w'.)

Gosh, looks like that applies even to a standard Linux box.  How
extraordinary.  What's the reasoning behind that, I wonder?

> } We can persuade emacs to use the right mode using the other method:
> } 
> }   # Local Variables:
> }   # mode:cperl
> }   # End:
> } 
> } should do it.
> 
> Please don't.  I find it aesthetically displeasing to have that cruft
> at the end of every file, and I hate having emacs stop during file load
> to ask whether it should pay attention to it, and it's not secure to
> simply always accept it.  I'd rather just type M-x cperl-mode if emacs
> has got it wrong.

Agreed, it is pretty nasty.  There are other elisp hacks you can solve
the problem with anyway.

> } If we use configure, presumably that would mean having (say)
> } Utils/helpfiles auto-generated from Utils/helpfiles.in?  My vote is
> } for that option.
> 
> Yes, that would be it, but my vote is still to avoid mucking with this
> in configure.  Maybe something like the following, run through the
> just-compiled zsh?

I suppose that's fine, as long as it wouldn't mess things up if you
ran it twice.  I still slightly prefer going via configure, as that
way you're not altering CVS files.  You probably have a more
convincing argument the other way though :-)


  reply	other threads:[~2001-08-16 14:12 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   ` /usr/local/bin/perl Adam Spiers
2001-08-15 16:59     ` /usr/local/bin/perl Bart Schaefer
2001-08-16 14:12       ` Adam Spiers [this message]
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=20010816151235.B20958@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-workers@sunsite.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).