From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28349@debbugs.gnu.org
Subject: bug#28349: 26.0.50; compilation mode syntax highlighting incorrect
Date: Sat, 16 Sep 2017 19:30:36 +0100 [thread overview]
Message-ID: <CAPM58oib42w5RWbY_u74B2ws1=-qu+6EHV1KTs0Vvnw8jy-tfA@mail.gmail.com> (raw)
In-Reply-To: <CAPM58ohJ4sZvcdzMBHVPvQWXTVx0_g6Y0KERA_2ZiANtA1oKHA@mail.gmail.com>
On 11 September 2017 at 20:51, Richard Copley <rcopley@gmail.com> wrote:
> On 11 September 2017 at 17:56, Eli Zaretskii <eliz@gnu.org> wrote:
>> Thanks. Can you post a short file which exhibits the problem under
>> compilation-mode? I tried to use your examples in this discussion,
>> but none of them triggers these errors, so I'm probably missing
>> something.
>
> I'll keep trying to come up with an example.
>
> Some of the key ingredients:
> * Native Windows Emacs
> * MSYS make
> * An "Entering directory /c/..." message
> * An error or warning
>
> There might be another ingredient that's specific to my
> environment, but I don't think so.
I had my own file-name-handler-alist entry that clobbered the match
data by calling (unmsys--filename) from "subr.el". Not an Emacs bug.
Ignore my previous attribution of this to file-truename.
next prev parent reply other threads:[~2017-09-16 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 19:21 bug#28349: 26.0.50; compilation mode syntax highlighting incorrect Richard Copley
2017-09-05 15:26 ` Eli Zaretskii
2017-09-09 18:05 ` Eli Zaretskii
2017-09-10 17:21 ` Tom Tromey
2017-09-10 18:33 ` Richard Copley
2017-09-10 19:42 ` Eli Zaretskii
2017-09-10 19:57 ` Richard Copley
2017-09-10 22:41 ` Richard Copley
2017-09-11 14:53 ` Eli Zaretskii
2017-09-11 15:33 ` Richard Copley
2017-09-11 16:56 ` Eli Zaretskii
2017-09-11 19:51 ` Richard Copley
2017-09-16 18:30 ` Richard Copley [this message]
2017-09-16 18:37 ` Eli Zaretskii
2017-09-16 18:49 ` Richard Copley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58oib42w5RWbY_u74B2ws1=-qu+6EHV1KTs0Vvnw8jy-tfA@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=28349@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.