From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: johnw@gnu.org, emacs-devel@gnu.org
Subject: Re: Very annoying Flymake regression in Emacs 26.1
Date: Sat, 12 May 2018 10:08:42 +0300 [thread overview]
Message-ID: <83zi15mjut.fsf@gnu.org> (raw)
In-Reply-To: <87o9hlub7t.fsf@gmail.com> (message from João Távora on Fri, 11 May 2018 22:35:50 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Fri, 11 May 2018 22:35:50 +0100
>
> 1. Navigate to a foo.c file
> 2. Turn on M-x flymake-mode
> 3. Because the legacy "proc" backend is active by default, flymake
> calls it and it makes its usual foo_flymake.c copies before doing its
> thing which is to call "CHK_SOURCES=foo_flymake.c make check-syntax"
> 4. If there isn't such a target in the Makefile, or if there isn't any Makefile,
> the backend reports a failure and flymake.el considers it disabled.
> 5. Nothing wrong until here, the problem is that the foo_flymake.c in
> step 3 is never cleaned up, and this starts littering the filesystem
> everytime you visit a .c file.
Is the above scenario the usual way of using Flymake, or is it some
variation that could be rare? If it isn't rare, I wonder how come no
one noticed until now that we are littering the filesystem with these
files.
Thanks.
next prev parent reply other threads:[~2018-05-12 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 21:35 Very annoying Flymake regression in Emacs 26.1 João Távora
2018-05-12 7:08 ` Eli Zaretskii [this message]
2018-05-12 9:01 ` João Távora
2018-05-12 9:33 ` Eli Zaretskii
2018-05-12 10:41 ` João Távora
2018-05-12 10:45 ` Eli Zaretskii
2018-05-13 5:03 ` John Wiegley
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=83zi15mjut.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=johnw@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.