unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: LanX <lanx.perl@googlemail.com>
Cc: 4689@emacsbugs.donarmstrong.com
Subject: bug#4689: 23.1.50; Matching of error lines in *compilation* buffer is broken for perl-files
Date: Fri, 09 Oct 2009 17:24:48 -0400	[thread overview]
Message-ID: <oybpkg8dlr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: ec36f5050910091328w1a0c064et5f468585d9c471e9@mail.gmail.com

LanX wrote:

> Neither mode-compile nor cperl-mode are necessary to reproduce the problem.

OK. If you want someone on this list to help fix anything, then the
way to go about it is to provide a complete, self-contained recipe
starting from `emacs -Q'. This does not seem to exist anywhere in
either of the two linked threads which I took the trouble to read.

> And after 12 years a maintainer might perhaps consider to delete his email
> address.

We leave the original Author: header intact to respect people's
contribution. Note that the Maintainer: header says "FSF".

None of this is at all revelant though, because the documented
procedure for reporting an Emacs bug is to use M-x report-emacs-bug.
That is all. Do not cc every email address you might find in the
source files.





  reply	other threads:[~2009-10-09 21:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <uy8wfgt10x.fsf_-_@fencepost.gnu.org>
2009-07-25 12:42 ` bug#3928: 23.1.50; compilation-mode not matching perl and more [regression] Kevin Ryde
     [not found]   ` <handler.3928.B.124852579914015.ack@emacsbugs.donarmstrong.com>
2009-07-27  1:13     ` bug#3928: " Kevin Ryde
2009-10-13  3:45   ` bug#3928: marked as done (23.1.50; compilation-mode not matching perl and more [regression]) Emacs bug Tracking System
2009-10-09 13:40 ` bug#4689: 23.1.50; Matching of error lines in *compilation* buffer is broken for perl-files LanX
2009-10-09 16:04   ` Glenn Morris
2009-10-09 16:28     ` LanX
2009-10-12  7:51       ` Heddy Boubaker
2009-10-12 14:26         ` LanX
2009-10-12 16:24           ` Glenn Morris
2009-10-12 16:30             ` Processed: " Emacs bug Tracking System
2009-10-12 19:36             ` Glenn Morris
2009-10-12 22:04               ` LanX
2009-10-12 16:57           ` Juanma Barranquero
2009-10-09 16:39     ` Glenn Morris
2009-10-09 16:46       ` LanX
2009-10-09 18:29         ` Glenn Morris
2009-10-09 20:28           ` LanX
2009-10-09 21:24             ` Glenn Morris [this message]
2009-10-10 14:49         ` Jason Rumney
2009-10-13  3:45   ` bug#4689: marked as done (23.1.50; Matching of error lines in *compilation* buffer is broken for perl-files) 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=oybpkg8dlr.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=4689@emacsbugs.donarmstrong.com \
    --cc=lanx.perl@googlemail.com \
    /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).