On Wed, May 30, 2018 at 2:25 AM, John Calcote wrote:
> I've tried escaping with backslash, I've tried quoting with single quotes,
> I've tried escaping within double quotes. Nothing works. It seems the
> unquoting functionality will not be tricked into allowing a special
> character to be escaped.
On Tue, May 29, 2018 at 8:10 PM, Eric Blake wrote:
> On 05/29/2018 08:25 PM, John Calcote wrote:
>
>> I'm trying to create a test using autotest that compares the stdout of my
>> program with a string. Unfortunately, the output of the program contains
>> the path of the program. As part of its ou
On 05/29/2018 08:25 PM, John Calcote wrote:
I'm trying to create a test using autotest that compares the stdout of my
program with a string. Unfortunately, the output of the program contains
the path of the program. As part of its output, it writes its own program
name (from argv[0]) to stdout, s
On Tue, May 29, 2018 at 7:34 PM, Nick Bowler wrote:
> On 2018-05-29, John Calcote wrote:
> > I'm trying to create a test using autotest that compares the stdout of my
>
> So, we can do (totally untested)
>
> AT_INIT
> AT_SETUP([tg1])
> printf 'Hello from %s/src/prog!\n' "$abs_top_builddir" >ex
On 2018-05-29, John Calcote wrote:
> I'm trying to create a test using autotest that compares the stdout of my
> program with a string. Unfortunately, the output of the program contains
> the path of the program. As part of its output, it writes its own program
> name (from argv[0]) to stdout, so
I'm trying to create a test using autotest that compares the stdout of my
program with a string. Unfortunately, the output of the program contains
the path of the program. As part of its output, it writes its own program
name (from argv[0]) to stdout, so I have to use ${abs_top_builddir} as part
of
