Kibana version: 5.0.0-alpha4
Server OS version: 5.0.0-alpha4
Browser version: Chrome
Browser OS version: Mac OS
Description of the problem including expected versus actual behavior:
If you attempt to open a CSV and there is an error after the point where the UI truncates things then you can't effectively troubleshoot the issue in the UI.
We need to have a horizontal scroll bar that shows where the error actually occurs.
Steps to reproduce:
Describe the feature:

Good point. The columns are truncated to prevent the browser from exploding if someone adds a csv with thousands of columns. I wonder how we could improve the errors without removing the truncation. My initial thought was to list the position of the bad columns, but that won't be very helpful when there are a large number. Any thoughts?
@Bargs What about grouping error messages together and list the positions of bad columns like this?

@ck-lee seems reasonable, I suppose just providing the column positions would be good enough for large numbers of columns as long as the user knows how to navigate around in their text editor of choice.
Nice! I will submit a PR this week. Thank you.
@ck-lee Awesome, I look forward to reviewing it!
Most helpful comment
Nice! I will submit a PR this week. Thank you.