Unreadably long message box when failing to read a file in a new project

[GoogleCodeExporter]

#What steps will reproduce the problem?
1. Add a lot of files that will trigger a "warning: LF will be replaced by CRLF"
2. Make one file unreadable, for example by having it being in use by Visual 
Studio, or changing the file permissions
3. Try to commit

#What is the expected output? What do you see instead?
I would expect to either get the warnings separately from the error, or to at 
least have the long list in a scroll box that allows you to scroll to the error.

In stead you get a message box that contains all the "warning: LF will be 
replaced by CRLF" messages, with the actual error message all the way at the 
end, which is not readable because it is way off screen.

The only way to make it readable is to drag the message box to the top of the 
screen and hold the 'up' cursor key for a few minutes until the bottom of the 
message box comes in view. Any movement of the mouse cursor during this process 
can reset progress.

#What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.8.14.0
git version 1.9.5.msysgit.0
Windows 8.1

Original issue reported on code.google.com by matlaure...@gmail.com on 25 Jun 2015 at 3:31

[GoogleCodeExporter]

1. The output is from git (Git for Windows, msysgit).
   That say, it is just shown there. :)

2. About lots of "warning: LF will be replaced by CRLF", perhaps a workaround:
   you could turn SafeCrlf to false or true, instead of warn.
   Actually, better to use .gitattributes file to deal with EOLs, 
   instead of AutoCrlf & SafeCrlf.

Improving mouse operation is possible?

Original comment by yuelinho...@gmail.com on 26 Jun 2015 at 3:07

[GoogleCodeExporter]

The warnings don't prevent you from continuing, yet they get in the way, so 
ideally there would be a button to filter them out, like you might see in 
visual studio's error window or Unity's console Window.

But it doesn't need to be that fancy for the problem to be solved. If 
potentially long messages were placed in a scrollable view, you would be able 
to read them in their entirety.

The line ending problem is one example of a situation where the problem occurs, 
there might well be other error messages that are too large for the message box.

Original comment by matlaure...@gmail.com on 26 Jun 2015 at 4:28

[GoogleCodeExporter]

Can you please exactly describe how you add the files (there are serveral ways)?

Original comment by sstrickr...@googlemail.com on 26 Jun 2015 at 9:52

[GoogleCodeExporter]

My way was using the context menu on a folder containing an existing code 
library to create a repo and then using the context menu commit and selecting 
all relevant files for addition.

Original comment by matlaure...@gmail.com on 26 Jun 2015 at 1:16