From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: living in the consolex
Date: Thu, 25 May 2017 23:25:26 +0000 [thread overview]
Message-ID: <CAO2sX32HaS4QU1vj1X6mkaJTmj6SocHmKxF0APkdGuhgec-2gA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705251806250.3818@southernprince>
With the console screen reader I use, I find adding
2> /dev/null
to the end of the command line does well to prevent junk text being
read over the audio being played by the program.
2> (the numeral 2 followed by the greater than/right angle bracket)
tells the terminal to redirect error messages to a file. /dev/null is
the null device and is a good candidate for redirecting output you
don't want.
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
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=CAO2sX32HaS4QU1vj1X6mkaJTmj6SocHmKxF0APkdGuhgec-2gA@mail.gmail.com \
--to=blinux-list@redhat.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.
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).