Package: nano
Version: 2.2.4-1, 2.2.2-1
Severity: normal

Hi,

on Debian Lenny (nano 2.0.7-4) nano was AFAIK the only editor which
was capable of editing FIFOs (at least zile and nvi can't edit
FIFOs). In Sid and Squeeze this ability of nano is mostly gone.

In my test case (see below), I wasn't even able to start it with the
contents of the FIFO, in our real life case (a wrapper around nano
which modifies the content before and after editing), nano is still
able to read from the pipe, but no more to write from it.

How to reproduce:

You need two shells (the mentioned wrapper forks for that purpose):

  Shell 1                  Shell 2
1 $ mkfifo foobar
2 $ echo bla >> foobar
3                          $ nano -t foobar
4                          Change something, save with C-x
5 $ cat foobar

This works fine on Debian Lenny (nano 2.0.7-4) as well as Ubuntu
Karmic (nano 2.0.9-2), but fails with Debian Sid, Squeeze (both nano
2.2.4-1) and Ubuntu Lucid (nano 2.2.2-1).

So I suspect this regression has been introduced with the 2.1/2.2
series of nano.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'oldstable'), (400, 
'stable'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages nano depends on:
ii  dpkg                      1.15.7.2       Debian package management system
ii  install-info              4.13a.dfsg.1-5 Manage installed documentation in 
ii  libc6                     2.10.2-9       Embedded GNU C Library: Shared lib
ii  libncursesw5              5.7+20100313-2 shared libraries for terminal hand

nano recommends no packages.

Versions of packages nano suggests:
pn  spell                         <none>     (no description available)

-- no debconf information



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

Reply via email to