buggrep - Bugs: bug #24925, line enders are not consistent in...


You are not allowed to post comments on this tracker with your current authentication level.

bug #24925: line enders are not consistent in output file

Submitted by:  Paul Breen <noman9607>
Submitted on:  Tue 25 Nov 2008 03:34:02 AM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open

Wed 23 Dec 2009 10:22:54 AM UTC, comment #1: 

Confirmed, it only occurs when the output is redirected.  See the call to SET_BINARY (1) in src/grep.c

Paolo Bonzini <bonzini>
Tue 25 Nov 2008 03:34:02 AM UTC, original submission:  

My editor reports inconsistent line enders in the output file made by the gnu grep
I have a windows xp pro sp2.
This problem will not show up on many editors, only those that insist on consistent cr-lf or 13,10(ascii)at the end of every line. This will not show up on notepad or wordpad that is included with windows for example. It does show up for win32 programmers that use the text control, however.
grep version is 2.5.3
Here is a sample command line
grep.exe -E -c -i "Alonso Quixano" DonQuixote.txt >> grepOutput.txt
Nothing wrong with the search, just the output file.
If I re-write the your output file with chr$(13,10)on every line (I program in basic) or save your file using dos cr-lf return type using source code editors everything is OK.
Paul Breen

Paul Breen <noman9607>


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by bonzini (Posted a comment)
  • -email is unavailable- added by noman9607 (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    No changes have been made to this item

    Back to the top

    Powered by Savane 3.7