GNU bug report logs - #36001
26.2; compile-mode.el/compilation-mode spontaneous behaviour

Previous Next

Full log

Message #14 received at 36001 <at> debbugs.gnu.org (full text, mbox):

From: Evgeniy Dushistov <dushistov <at> mail.ru>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 36001 <at> debbugs.gnu.org
Subject: Re: bug#36001: 26.2; compile-mode.el/compilation-mode spontaneous
 behaviour
Date: Thu, 30 May 2019 16:58:28 +0300

[Message part 1 (text/plain, inline)]

On Thu, May 30, 2019 at 08:01:18AM -0400, Noam Postavsky wrote:
> Evgeniy Dushistov <dushistov <at> mail.ru> writes:
> 
> > These are spontaneous errors, I have ~10 good cases,
> > when all works fine vs 1 bad case, when rending or jump to source location works
> > only for subset of errors/warnings.
> 
> Could you evaluate the code below, and then post the contents of the
> *trace-output* buffer after a bad case happens.
> 
>     (defun bug-36001-clear-trace (&rest _)
>       (with-current-buffer trace-buffer
>         (let ((inhibit-read-only t))
>           (erase-buffer))))
>     (advice-add 'compile :before #'bug-36001-clear-trace)
>     (trace-function-background 'compilation-filter)

I attached two files,
one is *trace-output* another is *compilation*,
the first error is not marked as error:

> error...
>   --> macroslib/src/lib.rs:428:27

I uses rust-mode, it adds some regexps to
compilation-error-regexp-alist-alist:

https://github.com/rust-lang/rust-mode/blob/master/rust-mode.el


-- 
/Evgeniy

[trace-output (text/plain, attachment)]

[compilation (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.