Re: [code] How to get GCC compiler errors to work

From: Mitchell <>
Date: Mon, 25 Mar 2013 15:50:00 -0400 (Eastern Daylight Time)

Hi Ryan,

On Mon, 25 Mar 2013, Ryan Pusztai wrote:

> Hi,
> I am trying to make the correct "error_details" for a newer version of GCC
> than the default TA CPP module has. GCC added 'line column' to the error
> output.
> This was easy to fix, but now my error messages from GCC don't have the
> path prepended to the filename that is compiling. This causes TA to open an
> empty buffer with just the name of the filename and it doesn't find the
> file because it is in a sub-directory. Any thoughts into a way to solve
> this. I am working with source that uses sub-directories quite a bit.
> Here is my definition in the `post_init.lua` file: (Notice the extra %d+:)
> m_run.error_detail.c = {
> pattern = '^(.-):(%d+):%d+: (.+)$',
> filename = 1, line = 2, message = 3
> }
> Here is the error message I attempt to double-click on:
> ScsSpeedDistanceProcessor.cpp:14:25: fatal error: ../CudUtils.h: No
> such file or directory
> Thoughts?

Does it work if you comment out modules/textadept/run.lua:73?

If so, I think the implementation needs to be tweaked to store the working
directory somewhere (maybe in the output or in a variable).


You are subscribed to
To change subscription settings, send an e-mail to
To unsubscribe, send an e-mail to
Received on Mon 25 Mar 2013 - 15:50:00 EDT

This archive was generated by hypermail 2.2.0 : Tue 26 Mar 2013 - 06:39:38 EDT