From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Eli Zaretskii <eliz@gnu.org>, 48079@debbugs.gnu.org
Subject: bug#48079: Temporary files while building after native-comp merge
Date: Thu, 29 Apr 2021 08:18:31 +0000 [thread overview]
Message-ID: <xjfbl9xzep4.fsf@sdf.org> (raw)
In-Reply-To: <CADwFkmn5wbbmEVwuT8BL-w8MdndxJTg5u7_bt3W9==9PFP-Jtw@mail.gmail.com> (Stefan Kangas's message of "Wed, 28 Apr 2021 16:26:30 -0500")
Stefan Kangas <stefan@marxist.se> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>> I'm wondering, is it a real issue not to have in .gitignore files that
>> are showing up temporary?
>
> That depends on your definition of "real issue", I suppose. ;-)
>
> For me it becomes a real issue because I'm used to be working in the
> magit-status buffer while compiling, and that buffer shows all
> uncommitted files at the top and any changes at the bottom. It is
> unsettling to have these files show up there occasionally as it makes
> the changes "jump" up and down.
Probably yes :) I use magit while compiling all the time and I never
cared about those files temporary showing up under "Untracked files" (it
can also be collabsed with tab).
> But perhaps the fix is as simple as:
>
> diff --git a/.gitignore b/.gitignore
> index fcbc9cd7f4..e27ebe36d0 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -135,6 +135,7 @@ src/gl-stamp
> *.dll
> *.core
> *.elc
> +*.elc[0-9A-Za-z][0-9A-Za-z][0-9A-Za-z][0-9A-Za-z][0-9A-Za-z][0-9A-Za-z]
> *.eln
> *.o
> *.res
FWIW LGTM
Andrea
next prev parent reply other threads:[~2021-04-29 8:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 11:10 bug#48079: Temporary files while building after native-comp merge Stefan Kangas
2021-04-28 12:10 ` Eli Zaretskii
2021-04-28 12:30 ` Eli Zaretskii
2021-04-28 13:14 ` Stefan Kangas
2021-04-28 19:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-28 21:26 ` Stefan Kangas
2021-04-29 5:14 ` Eli Zaretskii
2021-04-29 8:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 9:20 ` Eli Zaretskii
2021-04-29 10:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-02 23:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-03 17:14 ` Eli Zaretskii
2022-01-06 16:10 ` Andrea Corallo
2022-01-06 16:30 ` Glenn Morris
2022-01-06 16:48 ` Eli Zaretskii
2022-01-06 17:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-07 16:30 ` Andrea Corallo
2022-01-14 15:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 11:22 ` Stefan Kangas
2021-04-29 8:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-05-02 8:09 ` Lars Ingebrigtsen
2021-05-02 10:12 ` Stefan Kangas
2021-05-02 10:18 ` Lars Ingebrigtsen
2021-05-02 21:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 8:35 ` Lars Ingebrigtsen
2021-05-05 12:11 ` Eli Zaretskii
2021-05-05 12:47 ` Lars Ingebrigtsen
2021-05-05 14:01 ` Eli Zaretskii
2021-05-05 14:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 9:15 ` Lars Ingebrigtsen
2021-05-06 10:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-28 19:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-24 12:36 ` Lars Ingebrigtsen
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=xjfbl9xzep4.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48079@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).