[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Update related to F123e

From: Peter Vágner
Subject: Update related to F123e
Date: Mon, 7 Nov 2016 13:04:28 +0100


I am not yet decided on this however currently I feel I don't want to 
have someone dictating me how to override my environment. When looking 
at emacs as it stands currently it has numerous ways on how to inwoke 
its functions. There are its as you are calling them hard to remember 
shortcuts, there are function names you can call after pressing M-x, 
there is the menu bar, there are alternate keyboard shortcuts such as 
tab, shift+tab and arrow keys working in emacs it-self.

So at this point I am not going to play with spacemacs nor any other 
prepackaged environment. My immediate goal is to try to get to 
understand these things first and then hopefully I'll get an ability to 
make proper decision about this.

I don't know how spacemacs is build but also I would like to understand 
individual tools rather than jump into something I don't know how it's 
working having to deal with some unexpected situations when it breaks.

Unfortunatelly I don't trust the community to an extend such a 
preconfiguration can really do all the things. What if I would like to 
add yet another package spacemacs does not cover, will I introduce a 
conflict, or will I have to learn both spacemacs paradigm and also 
traditional emacs built in stuff?

It's very similar feeling  to the comparison of plain Arch Linux and 
Sonar / Manjaro if you would ask me. These customized distros are good, 
people working hard on these are awesome and friendly however it adds 
another layer between the real operating system / apps / tools / 
whatewer and me.

Unfortunatelly I consider it similar to how you can get almost 
everything cloned and improved at the same time from a chinese or 
ukrainian market. Those are just repackaged originals with some minor 

I apologize if I am inadvertently offending someone, it was not intended 
at all, I am just trying to illustrate how I feel about this.



On 07.11.2016 at 12:16 Fernando Botelho wrote:
> 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
>>> Speechd at lists.freebsoft.org
>>> http://lists.freebsoft.org/mailman/listinfo/speechd

reply via email to

[Prev in Thread] Current Thread [Next in Thread]