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


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

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

Submitted by:  Paul Breen <noman9607>
Submitted on:  Tue Nov 25 03:34:02 2008  
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Wed Dec 23 10:22:54 2009, 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 Nov 25 03:34:02 2008, 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
  • -unavailable- added by bonzini (Posted a comment)
  • -unavailable- added by noman9607 (Submitted the item)

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

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    No Changes Have Been Made to This Item

    Back to the top

    Powered by Savane 3.1-cleanup1