Paul, As I mentioned in the last post, the terminal gives you access to commands in a UNIX shell. Except for the addition of Mac control commands like default s and open mostly what you can do in the terminal is the same as on Linux or BSD UNIX> Ester's book reference is quite good.
In the Terminal a sighted person sees about 23 lines of text. On the Macintosh in the default terminal configuration the computer will keep the output of every command in the terminal session to be scrolled back to. So if you have thousands of lines stored up then it makes finding a more recent item difficult. The VO system does not specifically indicate with Keyboard commands what is visible. The trackpad commander does provide this feedback if you are interacting at the lowest level (text). When you start a terminal session the voice over cursor contains the entire contents of the text buffer both visible and scrolled off screen. If you "Interact" with a two finger swipe right or control-option-shift-down you will then be able to view the text line by line or word by word. You also asked about curses... Curses is a UNIX library that allows programs to take advantage of the entire screen of a terminal no matter what brand of terminal is in use. (Remember that UNIX is 40 years old and there were not many graphical computers then.) So with the curses library programmers did not have to write code for every terminal, they just gave calls like clear screen or move cursor to line 5 column 30 , and curses would do it the most efficient way for that terminal. THis was also important when most connections to computers were 1.2 kbps. Most text editors and terminal based chat programs use the curses library. Jonathan On May 20, 2011, at 2:55 PM, Paul Erkens wrote: > Hi Esther, > It feels like the terminal is way more technical than DOS used to be, but > wanting to get to know it means I'll have to start somewhere. The post from > Jon doesn't make that much sense to me at this time. Hopefully, you can > explain some about the following things: > 1. What are scroll back items? I assume this Is your own command history with > the command outputs. True? > 2. What is the VoiceOver text block? Is it the item in the VoiceOver cursor > or something else? > 3. Why does Jon make a difference between the terminal window contents and > the VoiceOver text block? In other words, if I clear screen my terminal > window, could VoiceOver still be reporting things that are already gone for > sighted folks? > 4. What is curses mode? > > Kindly, > Paul. > ----- Original Message ----- From: "Esther" <[email protected]> > To: <[email protected]> > Sent: Friday, May 20, 2011 8:05 PM > Subject: Re: terminal and voice over > > > Hi Paul, > > First, you might want to read Jonathan Cohn's reply from last week on > terminal usability: > On May 13, 2011, Jon Cohn wrote: > >> Two more notes on terminal. >> >> by default terminal does not clear out scrollback items, so your entire >> terminal session will be in both the terminal window and the VoiceOver text >> block. You can change this in the preference panels or by hitting command-K >> when you are about to start something new.. For example: I often will pipe >> a man command to cat and but hit command-K to clear the scroll-back before >> hitting enter. Three finger swipes will let you page through the text, and >> VO-shift-J followed by VO-shift-uparrow (or shift+numpad 8 in numpad >> commander mode) will get you to the top. I bet you can guess how to get to >> the bottom. >> In terms of cursor tracking, I usually have it off in command-line mode and >> on incurses mode. Any function that will move the terminal cursor will then >> cause the VO cursor to track it, but not the other way around. > > Secondly, the best single detailed post I've read outlining using Terminal > with VoiceOver is one that Travis Siegel wrote on the Mac-Access list last > October. He lists his preference configurations as part of the post. From > the Mac-Access list archives, here's the link to his post on "Hints on using > terminal": > http://mail.tft-bbs.co.uk/pipermail/mac-access/2010/004769.html > > There's also a link on the bottom of each of the archived posts with more > information about the Mac-Access mailing list for anyone who wants to join > it. Apart from the settings issues for VoiceOver, probably the best > introduction for new users to using terminal is the guide in the Take Control > series of downloadable eBooks: "Take Control of the Mac Command Line with > Terminal". Here's the link to the description from the Take Control web > pages: > http://www.takecontrolbooks.com/command-line > > HTH. Cheers, > > Esther > > On May 20, 2011, at 06:55, Paul Erkens wrote: > >> Hi Ester, >> >> When entering terminal mode, I'm having problems with VoiceOver focusing on >> where my cursor is. Would you say terminal is accessible? If it is, then >> what am I missing that makes operating it so difficult? I'm a starter in >> terminal mode on the mac, but I do know of complex command line syntaxes >> from my DOS years. The cmd shell in windows is still my friend. What do I do >> to work nicely in terminal? Any usability suggestions? I'm very interested >> to start off with it. >> Kindly, >> Paul. >>> On Aug 26, 2010, at 9:08 PM, Esther wrote: >>> >>>> Hi Scott, >>>> >>>> Your Mac has SSH and SFTP, and other server functions built in. You can >>>> access them directly from the command line in the Terminal app. I use >>>> Terminal so frequently that I have it as one of the default apps in my >>>> dock. (The dock can be useful as a quick way to navigate to apps that you >>>> use frequently -- you can customize it to remove the apps that you don't >>>> often use, and add ones that you do.) >>>> >>>> The Terminal app is located, not in the applications folder (which you can >>>> reach in Finder with the shortcut of Command+Shift+A), but in the >>>> Utilities folder, which is a sub-folder of Applications, and which you can >>>> reach with Command+Shift+U. Then press "T" to navigate to "Terminal" and >>>> launch/open the app. I use Command+Down arrow to do this. >>>> >>>> By default you'll be using the bash shell. To use ssh, to log into your >>>> account on another system you can simply type: >>>> >>>> ssh <your login>AT<your domain> >>>> >>>> for example, if your login account name is "scott" and the machine name is >>>> "computer. granados.net", you can type: >>>> >>>> ssh [email protected] and press return >>>> >>>> or you can use the IP address in place of the domain following the AT sign: >>>> >>>> ssh [email protected] and press return >>>> >>>> then type in your password. >>>> >>>> Use a similar syntax for sftp. Macs use "Open SSH" as the protocol. >>>> >>>> If you have some Unix/Linux background, there's an old web site: "Top Ten >>>> Mac OS X Hints for Unix Geeks": >>>> http://www.macdevcenter >>> > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
