From: Kevin Ryde <user42@zip.com.au>
To: emacs-pretest-bug@gnu.org
Subject: bug#3927: 23.1.50; etc/compilation.txt sample perl-glib from recent work
Date: Sat, 25 Jul 2009 22:38:00 +1000 [thread overview]
Message-ID: <87ab2t3plj.fsf@blah.blah> (raw)
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
While going through my compilation regexps I noticed this one which got
a fix lately but didn't get into compilation.txt, which might help it
stay fixed :-).
2009-07-25 Kevin Ryde <user42@zip.com.au>
* compilation.txt (perl): Add a note on store::odrecall versus program
name font locking. Add a Perl-Glib sample message which was the
subject of a recent bug (of matching too much).
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: compilation.txt.perl-glib.diff --]
[-- Type: text/x-diff, Size: 1208 bytes --]
*** compilation.txt 11 Jul 2009 07:12:00 +1000 1.27
--- compilation.txt 25 Jul 2009 22:03:09 +1000
***************
*** 300,311 ****
--- 300,326 ----
symbol: perl
+ For reference, the font-lock "Command output lines" pattern which
+ highlights "make:" etc program names also hits "store:" in the
+ "store::odrecall" module name here. That's not really wanted, but
+ it's harmless since the error match overrides it.
+
+
syntax error at automake line 922, near "':'"
Died at test.pl line 27.
store::odrecall('File_A', 'x2') called at store.pm line 90
(in cleanup) something bad at foo.pl line 3 during global destruction.
+ The following 'orrible looking bit is from the Perl-Glib module. It's
+ a Glib message put through Perl warn() to get "at FILENAME line N".
+ The aim is to match the Perl filename/linenum part since that's going
+ to be the offending code. As long as the "gnu" patterns are tight
+ enough not to take the "... WARNING **:" as a filename it should be
+ fine.
+
+ GLib-GObject-WARNING **: /build/buildd/glib2.0-2.14.5/gobject/gsignal.c:1741: instance `0x8206790' has no handler with id `1234' at t-compilation-perl-gtk.pl line 3.
+
* PHP
symbol: php
[-- Attachment #3: Type: text/plain, Size: 537 bytes --]
In GNU Emacs 23.1.50.4 (i586-pc-linux-gnu, GTK+ Version 2.16.4)
of 2009-07-24 on blah.blah
configured using `configure 'CFLAGS=-O -g' '--prefix=/down/emacs/b/inst' '--with-x-toolkit=gtk''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_AU
value of $XMODIFIERS: nil
locale-coding-system: iso-latin-1-unix
default-enable-multibyte-characters: t
next reply other threads:[~2009-07-25 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87skgj77rz.fsf@cyd.mit.edu>
2009-07-25 12:38 ` Kevin Ryde [this message]
2009-07-26 16:05 ` bug#3927: marked as done (23.1.50; etc/compilation.txt sample perl-glib from recent work) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ab2t3plj.fsf@blah.blah \
--to=user42@zip.com.au \
--cc=3927@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).