Bash-3.1 released

2005-12-09 Thread Chet Ramey
Introduction


The first public release of bash-3.1 is now available with the URLs

ftp://ftp.cwru.edu/pub/bash/bash-3.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash/bash-3.1.tar.gz

and from the usual GNU mirror sites.

This tar file does not include the formatted documentation
(postscript, dvi, html, and nroffed versions of the manual pages);
that may be retrieved with the URLs

ftp://ftp.cwru.edu/pub/bash/bash-doc-3.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/bash/bash-doc-3.1.tar.gz

When unpacking the documentation, make sure to extract the tar file
in the bash-3.1 source directory.

Diffs from bash-3.0 are not available.

Please use `bashbug' to report bugs with this version.  It is built
and installed at the same time as bash.

Installation


Please read the README file first.

Installation instructions are provided in the INSTALL file.

New Features


This is the first maintenance release for the third major release of bash.

As with all odd-numbered minor releases, the focus is on bug fixes;
there are several dozen important fixes included.  A few new features
have been added:  the `+=' assignment operator, the `-v var' option to
printf, and the `nocasematch' shell option are the most notable.

Read the file NEWS in the bash-3.1 distribution for a complete description
of the new features.  Here is a short list:

o  This version of bash can be configured to provide strict POSIX conformance
   by default using a new option to `configure'.

o  The `+=' assignment operator (append to the value of a string or array) is
   now supported for assignment statements and arguments to builtin commands
   that accept assignment statements.

o  The `printf' builtin takes a new option: -v var.  That causes the output
   to be placed into var instead of on stdout.

o  New shell option: nocasematch.  If non-zero, shell pattern matching ignores
   case when used by `case' and `[[' commands.

Changes have been made to the Readline library being released at
the same time as bash-3.1, readline-5.1, so that Bash can be
linked against an already-installed Readline library rather than
the private version in lib/readline.  Only readline-5.1 and later
versions are able to provide all of the symbols that bash-3.1
requires; earlier versions of the Readline library will not work
correctly.

A complete list of changes between bash-3.0 and bash-3.1 is
available in the file CHANGES; the relevant portions are appended.

Readline


Also available is a new release of the standalone Readline library,
version 5.1, with its own configuration scripts and Makefiles. 
It can be retrieved with the URLs

ftp://ftp.cwru.edu/pub/bash/readline-5.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/readline/readline-5.1.tar.gz

and from the usual GNU mirror sites.

Diffs from readline-5.0 are not available.

The formatted Readline documentation is included in the readline
distribution tar file.

A separate announcement listing the changes in Readline is being
distributed.

As always, thanks for your help.

Chet

+== CHANGES ==+
This document details the changes between this version, bash-3.1-release,
and the previous version, bash-3.1-rc2.

1.  Changes to Readline

a.  Several changes to the multibyte redisplay code to fix problems with
prompts containing invisible characters.

--
This document details the changes between this version, bash-3.1-rc2,
and the previous version, bash-3.1-rc1.

1.  Changes to Bash

a.  Fixed a bug that caused a DEBUG trap to overwrite a command string that's
eventually attached to a background job.

b.  Changed some code so that filenames with leading tildes with spaces in the
name aren't tilde-expanded by the bash completion code.

c.  Fixed a bug that caused the pushd builtin to fail to change to
directories with leading `-'.

d.  Fixed a small memory leak in the programmable completion code.

2.  Changes to Readline

a.  Fixed a redisplay bug caused by moving the cursor vertically to a line
with invisible characters in the prompt in a multibyte locale.

b.  Fixed a bug that could cause the terminal special chars to be bound in the
wrong keymap in vi mode.

3.  New Features in Bash

a.  If compiled for strict POSIX conformance, LINES and COLUMNS may now
override the true terminal size.

4.  New Features in Readline

a.  A new external application-controllable variable that allows the LINES
and COLUMNS environment variables to set the window size regardless of
what the kernel returns.

--
This document details the changes between this version, bash-3.1-rc1,
and the previous version, bash-3.1-beta1.

1.  Changes to Bash

a.  Fixed a bug that could cause core dumps due of accessing the current
pipeline while in the middle of modifying it.

b.  Fixed a bug that caused pathnames with backslashes still qu

Readline-5.1 released

2005-12-09 Thread Chet Ramey
The first public release of the GNU Readline library, version
5.1, is now available for FTP with the URLs

ftp://ftp.cwru.edu/pub/bash/readline-5.1.tar.gz
ftp://ftp.gnu.org/pub/gnu/readline/readline-5.1.tar.gz

and from the usual GNU mirror sites.

This distribution is essentially a standalone version of the
readline library that appears in Bash-3.1 together with an
`autoconf' framework.  The documentation has been updated and
is current.  Postscript, DVI, and Info versions of the Readline
and History manuals are included.  A list of changes in this
release is appended to this announcement.

GNU Readline is a library which provides programs with an input
facility including command-line editing and history.  Editing
commands similar to both emacs and vi are included.  The GNU
History library, which provides facilities for managing a list of
previously-typed command lines and an interactive command line
recall facility similar to that provided by csh, is also present.
The history library is built as part of the readline library as well
as separately.

Diffs from readline-5.0 are not available.

Please send readline bug reports to [EMAIL PROTECTED]

+== CHANGES ==+
This document details the changes between this version, readline-5.1,
and the previous version, readline-5.0.

1.  Changes to Readline

a.  Fixed a bug that caused multiliine prompts to be wrapped and displayed
incorrectly.

b.  Fixed a bug that caused ^P/^N in emacs mode to fail to display the current
line correctly.

c.  Fixed a problem in computing the number of invisible characters on the first
line of a prompt whose length exceeds the screen width.

d.  Fixed vi-mode searching so that failure preserves the current line rather
than the last line in the history list.

e.  Fixed the vi-mode `~' command (change-case) to have the correct behavior at
end-of-line when manipulating multibyte characters.

f.  Fixed the vi-mode `r' command (change-char) to have the correct behavior at
end-of-line when manipulating multibyte characters.

g.  Fixed multiple bugs in the redisplay of multibyte characters:  displaying
prompts longer than the screen width containing multibyte characters,

h.  Fix the calculation of the number of physical characters in the prompt
string when it contains multibyte characters.

i.  A non-zero value for the `rl_complete_suppress_append' variable now causes
no `/' to be appended to a directory name.

j.  Fixed forward-word and backward-word to work when words contained
multibyte characters.

k.  Fixed a bug in finding the delimiter of a `?' substring when performing
history expansion in a locale that supports multibyte characters.

l.  Fixed a memory leak caused by not freeing the timestamp in a history entry.

m.  Fixed a bug that caused "\M-x" style key bindings to not obey the setting
of the `convert-meta' variable.

n.  Fixed saving and restoring primary prompt when prompting for incremental   
and non-incremental searches; search prompts now display multibyte
characters correctly.

o.  Fixed a bug that caused keys originally bound to self-insert but shadowed
by a multi-character key sequence to not be inserted.

p.  Fixed code so rl_prep_term_function and rl_deprep_term_function aren't
dereferenced if NULL (matching the documentation).

q.  Extensive changes to readline to add enough state so that commands
requiring additional characters (searches, multi-key sequences, numeric
arguments, commands requiring an additional specifier character like
vi-mode change-char, etc.) work without synchronously waiting for
additional input.

r.  Lots of changes so readline builds and runs on MinGW.

s.  Readline no longer tries to modify the terminal settings when running in
callback mode.

t.  The Readline display code no longer sets the location of the last invisible
character in the prompt if the \[\] sequence is empty.

u.  The `change-case' command now correctly changes the case of multibyte
characters.

v.  Changes to the shared library construction scripts to deal with Windows
DLL naming conventions for Cygwin.

w.  Fixed the redisplay code to avoid core dumps resulting from a poorly-timed
SIGWINCH.

x.  Fixed the non-incremental search code in vi mode to dispose of any current
undo list when copying a line from the history into the current editing
buffer.

y.  Fixed a bug that caused reversing the incremental search direction to
not work correctly.  

z.  Fixed the vi-mode `U' command to only undo up to the first time insert mode
was entered, as Posix specifies.

aa. Fixed a bug in the vi-mode `r' command that left the cursor in the wrong
place.

bb. Fixed a redisplay bug caused by moving the cursor vertically to a line
with invisible characters in the prompt in a multibyte locale.

cc. Fixed a bug that could cause the terminal special chars to be bound in the
wrong keymap in vi mode.


Re: Readline-5.1 released

2005-12-09 Thread Michael Hudson
Chet Ramey <[EMAIL PROTECTED]> writes:

> q.  Extensive changes to readline to add enough state so that commands
> requiring additional characters (searches, multi-key sequences, numeric
> arguments, commands requiring an additional specifier character like
> vi-mode change-char, etc.) work without synchronously waiting for
> additional input.

If this is in response to my bug report (and, I guess, even if it's
not :) thanks a lot!  It fixes both my test case and my actual use
case.

Cheers,
mwh

-- 
  Ya, ya, ya, except ... if I were built out of KSR chips, I'd
  be running at 25 or 50 MHz, and would be wrong about ALMOST
  EVERYTHING almost ALL THE TIME just due to being a computer!
  -- Tim Peters, 30 Apr 97



___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash