pws-21

pws-21

[Peter Stephenson]

http://www.ifh.de/~pws/computing/
-rw-r--r--   1 pws  quadrics  251548 Jun  8 10:14 zsh-3.1.5-pws-21.doc.tar.bz2
-rw-r--r--   1 pws  quadrics  370239 Jun  8 10:14 zsh-3.1.5-pws-21.doc.tar.gz
-rw-r--r--   1 pws  quadrics  768134 Jun  8 10:14 zsh-3.1.5-pws-21.tar.bz2
-rw-r--r--   1 pws  quadrics  949770 Jun  8 10:14 zsh-3.1.5-pws-21.tar.gz

You will notice that the patchlist.txt has been absorbed into ChangeLog to
try and make an honest shell out of it.

The unposted --enable-fndir/install.fns change has the modifications
described in 6503 (FUNCTIONS_INSTALL).  However, it does not yet have
checks for overwriting existing functions on installation.  Maybe someone
will beat me to it (hope springs eternal).

I have not incorporated Tanaka Akira's latest patch on COLUMNS/LINES, I'll
wait to see what the reaction to Bart's comments is.  I'm unlikely to
meddle in this one myself.

There are various other bits of pending business I need to reply to,
at some point, but nothing urgent in the patch way.

Note that the list of changes is now in Stallmanesque backwards format.

1999-06-08  Peter Stephenson  <pws@ibmth.difi.unipi.it>

	* 3.1.5-pws-21 made available

	* Sven: 6515: Src/Zle/zle_tricky.c: fix memory problems with 6492

	* Wayne: 6510: Completion/Core/compinit: another nounset problem

1999-06-07  Peter Stephenson  <pws@ibmth.difi.unipi.it>

	* pws: configure.in, Config/defs.mk.in, Functions/Makefile.in,
	  Completion/Makefile.in, rearrangement of Functions
	  subdirectories:  --enable-fndir allows function installation,
	  defaults to ${datadir}/zsh/functions; is compiled into $fpath;
	  FUNCTIONS_INSTALL can specify functions to install e.g.
	  'Core/* Base/* Builtins/* Zftp/*'.

	* pws: 6509: Src/Zle/zle_tricky.c: comp_setunset -> comp_setunsetptr

	* pws: 6506: Completion/Core/compinit, Doc/Zsh/compsys.yo: if
	  completion dumpfile is not writeable, use
	  ${ZDOTDIR:-$HOME}/.zcompdump

	* Sven: 6502: Doc/Zsh/options.yo: document 6496

	* Sven: 6496: Src/Zle/zle_misc.c (makesuffix): more characters
	  that can't be part of a filename

	* Sven: 6493: Completion/Core/_approximate,
	  Completion/Core/_expand: %e wasn't being replaced properly in
	  correction prompts

	* Sven: 6492: Src/Zle/comp.h, Src/Zle/comp1.c, Src/Zle/compctl.c,
	  Src/Zle/zle_main.c, Src/Zle/zle_tricky.c, Doc/Zsh/compctl.yo,
	  Doc/Zsh/compsys.yo, Doc/Zsh/compwid.yo,
	  Completion/Base/_brace_parameter:  Completion inside quotes
	  now acts as if the file name is the entire quoted string;
	  `compctl -h' takes a command line from inside a quoted string;
	  the compctl tests q[s], q[d], q[b] are true if we are in single,
	  double, back quotes; compset -q tests quotes and splits the word,
	  affecting $PREFIX, $SUFFIX and setting $IQPREFIX, $IQSUFFIX for
	  the bits which will now be ignored.

	* pws: 6490: Completion/Core/compinit: nounset workaround

	* Bart: 6485: Src/loop.c: only show one screenful at a time
	  in select, as LINES doc implies it should do

	* Sven: 6484: Src/Zle/zle_main.c, Src/Zle/zle_tricky.c: close
	  fd 0 during zle widgets and completion and redup back afterwards
	  (removed unnecessary zclose()'s)
	
	* Wayne: 6481: Doc/Zsh/builtins.yo, Doc/Zsh/options.yo,
	  Src/hist.c:  improved new history documentation and comments

	* Wayne: 6480: Src/hist.c: Ignore some lines in remhist() to
	  workaround crashes attempting to add already removed lines

	* Tanaka Akira: 6478: Completion/User/_make: complete files
	  as fallback (but use _files instead of compgen -f)

1999-06-06  Peter Stephenson  <pws@ibmth.difi.unipi.it>

	* Naoki Wakamatsu <naoki-w@ht-net21.ne.jp>: 6477: configure.in:
	  undefine etcdir, not zshenv

1999-06-05  Peter Stephenson  <pws@ibmth.difi.unipi.it>

	* Merge ChangeLog entry from patchlist.txt in 3.1.5-pws-20
	  These are briefer than normal ChangeLog entries, but upgrading
	  all of them is too much work.

	* pws: 6473: Src/Modules/mapfile.c: munmap() after writing file

	* Bart: 6472: doc for 6458

	* pws: 6470: options.yo doc for globalrcs

	* Sven: 6468: -first- context example; allow $compcontext for
	  direct context in _complete; other stuff

	* pws: 6464: fix problem with 6433; disallow nested parameter
	  substitution without braces

	* Sven: 6458: allow seconds in globbing qualifier time comparisons

	* Zefram: off-list: metafaq updates

	* pws: 6437: rearrange quotes in expn.yo, zftpsys.yo, minor
	  corrections

	* pws: 6433: allow quotes around names of parameters in braces

	* pws: 6431: su saga again: new documentation

	* Bart: 4127: su saga: 6299 and 6313 backed off; this alters
	  ZSH_NAME using zgetenv("SHELL").  It can be turned into an
	  --enable if anyone complains.

	* Wayne: 6430: history tweaks: more careful ignoring history with
	  foreign lines, changed name incappendhistory

	* pws: 6424: reduce excess quoting in info files

	* pws: 6421: _mh should use $words instead of $argv

	* pws: 6416: document ${(f)"$(foo)"} change and nesting of quotes
	  in braces

	* Sven: 6414: completing parameters with extra quotes, don't
	  complete local parameters

	* Sven: 6411: fix display bug on terminals which can do
	  TCMULTRIGHT (gap left when clearing list).

	* pws: 6410: RCS option can now take affect at any point during
	  initialisation, new GLOBAL_RCS applies to /etc/z* files.

	* Bart: 6404: singleton arrays treated as scalars locally (as
	  before), but correct array/scalar status is passed to enclosing
	  substitutions.

	* Bart: 6395: uninstall info files over 9, too

	* Sven: 6212 (previously missed): an extra clear list

	* Andrej: 6392: install info files higher than 9

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

Re: LFS and explicit LIBS RE: pws-21

[Peter Stephenson]

"Andrej Borsenkow" wrote:
> Now, that I finally got a debugger for  my system (DBX), I decided to
> compile Zsh with debugging. To fully utilize DBX it is very advisable to
> link -lg into executable. Unfortunately, doing so disables LFS :-(

It's just an automated test for the unsophisticated.  Once you know what
the flags are, you can get exactly the same effect by adding them directly
to CFLAGS, just so long as you specify --enable-lfs so that all the tests
for sizes of integers are turned on.  I do this all the time (the default
--zsh-debug flags don't include -O which I always add).

> May be, for items, that are empty (LFS_CFLAGS, LFS_LDFLAGS etc) we
> should not disable LFS?

Yes, that's a possibility.

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

LFS and explicit LIBS RE: pws-21

[Andrej Borsenkow]

Now, that I finally got a debugger for  my system (DBX), I decided to
compile Zsh with debugging. To fully utilize DBX it is very advisable to
link -lg into executable. Unfortunately, doing so disables LFS :-(

It may be my private problem ... but I would *really* appreciate the way to
force LFS even if some of CFLAGS/CPPFLAGS/LIBS are set.

The joke is, I do not need LIBS to compile LFS program (getconf LFS_LIBS is
empty). May be, for items, that are empty (LFS_CFLAGS, LFS_LDFLAGS etc) we
should not disable LFS?

/andrej

RE: LFS and explicit LIBS RE: pws-21

[Andrej Borsenkow]

make[1]: Leaving directory `/tools/src/zsh-3.1.5-pws-21/Doc'
gmake[1]: Entering directory `/tools/src/zsh-3.1.5-pws-21/Completion'
if test xyes != x && test xyes != xno; then \
  ../mkinstalldirs yes || exit 1; \

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  for file in Core/* Base/* Builtins/* User/_configure User/_dd User/_gzip
User/_compress User/_uncompress Zftp/*; do \
    if test -f $file; then \
      .././install-sh -c -m 644 $file yes || exit 1; \
    fi; \
  done; \
fi; \
exit 0
mkdir yes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This is configure problem; I configure with --enable-fndir and fndir got set
to "yes".

/andrej

Re: LFS and explicit LIBS RE: pws-21

[Peter Stephenson]

"Andrej Borsenkow" wrote:
> This is configure problem; I configure with --enable-fndir and fndir got set
> to "yes".

I wasn't expecting people to use it without giving a value, but the
rules certainly allow that.

--- configure.in.fn	Mon Jun  7 12:12:59 1999
+++ configure.in	Tue Jun  8 13:21:10 1999
@@ -204,7 +204,11 @@
 undefine([fndir])dnl
 AC_ARG_ENABLE(fndir,
 [  --enable-fndir=DIR        where functions go (default DATADIR/zsh-fns)],
-[fndir="$enableval"], [fndir=${datadir}/zsh/functions])
+[if $enableval = yes; then
+  fndir=${datadir}/zsh/functions
+else
+  fndir="$enableval"
+fi], [fndir=${datadir}/zsh/functions])
 
 if test x${FUNCTIONS_INSTALL+set} != xset; then
   FUNCTIONS_INSTALL="Core/* Base/* Builtins/* User/* Commands/*"

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

Re: LFS and explicit LIBS RE: pws-21

[Peter Stephenson]

"Andrej Borsenkow" wrote:
> Is function install enabled by default? (if no --enable-fndir is specified)

This is what I put in INSTALL, I think it's clear on the subject.

  By default, the shell functions which are installed with `make install' or
  `make install.fns' go into the directory ${datadir}/zsh/functions, which
  unless you have specified --datadir is the same as
  ${prefix}/share/zsh/functions ($prefix itself defaults to /usr/local, as
  described below).  This directory will also be compiled into the shell as
  the default directory for the variable $fpath/$FPATH. You can override it
  with --enable-fndir=directory; --disable-fndir or --enable-fndir=no will
  turn off both installation of functions and the setting of a default value
  for $fpath/$FPATH.

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

RE: LFS and explicit LIBS RE: pws-21

[Andrej Borsenkow]

>
> I wasn't expecting people to use it without giving a value, but the
> rules certainly allow that.
>

Then, may be, I misunderstood it. I was sure, that to enable functions
installation I must use --enable-fndir; and in this case "defaults to ..."
definitely means, that I can omit argument.

Is function install enabled by default? (if no --enable-fndir is specified)

/andrej

Re: LFS and explicit LIBS RE: pws-21

[Tanaka Akira]

In article <9906081132.AA20839@ibmth.df.unipi.it>,
  Peter Stephenson <pws@ibmth.df.unipi.it> writes:

>  [  --enable-fndir=DIR        where functions go (default DATADIR/zsh-fns)],

Hmm. DATADIR/zsh-fns?

--- configure.in-	Tue Jun  8 21:06:09 1999
+++ configure.in	Tue Jun  8 21:06:26 1999
@@ -203,7 +203,7 @@
 
 undefine([fndir])dnl
 AC_ARG_ENABLE(fndir,
-[  --enable-fndir=DIR        where functions go (default DATADIR/zsh-fns)],
+[  --enable-fndir=DIR        where functions go (default DATADIR/zsh/functions)],
 [if $enableval = yes; then
   fndir=${datadir}/zsh/functions
 else

-- 
Tanaka Akira

PATCH: RE: LFS and explicit LIBS RE: pws-21

[Andrej Borsenkow]

>
> I wasn't expecting people to use it without giving a value, but the
> rules certainly allow that.
>

Typo correction:

--- configure.in.org    Wed Jun  9 12:16:40 1999
+++ configure.in        Wed Jun  9 12:20:41 1999
@@ -204,7 +204,7 @@
 undefine([fndir])dnl
 AC_ARG_ENABLE(fndir,
 [  --enable-fndir=DIR        where functions go (default DATADIR/zsh-fns)],
-[if $enableval = yes; then
+[if test $enableval = yes; then
   fndir=${datadir}/zsh/functions
 else
   fndir="$enableval"

PATCH: RE: LFS and explicit LIBS RE: pws-21

[Andrej Borsenkow]

> 
> > May be, for items, that are empty (LFS_CFLAGS, LFS_LDFLAGS etc) we
> > should not disable LFS?
> 
> Yes, that's a possibility.
> 
> -- 

The patch below tries this. 

/andrej


--- aczsh.m4.org        Wed Jun  9 18:45:55 1999
+++ aczsh.m4    Wed Jun  9 19:00:20 1999
@@ -41,11 +41,13 @@
   CPPFLAGS) ac_lfsvar=LFS_CFLAGS ;;
   *) ac_lfsvar=LFS_$ac_shellvar ;;
   esac
-  eval test '"${'$ac_shellvar'+set}"' = set && ac_set=$ac_shellvar
   (getconf $ac_lfsvar) >/dev/null 2>&1 || { ac_result=no; break; }
   ac_getconf=`getconf $ac_lfsvar`
-  ac_getconfs=$ac_getconfs$ac_getconf
-  eval ac_test_$ac_shellvar="\$ac_getconf"
+  if test -n "$ac_getconf"; then
+    eval test '"${'$ac_shellvar'+set}"' = set && ac_set=$ac_shellvar
+    ac_getconfs=$ac_getconfs$ac_getconf
+    eval ac_test_$ac_shellvar="\$ac_getconf"
+  fi
 done
 case "$ac_result$ac_getconfs" in
 yes) ac_result=no ;;