Re: Espeak female
On 8/17/19, Vojtěch šmiro wrote: Please send messages to the list (not to me) > And what about this: > pkill speech-dispatch > I am using it if is something wrong. Please use one of the commands I suggested. pkill -f speech If you want to see which process will be killed by that command, try ps -ef | grep speech I assume you are using a debian system, of course. Both commands are standard unix commands. If you are using windows, I can't be of help, as I dont' use it myself. Loredana
Re: Espeak female
On Sat, Aug 17, 2019 at 11:21 AM Sebastian Humenda 1" > I don't know what the official way of restarting speech-dispatcher is, killing > it might be an option. Otherwise you can always reboot ;-). Before rebooting ... If you go the kill way from the command line: pkill -f speech This kills all user processess whose name starts with "speech". If you are root: systemctl restart speech-dispatcher If you are in the sudoers list: sudo systemctl restart speech-dispatcher Usually applications starts speech-dispatcher as needed, so killing it at the user level (pkill) should be enough. Loredana
webmail and email from command line
I find increasily difficult and error prone to read/send email via a browser and would like to either use emacs (preferred, now that it talks) or the command line. 'Though I managed to send mail to my gmail account by allowing less secure applications, this is likely not to be a viable solution (it seems that google is going to forbit less secure application access starting November first of this year and it is already a pain to use it now). Two factor authentication may well be the only solution for desktop users in a couple of months time. Your Institution willl have somebody solving this issue for you, but at home normal users who prefer to avoid using a browser for email are on their own. Once the authentication issue is solved, then any client (not only a browser) should be able to read/send mail, making life for me and possibly other visually impaired people easier. Here is what I plan to do: 1) use mbsync to fetch mail locally 2) use any tool to read/edit mail locally (I will use emacs and mu4e, bt at this point any editor and mail agent able to work with mail locally should be just fine) 3) configure exim to deal with gmail authentication to read and send mail via smtp gmail server. Is this a reasonable approach? Any comment or suggestion? Any other way of dealing with email locally, without a browser and to use the network only for reading/sending mail with an acceptable authorization? BTW, swacks is in debian and it is a very nice tool to test smtp connections from the command line: swaks --tls --auth --to @gmail.com --server smtp.gmail.com Be careful with spoken passwords .. Loredana
Re: speech-dispatcher and speechd-el client error
Hello, On Thu, Aug 8, 2019 at 8:23 PM Samuel Thibault wrote: > > Source: speechd-el > Version: 2.8-2 > Severity: important > [...] > Rather, speechd-el should be taught to use the new place. Anybody out > here to help working on the lisp speechd.el script, to make it try not > only $SPEECHD_SOCK, $XDG_RUNTIME_DIR/speech-dispatcher/speechd.sock, > and ~/.speech-dispatcher/speechd.sock, but also > /run/user//speech-dispatcher/speechd.sock? I tried the live version (debian 9.9 amd64) which includes speechd-el 2.8-2 (instead of speechd-el 2.7-1) and it works properly. Apparently the $XDG_RUNTIME_DIR (which is set both in the live i386 debian 8.5 and amd64 live 9.9) is correctly used by speechd-el 2.8-2 but not by speechd-el 2.7-2.This is only an educated guess, I haven't checked the source code. Loredana
Re: speech-dispatcher and speechd-el client error
> Which version of speechd-el do you use? I had the problem with the > version in wheezy, but from jessie the path is correct. > speechd-el 2.8 debian 8.5 live i386 speechd-el 2.7.1 I am using an old spare machine for testing. I'l try newer versions and see whether the problem is gone. I am rather new to this low vision problem, thanks to everybody in this list for their support. Hopefully I will provide my two cents once I find a good solution. Still gasping ... --- Loredana
Re: speech-dispatcher and speechd-el client error
Thank you very much, that solved the problem. Now emacs speaks on startup. Just wonder. Should such a symbolick link be added automatically when installing the speech-dispatcher package? It could save time and some frustration to people less stubborn than me... On Tue, Aug 6, 2019 at 12:50 PM Raphaël POITEVIN wrote: > > Hi! > > loredana writes: > > ssip-connection-error: (file-error make client process failed no such > > file or directory :name speechd :family local :remote > > /home/user/.speech-dispatcher/speechd.sock) > > Check that path: > /run/user//speech-dispatcher > create an symbolink link into /home/user/.speech-dispatcher > > Regards, > -- > Raphaël >
speech-dispatcher and speechd-el client error
Greetings, I am trying to use the emacs client for speech-dispatehcer, but I get an error: ssip-connection-error: (file-error make client process failed no such file or directory :name speechd :family local :remote /home/user/.speech-dispatcher/speechd.sock) Indeed, the .speech-dispatcher directory does not exist. I am visually impaired and experimenting with a live jessie version of debian on top of which I have installed emacs and speechd-el. Speech-dispatcher itself seems to work properly (spd-say speaks and I am able to change the configuration from the command line with spd-conf) so I guess the problem may be some environmental variable or compiled variable value that does not match the expectations. Can anyone point me in the right direction? I have been using debian since debian potato and emacs since longer. I may be able to compile from source but it may be difficult now that my vision is so poor to experiment a lot. However, I am definitely motivated to do my best to solve the problem, just let me know how I can help myself and others. Thanks in advance Loredana Lo Conte
Re: broken xcalib
On Fri, Oct 27, 2017 at 9:25 AM, Alex ARNAUD <alexarn...@hypra.fr> wrote: > I can confirm the issue. A low-vision person reports me this issue. There is > a workaround to solve the issue if you are able to change the default xorg > configuration. Could you please explain the workaround or point us somewhere? Thanks, Loredana
