zsh-workers
 help / color / mirror / code / Atom feed
From: P.Stephenson@swansea.ac.uk
To: kpc@ptolemy-ethernet.arc.nasa.gov
Cc: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: bug in zsh 2.6 beta 11: xkeysymdb
Date: Tue, 07 Nov 95 12:55:20 +0000	[thread overview]
Message-ID: <23829.9511071255@pygmy.swan.ac.uk> (raw)
In-Reply-To: "kpc@ptolemy.arc.nasa.gov"'s message of "Tue, 07 Nov 95 02:59:41 PST."             <9511071059.AA18493@phenotype.arc.nasa.gov>

kpc@ptolemy.arc.nasa.gov wrote:
> beta11 compiles cleanly but has the following bug and complains of a
> syntax error in my .zshrc that I cannot locate.  It says ".zshrc:
> parse error near `)' [307]".  I will spare you my .zshrc but hope that
> future versions can locate syntax errors better.  Note that 2.3.1 does
> not complain at all.  I have no idea where the error is or whether
> there is one.  All parentheses and braces and brackets match that I
> know of.

Maybe you're using the csh-like syntax 'if (...) { ... }', in which
case `setopt cshjunkiesyntax' at the top of .zshrc (or if you're
really set on the syntax, in ~/.zshenv).  This change was forced
because there is no way in general of telling whether the parentheses
represent a C-shell-like test or a Bourne-shell-like subshell and it
was felt the latter should take precedence in case of conflict.

> % . .zslow
> .zslow: no such file or directory: usr/local/X.V11R5/lib/XKeysymDB [291]
> ...

May be problems with the Berkeley compatibility library on Solaris
again, judging from the initial part of the file name missing ---
although it's not actually obvious why that would be relevant, it's
worth checking: it's clearly a system-specific problem.  Here's the
relevant bit from the FAQ.  (As far as I know, this is the only
compatibility problem for Solaris of any version of 2.6.)

  *Note for Solaris 2.2 and 2.3*: The UCB versions of the routines for
  reading directories are not usable (the struct definitions are2
  incompatible with the ones assumed by zsh).  The symptom of this is
  that globbed filenames in the compiled version of zsh will be
  missing the first two letters.  To avoid this, make sure you compile
  zsh without any reference to /usr/ucblib in (e.g.) your
  LD_LIBRARY_PATH.

-- 
Peter Stephenson <pws@ifh.de>       Tel: +49 33762 77366
WWW:  http://www.ifh.de/~pws/       Fax: +49 33762 77330
Deutches Electronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, 15735 Zeuthen, Germany.


  reply	other threads:[~1995-11-07 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-07 10:59 kpc
1995-11-07 12:55 ` P.Stephenson [this message]
1995-11-07 15:42 ` bug in zsh 2.6 beta 11 Peter William Stephenson
1995-11-07 17:54   ` Vinnie Shelton
1995-11-07 20:01   ` Richard Coleman
1995-11-09  2:42   ` kpc
1995-11-09  2:52     ` Richard Coleman
1995-11-09  3:20       ` kpc

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=23829.9511071255@pygmy.swan.ac.uk \
    --to=p.stephenson@swansea.ac.uk \
    --cc=kpc@ptolemy-ethernet.arc.nasa.gov \
    --cc=zsh-workers@math.gatech.edu \
    /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).