Hi Jason, On Mo, Jun 23, 2014 at 06:16:01 +1000, Jason White wrote: >Christian Schoepplein <[email protected]> wrote: > >> One big issue is, that VoiceOver is not focusing the cursor possition >> all the times correctly. Try opening a file with vi and navigate in the >> file with arrow up and down to get spoken the current line. You will >> see, that VoiceOver sometimes reads the wrong line, sometimes the line >> above or below. >> >> Then try to use a program like mutt, my favorite mail programm :-). > >Mine too.
*lol* Yes, there is nothing better :-). >> There you also notice the focusing problems but also that VoiceOver is >> not able to track a softcursor, which is used in many of textbased >> tools. >> > >Adding the following line to your ~/.muttrc file might help: >set braille_friendly=yes > >Mutt doesn't use a soft-cursor by default anyway. I'm not sure if this setting for mutt will help. From the mutt manual: ----- 3.23. braille_friendly Type: boolean Default: no When this variable is set, mutt will place the cursor at the beginning of the current line in menus, even when the $arrow_cursor variable is unset, making it easier for blind persons using Braille displays to follow these menus. The option is unset by default because many visual terminals don't permit making the cursor invisible. ----- The problem isn't the not displayed cursor, but that VO does not track the cursor in some situations. For example, if you are in the message list and press "/" to search a particular message, VO keeps focusing the selected message in the list and does not jump to the bottom of the screen into the field where the searchterm can be inserted. I'll try the mutt setting, maybe it helps, but I believe it will not :-(. And ofcourse that will not change the problem with the lines that are not read corect in editors or in the shell. >> Maybe the problems described above can be solved by changing some >> settings for VoiceOver or for the terminal, but I've not found out what >> needs to be changed :-(. But those both problems are the major show >> stoppers for a good terminal support in Mac OS in my opinion :-(. > >It looks nasty. I'm a very intensive terminal user and that isn't going to >change, so if anyone knows a good solution to the above, suggestions would be >welcome. There've been some hints how to configure the terminal to get VO work better, but they did not work for me :-(. Regards from Munich, Christian <--- Mac Access At Mac Access Dot Net ---> To reply to this post, please address your message to [email protected] You can find an archive of all messages posted to the Mac-Access forum at either the list's own dedicated web archive: <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html> or at the public Mail Archive: <http://www.mail-archive.com/[email protected]/>. Subscribe to the list's RSS feed from: <http://www.mail-archive.com/[email protected]/maillist.xml> As the Mac Access Dot Net administrators, we do our very best to ensure that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and worm-free. However, this should in no way replace your own security strategy. We assume neither liability nor responsibility should something unpredictable happen. Please remember to update your membership preferences periodically by visiting the list website at: <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
