Your message dated Mon, 25 Apr 2005 21:37:16 -0400
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #306346,
regarding zsh: replacement seems broken in prompt
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---------------------------------------
Received: (at 306346-forwarded) by bugs.debian.org; 26 Apr 2005 01:37:17 +0000
>From [EMAIL PROTECTED] Mon Apr 25 18:37:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from acolyte.scowler.net [216.254.112.45] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DQF0n-0001jo-00; Mon, 25 Apr 2005 18:37:17 -0700
Received: by acolyte.scowler.net (Postfix, from userid 1000)
        id 851BB7004A; Mon, 25 Apr 2005 21:37:16 -0400 (EDT)
Date: Mon, 25 Apr 2005 21:37:16 -0400
From: Clint Adams <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Bug#306346: zsh: replacement seems broken in prompt]
Message-ID: <[EMAIL PROTECTED]>
Mail-Followup-To: [EMAIL PROTECTED],
        [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

This is with 21170.

----- Forwarded message from Michal Politowski <[EMAIL PROTECTED]> -----

Date: Tue, 26 Apr 2005 00:01:18 +0200
From: Michal Politowski <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Bug#306346: zsh: replacement seems broken in prompt

4.2.5-4 didn't show this behaviour, so maybe it's the newest patch.
${${foo}/?*/replacement} puts replacement in the prompt even when foo is empty
${foo/?*/replacement} works as expected.

On the command line, echo ${...} works as expected for both expressions,
printing nothing when foo is the empty string.

----- End forwarded message -----


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

Reply via email to