bug#22568: "grep ... | tee file" drops the 'n' in its output

tags 22568 moreinfo close 22568 stop (triaging old bugs) On Fri, Feb 05, 2016 at 03:05:24PM -0700, Eric Blake wrote: > On 02/05/2016 02:41 PM, oldefoxx wrote: > > Odd problem. Seems to be partly tied to when IFS=\n is used for > > It's not obvious how grep, cat, or tee fit into the picture

bug#22568: "grep ... | tee file" drops the 'n' in its output

Odd problem. Seems to be partly tied to when IFS=\n is used for handling read statements. Can't find a way around it that works reliably, so forced to use grep ... > file; cat file or grep ... >> tmp; cat tmp; cat tmp >> file; rm tmp Not near as clean and elegant, and is always

bug#22568: "grep ... | tee file" drops the 'n' in its output

On 02/05/2016 02:41 PM, oldefoxx wrote: > Odd problem. Seems to be partly tied to when IFS=\n is used for You didn't provide enough context for us to see what you were actually typing. But if you really typed: IFS=\n stuff then that's the same as if you had typed: IFS=n which tells

bug#22568: "grep ... | tee file" drops the 'n' in its output

oldefoxx writes: > IFS=\n This is the same as IFS=n. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."