zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: PATCH: Re: Compilation on IRIX 5.3
Date: Thu, 08 Jun 2000 15:31:01 +0100	[thread overview]
Message-ID: <393FAE25.4759316A@u.genie.co.uk> (raw)
In-Reply-To: <000605163843.ZM25737@candle.brasslantern.com>

Bart Schaefer wrote:
> >
> > Can't open -e
> > Can't open /^!MOD!)$/q;p
> My only guess is that IRIX sed does not understand '-ne' and requires that
> there be two options '-n -e' instead.  Could you try that?

That was the problem. The IRIX sed does actually allow '-ne' as long as
there isn't another -e later on the line. The patch fixes our Makefile.

With the other problem with sys/types.h, I've been wasting your time
again so sorry about that. After removing certain entries from my
autoconf cache which were wrong, they were correctly determined when
rerunning configure so another program or older version of Zsh must have
got it wrong. I'll have to remember to try a clear cache before
reporting these build problems.

An unrelated point which I though I should mention is that if you run
the tests as root (which I did accidentally because I'd been root for
make install), you will get a failure for -r in the 07cond tests because
a file can be read as root even if the permissions are 000. I can't
think what the best way to deal with this is, maybe a check at the start
of the tests which displays a warning message.

I've also included a small change to _urls to use Sven's new -K option
to zparseopts. Is there a good reason why the -f options to _urls
completes files _first_ as opposed to together with URLs? I'd prefer to
be reminded by completion that urls would be valid in the current
context and anyone who likes the URLs first can always use a tag-order
style.

Oliver

Index: Completion/User/_urls
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/User/_urls,v
retrieving revision 1.12
diff -u -r1.12 _urls
--- Completion/User/_urls       2000/06/06 19:43:30     1.12
+++ Completion/User/_urls       2000/06/08 13:52:39
@@ -52,8 +52,8 @@
   _wanted -C -f files expl file _files "$@" && return 0
 fi

-zparseopts -D -E g:=glob
-: ${(A)=glob:=-g '*(^/)'}
+glob=(-g '*(^/)')
+zparseopts -D -K -E g:=glob

 ipre="$IPREFIX"

Index: Doc/Makefile.in
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Makefile.in,v
retrieving revision 1.3
diff -u -r1.3 Makefile.in
--- Doc/Makefile.in     2000/06/02 17:22:50     1.3
+++ Doc/Makefile.in     2000/06/08 13:52:39
@@ -193,7 +193,7 @@
        ( \
            echo "startitem()"; \
            for modfile in $(MODDOCSRC); do \
-               sed -ne '1{s|^COMMENT(!MOD!\(.*\)$$|item(tt(\1))(|;p;d;}' \
+               sed -n -e '1{s|^COMMENT(!MOD!\(.*\)$$|item(tt(\1))(|;p;d;}' \
                    -e '/^!MOD!)$$/q;p' \
                    < $(sdir)/$$modfile; \
                echo ")"; \


      reply	other threads:[~2000-06-08 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-05 20:58 Oliver Kiddle
2000-06-05 23:38 ` Bart Schaefer
2000-06-08 14:31   ` Oliver Kiddle [this message]

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=393FAE25.4759316A@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --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).