From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: re: living in the console
Date: Sat, 3 Jun 2017 11:37:33 -0700 [thread overview]
Message-ID: <Pine.LNX.4.64.1706031120320.9240@server2.shellworld.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1706031400270.7417@server2.shellworld.net>
Actually I agree with Karen, even though I have been in Linux since 2003, but
subscribing to shell accounts since 1995. Sure Linux is powerful and because its
case sensative you can have practicly unlimited amount of file names. My
problems are ways which man-pages are written. They really don't adequately
explain to a new user how to use a command. I think I remember the DOS help
system much simpler. 1 of our LUG members suggested this user driven Linux
application, called "bro" from
www.bropages.org
Since I don't have it installed on this laptop, I cannot show an example, but 1
which I contributed, if you were to type
bro unrar
1 of those 4 suggestions was about useing a wild-card.
In general I was eventually able to understand a DOS batch file, but especially
since I am not a fan of punctuation, when Linux man-pages show examples, I tend
to take them quite literally.
And lastly, I would still love to run my DecTalk U S B with Vocal-Eyes, where I
was able to enjoy a large exception dictionary. Thanks for listening
Chime
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 47+ 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
` 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
` 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
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
[not found] ` <20170602170642.GA25350@lenovo.local>
` 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=Pine.LNX.4.64.1706031120320.9240@server2.shellworld.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).