Since white space lines are removed on file load the line number feature is very useful within log fusion itself, yet, when a file is opened with an external editor the line numbers don't match.
Can we have another checkbox below the "limit the number of bytes to load" option where for "include blank lines from log"?
The ONLY reason i would ever use this is if i had to pull hash data from an encrypted log and i need to include the whitespace as part of the log snip when performing analysis on that log data in other tools.
EDIT: I JUST noticed the skip blank lines feature request from 2 months ago. so i can definitely say i second that feature...
Nov 9, 2011 (modified Nov 9, 2011)
•
#1