Hello Janina, technically your screen reader is a process in RAM, communicating with other processes, like at-spi and speech-dispatcher. Typing "orca -r", you kill this process (i.e., you remove it from the RAM), and you replace it with a new one. Here is an example. In the a terminal I type this command: didier[~]$ ps -C orca PID TTY TIME CMD 26823 tty1 00:00:34 orca In the output, PID is the process identifier. Then, I press Alt+F2 and type orca -r After that: PID TTY TIME CMD 394 tty1 00:00:00 orca didier[~]$ So the previous process disappeared and we have a new one. So technically, it is indeed a replacement, not a restart: I replaced a screen reader by a new one. Best, Didier On 15/01/2019 08:02, Linux for blind general discussion wrote: > I rely on "orca -r" quite a bit, actually. There are any number of > conditions that can silence a running Orca that can be quickly remedied > that way. Guess I never noticed I stood for "replace," and the > juxtaposition of "screen-reader" really threw me. Replace my screen > reader? With what? > > Best, > > Janina > > Linux for blind general discussion writes: >> For what it's worth, I'd agree --restart would be more intuitive and >> self-documenting from the perspective of a native English speaker >> assuming there isn't already a --restart switch that does something >> different. That said, it's ultimately the developer's decision, it's >> hardly the most esoteric command-line switch in existence, and >> honestly, I'm kind of surprised a graphical application would even >> have such a function built-in to its command-line syntax. >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/blinux-list > _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list