Package: bash
Version: 3.1-5
Severity: minor

{ Preliminary note: This potential bug can be fixed by a single character }

In bash 3.00.16(1) (Sarge package bash3-3.0-12), the string defined in
HISTTIMEFORMAT was interpreted as if there was a space character behind:

$ echo "\"$HISTTIMEFORMAT\""
"%Y-%m-%d %H:%M:%S %z"   # as you can see, there's no space at the end
$ history | grep some_command
 9567  2006-08-14 17:49:09 +0200 some_command
$

In Etch's bash 3.1.17(1) (package bash-3.1-5), this space was silently
omitted:

$ history | grep some_command
 9567  2006-08-14 17:49:09 +0200some_command
$

I'm okay with either way:

* The old behavior was reasonable.
* The new behavior is more flexible (you could then "finish" the job and
  define a HISTFORMAT to control the whole history line's format, although
  at least I don't need that).

But I want to know if this is just a bug or a new feature I can rely on,
in which case it should be documented appropriately; at least a note in the
changelog would be a good idea, so that people won't report this as a bug.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_US, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages bash depends on:
ii  base-files                    3.1.14     Debian base system miscellaneous f
ii  debianutils                   2.17       Miscellaneous utilities specific t
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries
ii  libncurses5                   5.5-2      Shared libraries for terminal hand

bash recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to