From: "O'Brien, Will" <will.08rien@gmail.com>
To: Randy Taylor <dev@rjt.dev>
Cc: Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
74786@debbugs.gnu.org
Subject: bug#74786: [PATCH] Add custom args to test compile step
Date: Tue, 17 Dec 2024 08:34:05 +0000 [thread overview]
Message-ID: <m2msgupv2a.fsf@gmail.com> (raw)
In-Reply-To: <qiGZzqzr2w1yz2_zY7_ZZu2kMlzo68dOzRObNrgHBLO2W8WylmihKjSbn8ebwkv7nzQaEP1ervnMT95a1r9IyTiGiXAMTJuHQ_d_ItqcOtw=@rjt.dev> (Randy Taylor's message of "Sun, 15 Dec 2024 02:17:55 +0000")
On Sun, Dec 15 2024 at 02:17, Randy Taylor <dev@rjt.dev> wrote:
> On Wednesday, December 11th, 2024 at 11:31, O'Brien, Will <will.08rien@gmail.com> wrote:
>> [...]
>>
>> Ah, thanks! I've attached a new patch with the simplification.
>>
>> best
>> --
>> will
>
> Thanks for working on this.
>
> +(defcustom go-ts-mode-test-args nil
> + "List of extra args for the Go test commands."
> Should we call this `go-ts-mode-test-flags' instead?
> That seems to be the parlance golang uses, and there is an official
> `-args' that go test supports that has a specific behaviour:
> -args
> Pass the remainder of the command line (everything after -args)
> to the test binary, uninterpreted and unchanged.
> Because this flag consumes the remainder of the command line,
> the package list (if present) must appear before this flag.
>
> + (compile (format "go test %s -v %s -run '%s'"
> + (string-join go-ts-mode-test-args)
> With the above in mind, we may want to move the %s to the absolute
> end so that -args could be used without catastrophe.
Got it. Right I'll work on this and test out a few options with
combinations flags.
> This will also need a commit message and a NEWS entry.
> See the CONTRIBUTE file for details.
Ok, will send new patch with code changes and NEW entry along with
a commit message.
Thank you!
--
will
next prev parent reply other threads:[~2024-12-17 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:18 bug#74786: [PATCH] Add custom args to test compile step O'Brien, Will
2024-12-11 15:45 ` Eli Zaretskii
2024-12-11 15:58 ` Robert Pluim
2024-12-11 16:31 ` O'Brien, Will
2024-12-15 2:17 ` Randy Taylor
2024-12-17 8:34 ` O'Brien, Will [this message]
2024-12-19 16:20 ` O'Brien, Will
2024-12-20 16:14 ` O'Brien, Will
2024-12-17 2:41 ` J.P.
2024-12-17 8:32 ` O'Brien, Will
2024-12-11 16:30 ` O'Brien, Will
2024-12-11 17:10 ` Eli Zaretskii
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=m2msgupv2a.fsf@gmail.com \
--to=will.08rien@gmail.com \
--cc=74786@debbugs.gnu.org \
--cc=dev@rjt.dev \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
/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.