[kernel] bug#156: kernel] bug#156: zsh's backticks fail with lesspipe

X-PA-RISC Linux-PR-Message: report 156
X-PA-RISC Linux-PR-Package: kernel
X-Loop: daniel_frazier@hp.com
Received: via spool by 156-bugs@bugs.parisc-linux.org id=B156.10069823864558
          (code B ref 156); Wed, 28 Nov 2001 21:33:01 GMT
Date: Wed, 28 Nov 2001 21:19:43 +0000
From: Matthew Wilcox <willy@debian.org>
To: Matthew Wilcox <willy@debian.org>, 156@bugs.parisc-linux.org
Cc: zsh@packages.debian.org
Message-ID: <20011128211943.D24794@parcelfarce.linux.theplanet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <no.id>; from kernel-admin@lists.parisc-linux.org on Wed, Nov 28, 2001 at 08:49:05PM +0000
Sender: <willy@www.linux.org.uk>

> FYI:
> $ dpkg --status kernel-image-2.4.14-64-smp |grep Version
> Version: 11.1

hmm.  on jagu (my personal machine):

Linux jagu 2.4.14-pa10 #92 SMP Sat Nov 24 15:05:45 MST 2001 parisc64 unknown

zsh exhibits no problems.  the specific example:

[willy@jagu:~]% eval `lesspipe`

works _just fine_

[willy@jagu:~]% lesspipe
export LESSOPEN="| /usr/bin/lesspipe %s";
export LESSCLOSE="/usr/bin/lesspipe %s %s";
# If you tried to view a file with a name that starts with '#', you
# might see this message instead of the file's contents.
# To view the contents, try to put './' ahead of the filename when
# calling less.

When I upgrade jagu to zsh 4.0.4-4, the problem reappears.  Downgrading to
4.0.4-3 fixes the problem.  So the problem seems to have been introduced
between 4.0.4-3 and 4.0.4-4.  Clint?

-- 
Revolutions do not require corporate support.