From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 09/22] more: allow non-interactive invocation of the command
Date: Thu, 24 Jan 2013 19:33:50 +0100 [thread overview]
Message-ID: <20130124183350.GD27413@x2.net.home> (raw)
In-Reply-To: <1358554151-25985-10-git-send-email-kerolasa@iki.fi>
On Sat, Jan 19, 2013 at 12:08:58AM +0000, Sami Kerola wrote:
> - no_tty = tcgetattr(fileno(stdout), &otty);
> + if (non_interactive == 0)
> + no_tty = tcgetattr(fileno(stdout), &otty);
I have added #ifdef TEST_PROGRAM to enable non-interactive mode, and
in the tests we use "test_more" binary. It seems less invasive than to
add the -n option.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2013-01-24 18:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 0:08 [PATCH 00/22] tests: lots of tests Sami Kerola
2013-01-19 0:08 ` [PATCH 01/22] build-sys: add gcov files to .gitignore Sami Kerola
2013-01-19 0:08 ` [PATCH 02/22] tests: add rev(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 03/22] tests: add utmpdump(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 04/22] tests: add getopt(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 05/22] tests: add mcookie(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 06/22] tests: add tailf(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 07/22] tests: add ul(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 08/22] tests: add ionice(1) check Sami Kerola
2013-01-19 0:08 ` [PATCH 09/22] more: allow non-interactive invocation of the command Sami Kerola
2013-01-24 18:33 ` Karel Zak [this message]
2013-01-19 0:08 ` [PATCH 10/22] tests: add more(1) check Sami Kerola
2013-01-19 0:09 ` [PATCH 11/22] tests: add line(1) check Sami Kerola
2013-01-19 0:09 ` [PATCH 12/22] tests: add dmesg(1) check Sami Kerola
2013-01-19 0:09 ` [PATCH 13/22] dmesg: add boundary check to facility & level array usage Sami Kerola
2013-01-19 0:09 ` [PATCH 14/22] tests: add setsid(1) check Sami Kerola
2013-01-19 0:09 ` [PATCH 15/22] tests: add setarch(8) check Sami Kerola
2013-01-19 0:09 ` [PATCH 16/22] tests: add fallocate(1) check Sami Kerola
2013-01-19 0:09 ` [PATCH 17/22] docs: mkswap.8: recommend fallocate(1) Sami Kerola
2013-01-25 9:17 ` Karel Zak
2013-01-19 0:09 ` [PATCH 18/22] tests: add isosize(1) check Sami Kerola
2013-01-25 9:25 ` Karel Zak
2013-01-19 0:09 ` [PATCH 19/22] tests: add whereis(1) check Sami Kerola
2013-01-19 0:09 ` [PATCH 20/22] dmesg: parse level when --color is used Sami Kerola
2013-01-19 0:09 ` [PATCH 21/22] tests: add ipcmk(1) and ipcrm(1) checks Sami Kerola
2013-01-19 0:09 ` [PATCH 22/22] tests: sort commands strings Sami Kerola
2013-01-25 10:09 ` [PATCH 00/22] tests: lots of tests Karel Zak
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=20130124183350.GD27413@x2.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox