I'm building for ESP and it looks like some gcc messages are being filtered out when displaying results in the Output window.  In this case there appears to be mixed \ and / in the path.  I think there may be other cases where the line doesn't start with a path (message split to multiple lines?).
[code]
Executing from commandline:

...AppData\Local\V.Micro\Arduino\Builds\IRServerVS\generic\config.cpp.o: In function `Config::Config(String)':
...AppData\Local\V.Micro\Arduino\Builds\IRServerVS\generic/config.cpp:36: undefined reference to `timeString(long)'
...AppData\Local\V.Micro\Arduino\Builds\IRServerVS\generic/config.cpp:39: undefined reference to `timeString(long)'
collect2.exe: error: ld returned 1 exit status

Output window after compiling in VS:

config.cpp.o:In function `Config::Config(String)':
collect2.exe*:error: ld returned 1 exit status
[/code]

Thanks, actually I just fixed that yesterday. There will be a release later today I hope.

More info in the "work in progress" post
http://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

A very annoying problem and I think it's been like that for a while!!

Great, thanks!

Fixed in the latest release for visual studio there were a lot of missing messages as you correctly stated. The issue had got even worse since arduino started to use an updated toolchain a few months ago.

Double click drill down

The drill down into source should always be possible when line,column numbers show in the message. Other messages should often also drill down into the correct underlying core or library sources if additional paths were included in the original message.

For information

If you ask why not just show the message in raw form its because most of the paths are wrong and/or point to the wrong code location. Keep in mind that all .ino files are combined into a single .cpp in a temp folder for compile. So all project sources are copied to the temp folder and compiled from there. Line number for .ino sources have to convert from the combined .cpp file to the correct line in the correct .ino file, also taking into account the automatically generated function prototypes and includes that are placed before all .ino code. Finally vs can't interpret the file,line,col messages returned by the gcc compiler so the also get re-jigged.