unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Evgeniy Dushistov <dushistov@mail.ru>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 36001@debbugs.gnu.org
Subject: bug#36001: 26.2; compile-mode.el/compilation-mode spontaneous behaviour
Date: Thu, 30 May 2019 17:10:27 +0300	[thread overview]
Message-ID: <20190530141027.GB111022@15inch.localdomain> (raw)
In-Reply-To: <871s0gw4py.fsf@tcd.ie>

On Thu, May 30, 2019 at 12:40:09PM +0100, Basil L. Contovounesios wrote:
> Evgeniy Dushistov <dushistov@mail.ru> writes:
> 
> > compile-mode.el (compilation-mode) works in really spontaneous way.
> >
> > I run compilation via:
> >
> > (defun rust-compile ()
> >   "Compile using `cargo build`"
> >   (interactive)
> >   (compile "cargo build"))
> >  
> > Sometimes errors are highlighted, sometimes aren't.
> > For example I run compilation, and the first error is not highlighted:
> >
> > https://user-images.githubusercontent.com/156697/58186628-f013bf80-7cbd-11e9-956b-741e64fabbe6.png
> >
> > Then I switch buffer '*compilation*' and run M-x compilation-mode,
> > and error is highlighted in the right way:
> >
> > https://user-images.githubusercontent.com/156697/58186629-f013bf80-7cbd-11e9-88c4-7a1fc90b08d8.png
> >
> > Also jump to the error via C-x ` sometimes doesn't work (emacs insitead of jump to code,
> > asks where find source file), but after I would switch to '*compilation*' and
> > run M-x compilation-mode, C-x ` works again. 
> >
> > 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.
> 
> Are you able to reproduce these issues starting from 'emacs -Q'?
> 

I can reproduce it with:
emacs -Q 
M-: (load "~/.emacs.d/elpa/rust-mode-20190517.2037/rust-mode.el")

and then 
M-x compile
cargo build <-- command to run rust code compilation

Interesting, that `cargo build` works in deterministic way, it produces
the same output for the same code set on the Rust language.
So the content of *compilation* buffer is always the same,
except of course:
Compilation started at ...
Compilation exited abnormally with code 101 ...

But sometimes it renders ok, sometimes bad.
And if I run 
M-x compile
cat /tmp/saved-compilation-buffer-content.txt

the *compilation* rendering is always fine, no errors.


-- 
/Evgeniy





  reply	other threads:[~2019-05-30 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  9:49 bug#36001: 26.2; compile-mode.el/compilation-mode spontaneous behaviour Evgeniy Dushistov
2019-05-30 11:40 ` Basil L. Contovounesios
2019-05-30 14:10   ` Evgeniy Dushistov [this message]
2019-05-30 12:01 ` Noam Postavsky
2019-05-30 13:58   ` Evgeniy Dushistov
2019-05-30 16:35     ` npostavs

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=20190530141027.GB111022@15inch.localdomain \
    --to=dushistov@mail.ru \
    --cc=36001@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).