From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: william.a.george@gmail.com Newsgroups: gmane.emacs.help Subject: Re: Parsing compilation error/warning not possible. Date: 22 Dec 2006 03:53:26 -0800 Organization: http://groups.google.com Message-ID: <1166788406.516892.99320@48g2000cwx.googlegroups.com> References: <1166531810.419268.36210@t46g2000cwa.googlegroups.com> <1166555911.178767.309200@n67g2000cwd.googlegroups.com> <1166560684.889573.69150@80g2000cwy.googlegroups.com> <1166605097.303161.145590@t46g2000cwa.googlegroups.com> <1166640852.521062.79270@i12g2000cwa.googlegroups.com> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: sea.gmane.org 1166791243 29325 80.91.229.10 (22 Dec 2006 12:40:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 22 Dec 2006 12:40:43 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Dec 22 13:40:42 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1GxjhW-0001Gg-14 for geh-help-gnu-emacs@m.gmane.org; Fri, 22 Dec 2006 13:40:38 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GxjhV-0004J3-HL for geh-help-gnu-emacs@m.gmane.org; Fri, 22 Dec 2006 07:40:37 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!48g2000cwx.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 61 Original-NNTP-Posting-Host: 194.103.159.2 Original-X-Trace: posting.google.com 1166788412 31323 127.0.0.1 (22 Dec 2006 11:53:32 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Fri, 22 Dec 2006 11:53:32 +0000 (UTC) In-Reply-To: <1166640852.521062.79270@i12g2000cwa.googlegroups.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: 48g2000cwx.googlegroups.com; posting-host=194.103.159.2; posting-account=3aEwkg0AAACjdMYn5Wo2v2XLndflpiJl Original-Xref: shelby.stanford.edu gnu.emacs.help:144230 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:39834 Archived-At: Robert Thorpe wrote: > william.a.george@gmail.com wrote: > > william.a.george@gmail.com wrote: > > > Robert Thorpe skrev: > > > > > > > william.a.george@gmail.com wrote: > > > > > Hi. > > > > > I'm using Emacs on WindowsXP. > > > > > I make compilations through emacs with an own written Makefile. The > > > > > compilation result is presented on a new buffer. It should be possible > > > > > to click on the error or warning message to go directly to the > > > > > corresponding line in the file where the error is. > > > > > But I can't make it happen. I have read a little bit about this, and > > > > > what I could find is something about (compilation-error-regexp-alist) > > > > > that should fix this in someway. > > > > > Can anyone tell me how this should be done? > > > > > > > > Generally you do M-x compile > > > > Then enter the command to make the program, eg "make" > > > > Then you can select the errors one at a time by pressing C-x ` > > > > > > > > This will only work if your compiler emits messages in a format > > > > understood by Emacs compile-mode. > > > > > > Thanks for your response. > > > The compilation part is OK. The problem is that it is not possible to > > > select the errors in any way. Not by C-x or clicking mouse 2 button or > > > any other way. > > > The question is if my compiler is emitting messages in a format that is > > > understood by emacs compile-mode, as you said. > > > How can I make the compile-mode to understand my compiler messages? > > > > Hi again. > > I wanted to show the syntax for errors and warnings generated by my > > compiler: > > terminal.c: > > 5946: while ( (*buf_p != ':') && (*buf_p != CR) && (*buf_p != '\0') > > ) > > E 42: syntax error, expecting statement > > 5997: } > > W 68: function "GetIntelHex": parameter "stream" not used > > W 183: variable 'content_p' possibly uninitialized > > total errors: 1, warnings: 2 > > > > Maybe this can help in case emacs doesn't understand the compilers > > generated errors/warnings. > > I don't think it does. There is a standard in the GNU coding standards > for errors, what you've showed me doesn't follow it. > > You can though write your own compilation-parse-errors, or more simply > customize compilation-error-regexp-alist to recognise what you need. Hi Again. That is exactly what I wanted to know. How do tailor my own compilation-parse-errors. It would be nice if you could give me some hints or examples... I'm a beginner when it comes to emacs and lisp. Thanks.