Improving docs about lines processing

[wfranzini]

As a conduit and haskell newbie, I'm having problems understanding how conduit should be used processing text file one line at a time.

I'm going to list the things that confuses me, but I also volunteer to improve the docs (with some guidance)

• Why lineC produce only one line?
• Why linesUnbounded has a warning about memory exhaustion and lineC is immune from this problem?
• What's the proper way to write a numbering lines function (aka nl) without using linesUnbounded or splitOnUnboundedE?
• What's the proper way to process a text file where lines are split using
  • C convention (i.e. if the last char is '\' then the next line must be joined with the current one discarding the '\' and the '\n')
  • LDIF convention (i.e. if the first char is space then the line should be joined with the previous one discarding both '\n' and ' ')

Feel free to close the issue if you think the documentation is ok and my difficulties are only due to my ignorance :-)

[snoyberg]

There's a section in the README that addresses some of your questions (hopefully the first 3):

https://github.com/snoyberg/conduit#forced-consumption

There's no built-in solution for the C/LDIF convention approach you mention, you'd want to write your own ConduitT that awaits and yields, possibly with a leftover.