[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Encoding customization variable names
From: |
Gavin Smith |
Subject: |
Re: Encoding customization variable names |
Date: |
Tue, 31 May 2022 21:11:21 +0100 |
On Mon, May 30, 2022 at 10:32:07PM +0200, Patrice Dumas wrote:
> On Mon, May 30, 2022 at 08:04:34PM +0100, Gavin Smith wrote:
> > On Mon, May 30, 2022 at 06:43:32PM +0100, Gavin Smith wrote:
> > > On Mon, May 30, 2022 at 11:48:22AM +0200, Patrice Dumas wrote:
> >
> > > > Some tests need this either to have expected error messages, or
> > > > more fundamentaly for input file names decoding. I can propose
> > > > something similar with 'Need recoded file names' with a dummy set
> > > > on the test command line.
> > >
> > > Could some of this be fixed with customization variables added to the
> > > tests?
> >
> > >
> > > I'm going to try to see if some of the other tests can be made to pass
> > > the same way.
> >
> > Here are the changes currently needed for the test suite to pass:
>
> This looks good to me. I could do the same for the remaining tests in
> many_input_files too.
I've committed the change. Please feel free to make other changes to
complete this.