Re: Update related to F123e
Fernando Botelho <[email protected]>
| Newsgroups | gmane.linux.redhat.blinux.general |
|---|---|
| Organization | F123 |
| Message-ID | <[email protected]> |
I myself, will migrate to Mutt or Emacs. F On 11/07/2016 03:31 PM, John G Heim wrote: > Stupid orca & thunderbird!!! I keep responding to the wrong messages. > > > > > > On 11/07/2016 10:02 AM, John G Heim wrote: >> I thought it was a one-time thing. It wasn't clear in your original >> message that it happens every time. I'll fix it. >> >> >> >> >> On 11/07/2016 05:35 AM, Jude DaShiell wrote: >>> A file emacspeak-easy-howto has some useful information in it. I'll >>> search my bookmarks and see if I can locate a link, but a google >>> search with file:emacspeak-easy-howto ought to locate it if I don't >>> have it in my bookmarks. >>> >>> On Mon, 7 Nov 2016, Fernando Botelho wrote: >>> >>>> Date: Mon, 7 Nov 2016 06:16:20 >>>> From: Fernando Botelho <[email protected]> >>>> To: Peter V?gner <[email protected]>, [email protected], >>>> [email protected], [email protected] >>>> Subject: Re: Update related to F123e >>>> >>>> Peter, we have now linked to your first post on this topic. >>>> >>>> Do you have plans to research the possibility of importing >>>> Spacemacs keybindings to Emacs before you memorize too many of >>>> those Emacs keybindings? >>>> >>>> Fernando >>>> >>>> >>>> On 11/07/2016 07:53 AM, Peter V?gner wrote: >>>>> Hello, >>>>> >>>>> >>>>> It took me a long time to decide but I have attempted to start >>>>> first blog post of what I hope will be a series on short tips on >>>>> emacs accessibility. >>>>> >>>>> For example I am looking into it for about a year sporadically. >>>>> >>>>> I like F123E plan but instead of automation I would rather like to >>>>> do something that would build on Arch linux philosophy. I am not >>>>> going to rewrote the documentation but I would like to try showing >>>>> some success stories while handling these things. Most of the >>>>> articles end with a message saying something like it has a bit >>>>> higher learning curve etc but unfortunatelly very little of them >>>>> actually showcase how to go about changing that. >>>>> >>>>> Let's see how this attempt will turn out. >>>>> >>>>> >>>>> So far I have got into basic buffer navigation and manipulation >>>>> commands, navigating around emacs in general, emacs editing >>>>> commands, understood so called easy customizations, got my-self to >>>>> install and upgrade packages from elpa / melpa, briefly started >>>>> playing with org mode, learned about basic dired file manipulation >>>>> features, managed to connect to twitter with twittering-mode. And >>>>> some invisible issues along my way such as debugging issues with >>>>> request.el library and curl, getting epg working with gpg. >>>>> >>>>> These are things I hope I have learned enough so I can comfortably >>>>> use them. >>>>> >>>>> >>>>> >>>>> Next on my todo list are knowing speechd-el better, emacs packages >>>>> such as matrix-client for inovative instant messaging and more, >>>>> jabber for classic messaging, gnus for email, sauron for >>>>> integrated notifications. >>>>> >>>>> >>>>> This is my initial plan and these are things I wish to eventually >>>>> cover later. >>>>> >>>>> >>>>> My first article just talks about installing and running emacs for >>>>> the first time. >>>>> >>>>> >>>>> https://pvagner.tk/2016/emacs-a11y-tip-1-introduction-and-how-to-install >>>>> >>>>> >>>>> >>>>> Of course if you have ideas, comments, anything feel free to post. >>>>> >>>>> >>>>> Thanks and greetings >>>>> >>>>> >>>>> >>>>> Peter >>>>> >>>>> >>>>> >>>>> >>>>> On 06.11.2016 at 18:17 Fernando Botelho wrote: >>>>>> Thanks to those who have sent feedback to my emails to various >>>>>> lists. >>>>>> >>>>>> So far this is what I have found out: >>>>>> >>>>>> A lot of people are in agreement regarding the need for: >>>>>> >>>>>> * An easier way to install and setup Emacspeak; >>>>>> * An easier way for Emacspeak to use eSpeak and/or other >>>>>> synthesizers; and >>>>>> * At least one expert also mentioned that Spacemacs does not >>>>>> solve all issues, as it has some inaccessible output. >>>>>> >>>>>> However, it has been said that: >>>>>> >>>>>> * SpeechD-el can make Emacs accessible; >>>>>> * SpeechD-el already works well with Speech-Dispatcher and eSpeak; >>>>>> * SpeechD-el is already easier to install and is multilingual by >>>>>> default; >>>>>> * SpeechD-el could even be used to bridge communication between >>>>>> Emacspeak and Speech-Dispatcher and eSpeak; and >>>>>> * it might be easier to just bring Spacemacs keybindings to >>>>>> classic Emacs rather than move all of the SpeechD-el or Emacspeak >>>>>> accessibility to Spacemacs. >>>>>> >>>>>> I have updated our project document accordingly: >>>>>> https://public.f123.org/experimental/About-F123e.html >>>>>> >>>>>> Best, >>>>>> >>>>>> Fernando >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Speechd mailing list >>>>>> [email protected] >>>>>> http://lists.freebsoft.org/mailman/listinfo/speechd >>>>> >>>> >>>> _______________________________________________ >>>> Blinux-list mailing list >>>> [email protected] >>>> https://www.redhat.com/mailman/listinfo/blinux-list >>> >> >