From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: stefan@marxist.se, contact@parouby.fr, 46055@debbugs.gnu.org
Subject: bug#46055: [PATCH] Add rust lang to etags
Date: Thu, 20 May 2021 13:03:58 +0300 [thread overview]
Message-ID: <83y2c9oh69.fsf@gnu.org> (raw)
In-Reply-To: <87im3gf965.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 18 May 2021 15:44:50 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: pot@gnu.org, stefan@marxist.se, contact@parouby.fr,
> 46055@debbugs.gnu.org
> Date: Tue, 18 May 2021 15:44:50 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The test suite uses the same source files for 7 different runs, each
> > time invoking etags with different command-line switches. So whenever
> > you add a new source file, you need to run make, and each time it
> > fails, copy the left-over ETAGS file into ETAGS.good_1, ETAGS.good_2,
> > etc., one by one.
>
> Ah, I see. Putting this info in a README in that directory would be
> helpful for the next person who wonders how it works, though.
Done.
next prev parent reply other threads:[~2021-05-20 10:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 19:01 bug#46055: [PATCH] Add rust lang to etags Pierre-Antoine Rouby
2021-01-23 19:59 ` Lars Ingebrigtsen
2021-01-23 20:23 ` Eli Zaretskii
2021-01-25 10:08 ` parouby
2021-01-25 10:09 ` Lars Ingebrigtsen
2021-04-21 3:19 ` Stefan Kangas
2021-04-21 8:54 ` Eli Zaretskii
2021-01-25 10:15 ` Pierre-Antoine Rouby
2021-01-25 14:33 ` Pierre-Antoine Rouby
2021-04-21 12:39 ` Stefan Kangas
2021-04-21 15:02 ` Francesco Potortì
2021-05-17 15:23 ` Lars Ingebrigtsen
2021-05-17 15:51 ` Eli Zaretskii
2021-05-17 16:08 ` Lars Ingebrigtsen
2021-05-17 16:14 ` Eli Zaretskii
2021-05-17 16:27 ` Lars Ingebrigtsen
2021-05-17 16:31 ` Lars Ingebrigtsen
2021-05-17 16:40 ` Eli Zaretskii
2021-05-18 13:44 ` Lars Ingebrigtsen
2021-05-20 10:03 ` Eli Zaretskii [this message]
2021-05-17 15:21 ` 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=83y2c9oh69.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46055@debbugs.gnu.org \
--cc=contact@parouby.fr \
--cc=larsi@gnus.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).