public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
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 20:21:30 -0500	[thread overview]
Message-ID: <F2294940-15E3-45F1-93FA-BB7DEEFD0CC6@gmail.com> (raw)
In-Reply-To: <CAO2sX32HaS4QU1vj1X6mkaJTmj6SocHmKxF0APkdGuhgec-2gA@mail.gmail.com>

I do the same thing except I usually redirect it to an actual file so I can review it in an editor if I want to.
I use aliases a lot, e.g., alias apt1='sudo apt-get -y update' 2> 1, to update linux.
I use integers as filenames for scratch files.
vlc is my favorite music player now, but mplayer is fine.


On May 25, 2017, at 6:25 PM, Linux for blind general discussion <blinux-list@redhat.com> wrote:

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.

_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

  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
   ` 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

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=F2294940-15E3-45F1-93FA-BB7DEEFD0CC6@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).