[quoted lines by Sebastian Humenda on 2017/01/27 at 17:02 +0100]
>>the more I think about it, the more it makes sense to >me for autospeak to
>>default to on. If a user selects a speech driver then he must be expecting
>>it to work. Since speech defaults to being off, this change probably won't
Hi
Dave Mielke schrieb am 18.01.2017, 13:55 -0500:
>[quoted lines by Nicolas Pitre on 2017/01/18 at 13:32 -0500]
>>> Are you saying that you believe the default for autospeak - assuming that it
>>> hasn't been explicitly set yet - should be on?
>>
>>I would say so. Especially if there is already
Sebastian Humenda (2017/01/19 14:35 +0100):
> >One thing I'd find useful here would be to have command-line options to
> >enter help-screen, preferences menu and command-learn mode as soon as
> >brltty is started.
> Yes, or a command from the command line to tell the currently running BRLTTY
>
[quoted lines by Nicolas Pitre on 2017/01/18 at 13:32 -0500]
>> Are you saying that you believe the default for autospeak - assuming that it
>> hasn't been explicitly set yet - should be on?
>
>I would say so. Especially if there is already -Q to negate that
>behavior.
I don't understand, but,
[quoted lines by Nicolas Pitre on 2017/01/18 at 11:53 -0500]
>If speech is enabled then I think it makes sense for autospeak to be
>active by default, especially if there is no braille display.
If the braille device isn't connected then autospeak should already be enabled
by default. This, of
