zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: success (mostly) pws 17 under NeXTStep 3.3
Date: Tue, 11 May 1999 10:06:23 +0200	[thread overview]
Message-ID: <9905110806.AA14078@ibmth.df.unipi.it> (raw)
In-Reply-To: "Timothy J Luoma"'s message of "Mon, 10 May 1999 22:40:11 DFT." <199905110240.WAA18115@ocalhost>

Timothy J Luoma wrote:
> Using regular NeXT 3.3 'cc' and 'make'
> 
> 	configure ok
> 	
> 	make dies with '.pro' errors

That's a strange make, since it hasn't built the .pro files at all, which
are in the dependencies for zsh.mdh.

> (it failed at the end, after making 'zsh' -- I think because I don't have  
> the 'yodl' program -- shouldn't it recognize that and not try and build the  
> documentation?)

In the released version, the documentation is up to date, so that yodl is
only necessary if you alter the files.  You can avoid this here by getting
hold of the .doc.tar file from the same place and untarring it on top of
the source code.

> Users/                  private/
> 
> # /bin/ls -F /U[tab]
> # /bin/ls -F /U[cursor still here]
> 
> (ALL of the other files in / complete successfully)

The code in question is in get_matches_files() in Src/Zle/zle_tricky.c.
The main possibilities are that either zreaddir() and hence readdir() are
missing out Users, in which case ls probably wouldn't show it up, or that
the stat() call later on fails and the directory is skipped.  You can test
the effect of stat() if you have compiled zsh with dynamically loaded
libraries, by using `zmodload stat; stat -rs /Users', or see the main
README file about how to get the file stat.so compiled into the base
executable.  Maybe ls -ld /Users would give a clue, since that's basically
a stat() as well.

Another possibility is that the macro access(..., F_OK) is failing.  The
following shell code should do exactly the same check:

[[ -e /Users ]] && print file exists || print file doesn\'t exist

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


      reply	other threads:[~1999-05-11  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-23 10:59 yet another undesired 3.1.5-pws-15 change Sven Wischnowsky
1999-04-24  3:11 ` Timothy J Luoma
1999-04-25 13:44   ` Peter Stephenson
1999-04-25 14:35     ` Geoff Wing
1999-04-25 15:22       ` PATCH: 3.1.5-pws-15: multiline prompt Geoff Wing
     [not found]   ` <990423234917.ZM30140@candle.brasslantern.com>
     [not found]     ` <199904241324.JAA23300@ocalhost>
     [not found]       ` <990424092703.ZM32177@candle.brasslantern.com>
     [not found]         ` <199904302157.RAA26524@ocalhost>
     [not found]           ` <990504100735.ZM28408@candle.brasslantern.com>
1999-05-11  2:40             ` success (mostly) pws 17 under NeXTStep 3.3 Timothy J Luoma
1999-05-11  8:06               ` Peter Stephenson [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=9905110806.AA14078@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --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).