Thread: [GnuWin32-Users] sed produces strange files

Hello all,

I  have  a  problem  when  using  sed  with  the  -i
(--in-place) option.  Upon processing a file, a  new
file named like sedYNFdj6 appears in the working di-
rectory and contains an exact copy of the  resulting
file.  I was using this command line:

              sed -i -e 1,5d test.txt

with sed 4.2.1.  I don't think these files should be
created.

-- 
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments

On 6/12/2012 12:24 PM, Anton Shepelev wrote:
> 
> I  have  a  problem  when  using  sed  with  the  -i
> (--in-place) option.  Upon processing a file, a  new
> file named like sedYNFdj6 appears in the working di-
> rectory and contains an exact copy of the  resulting
> file.

Looks like a temporary file that isn't being cleaned up.

-- 
Charles Calvert

Charles Calvert:

> Looks  like  a  temporary  file  that  isn't being
> cleaned up.

Yes indeed.  But whom to contact about the  problem?
It seems to be GNUWIN32-specific...

-- 
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments

This is probably (I didn't look the source code) an usual unix to windows
porting problem: on unix (posix?) an open file can be first removed
(unlinked) and then closed  while on windows an open file can not be
removed.

In our case the temporary file is open, then it is tried to be removed
which fails (obviously there is no check if the remove call was
successfull) and then the file is closed. This is why remains in the
current dir after sed termination.

I propose to submit the requet (even better: prepare the patch) to the
original GNU sed developers. If they'll fix it the problem will be solved
once for ever. In other case the fix has to be done on GNUWIN32 port and
repeated for each new release.

Borut

On Wed, Jun 13, 2012 at 11:16 PM, Anton Shepelev <ant...@gm...>wrote:

> Charles Calvert:
>
> > Looks  like  a  temporary  file  that  isn't being
> > cleaned up.
>
> Yes indeed.  But whom to contact about the  problem?
> It seems to be GNUWIN32-specific...

On 6/14/2012 3:09 AM, Borut Ražem wrote:

[snip]

> I propose to submit the requet (even better: prepare the patch) to the
> original GNU sed developers. If they'll fix it the problem will be solved
> once for ever. In other case the fix has to be done on GNUWIN32 port and
> repeated for each new release.

This is an excellent idea.

-- 
Charles Calvert

Charles Calvert:

> > I  propose  to  submit  the requet (even better:
> > prepare the patch) to the original GNU  sed  de-
> > velopers.  If they'll fix it the problem will be
> > solved once for ever. In other case the fix  has
> > to  be  done  on  GNUWIN32 port and repeated for
> > each new release.
>
> This is an excellent idea.

Paolo Bonzini, maintainer of GNU sed, said that this
bug had been fixed in the git repository, but not in
any released version.

Borut, thanks for your expertise.

-- 
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments