Package: sed
Version: 4.2.1-6
Severity: normal
When I used the aggregated command line switches -in, I was surprised to find
out the 'n' was taken to be as the prefix of another input file. Consider the
following:
$ ls noSuchFile*
ls: cannot access noSuchFile*: No such file or directory
$ touch noSuchFile
$ sed -n '/no such line/p' noSuchFile
$ sed -in '1i\
> add that line
> ' noSuchFile
$ ls noSuchFile*
noSuchFile noSuchFilen
As you can see, the 'n' caused another output file to get created.
Not sure if I shouldn't have set severity to wishlist. Isn't now days, the
aggregated -in command line switches expected to get interpreted equivalently to
-i -n ?
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
