The Wolfe Pack

The Wolfe Pack

because vscode extensions are prone to changing on a wimm, see git and remote explorer for example, I decided it's time to switch to a more lightweit environment, one where the screenreader would be better accomodated and the interface would be less cluttered.
The replacement must have the following:

* lsp mode
* accessible inline errors, optionally with an audio queue
* the ability to read many kinds of documents in a single workspace, most commonly encountered combo is markdown and code
* accessible autocomplete, aka emacs company mode
* powerful search. This includes searching for symbols, commands in pluggins, files matching that search, editor specific options, etc

Based on what other people told me IRL, I'm left with the following two options, which I'll have to learn from scratch, with anything required to make stuff accessible for us:

* emacs
* neovim

which do you think is better, and why?
please boost for reach and reply if you know something.

@bgtlover I'd personally go with emacs. Once you install emacspeak, basically everything in emacs is accessible to you. In terms of running code and stuff like that, I'm not sure if emacs has built in functions for doing this, but you could definitely script them in without too much difficulty. You also get some good stuff by default such as auto indent and it'll automatically tell you if braces and brackets and things like that match when you focus on the character. you should also be able to use autocomplete with that emacs mode without too much difficulty as well.

@destructatron since both emacs and vim are kinda relics at this point, I don't want to go very deep the rabbit whole, so, are there some quickstart guides as to how I setup emacs with emacspeak and probably lsp mode with rust support? probably the latter can wait, but the former is critical, my searches gave me either dead links or outdated information. Also, which emacs should I pick? the terminal one, or the one with gtk support?

@bgtlover I use the GTK version of emacs. As for setting up emacspeak it's actually very easy. Install the emacspeak AUR package and when it's done, you'll have an emacspeak binary you can use which will get emacs going with emacspeak automatically. The most up to date version of the emacspeak manual I could find is here: https://tvraman.github.io/emacspeak/manual/

@destructatron awesome, thanks! I managed to start emacs, install emacspeak and now it's a glorified nano with awesome sounds. Now that I learned how to quit it, time to go through the tutorial. But first, I have to install the rustic package for rust support with rust-analizer. Now, if only I could find an emacs that doesn't depend on gtk, it would be awesome, since sometimes I'm running on a bare tty, especially when I'm compiling heavy stuff. Anyway, thanks, I've been able to run and hear espeak at least, though speed would be awesome if it would be 100%

@bgtlover You can change the rate quite easily. Press CTRL E, then d, then r. You can enter a custom rate there. I have mine at 600 and that's nice and fast. I've had issues saving it though when customising the emacspeak group as the setting doesn't seem to save. I've heard fenrir can work with emacs in a certain way but I haven't looked if there's documentation on getting that working. What with Fenrir's current buggy state it probably won't be usable anyway until that bug is fixed.

@destructatron @bgtlover a patch to fix that bug is in coming. I’m currently testing the kernal patch that fixes it.

@storm @bgtlover If it's a kernel patch, does this mean it has to be compiled into the kernel or something with dkms or straight up recompiling the whole thing?

@destructatron @bgtlover It would mean applying the patch to the kernel and building it. But it is probably going to be in the next release, and it is being back ported to all the supported kernels, so probably in the next few days. I was given a prebuilt kernel to test, I can share the link with you if you would like it. In this build, though, sysctl tiocsti is disabled, so pasting from the clipboard doesn’t work. I have asked about that in the thread where I first reported the bug, so I’ll hopefully know more soon.

replies
0
announces
0
likes
0

@destructatron @bgtlover OIt’s live now. I just installed linux-lts and it works. In the latest kernel there’s a not yet applied patch that fixes the clipboard issue, but that’s coming next. If you use lts, though, everything should work as expected.

@destructatron yeah, I figured that out by reading more of the manual. Making it persistant is a pane in the ass, I tryed and didn't succeed, well, it's not hard to change it every time, but certainly it's annoying. About fenrir, dk what specific bug that is, but fenrir itself has been very buggy for a long while for me, as in, it doesn't want to start and all that. In any case, now I have the loading of emacspeak at the beginning of ~/.emacs, so I hear all the messages I didn't before because with the emacspeak command that basically started last. Also, is it normal that it contacts the packaging host every time it starts? I think that's because I installed lsp, company-mode and rustic by putting lisp code directly in the config file, so it's probably trying to install them every time, I should probably see that like a check for updates thing, but I'd still like it if it didn't take as much as vscode to start, perhaps I should start using the emacs-client in stead of simply emacs.

@bgtlover Do you just stick emacspeak at the top of the file or something? I'm not too good at lisp syntax yet so I'm not sure how you'd go about starting emacspeak without using the emacspeak binary.