From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: living in the consolex
Date: Mon, 29 May 2017 08:40:08 -0400 [thread overview]
Message-ID: <20170529124008.GA1965@opera.rednote.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1705260712570.3164@willempc.meraka.csir.co.za>
Willem:
The see command is a new one to me, and it's not on my system. What
package provides that? It sounds very useful.
tia
Janina
Linux for blind general discussion writes:
> Hi,
> It has a -really-quiet option which stop most output.
> Also just shut up your screen reader while playing music will work.
> If it is speakup, press the right bottom key on your keyboard, the enter key
> on the numpad for shut up.
> You can also set some config parameter in the mplayer config file in /etc to
> keep it quiet.
> for printing, just run
> print any_file_name
> If you have a properly defined mailcap file, things will just work.
> You can usually also just run
> lp any_file_name
> once your printer is configured properly.
> Web browsing is the one area where one has problems from the console.
> The lynx browser, that is l y n x, works well for many things, but does not
> support modern web pages.
> That said, I use it unless I really cannot do otherwise.
> The three commands, see, edit and print uses your mailcap file and is quite
> powerful.
> e.g. if I do
> see some_file.doc
> it will read a microsoft word document to me.
> If I do
> see song.wav
> It will start playing the music.
> FWIW, Willem
>
>
> On Thu, 25 May 2017, Linux for blind general discussion wrote:
>
> > Well, Mark peveto here,
> > I tried mplayer, and yeah, it works, but good heavens how do I get it not to read that screen full of fluff while it plays?
> >
> >
> > Mark Peveto
> > Registered Linux user number 600552
> > Everything happens after coffee!
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
>
> --
>
> This message is subject to the CSIR's copyright terms and conditions, e-mail
> legal notice, and implemented Open Document Format (ODF) standard. The full
> disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
>
> Please consider the environment before printing this email.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina@rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
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
` 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 [this message]
` 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=20170529124008.GA1965@opera.rednote.net \
--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).