After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358302 - command line configuration
command line configuration
Status: RESOLVED WONTFIX
Product: lsr
Classification: Deprecated
Component: misc
0.3.x
Other Linux
: High enhancement
: ---
Assigned To: LSR maintainers
LSR maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-09-29 13:40 UTC by George Kraft IV
Modified: 2011-07-06 06:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description George Kraft IV 2006-09-29 13:40:27 UTC 
Currently, LSR v0.3.0 uses a GUI to set its preferences.   The preferences are stored in a berkley db in directory $HOME/.lsr/.  It would be nice if these preferences could also be set via the command line.  For example, "lsr --config IBMSpeech/rate 100".  In addition, it would be nice if lsr could export its settings into a script so that it could be used later as a restore point.
Comment 1 Peter Parente 2007-05-24 15:22:10 UTC 
This topic came up again under the guise of wanting to have different defaults for  different profiles. For instance, a "tester" profile might want full verbosity so that the tester can determine if LSR is seeing all the available information about a widget.

I'm bumping priority on this bug since it's becoming more of a concern.
Comment 2 Akhil Laddha 2011-07-06 06:40:44 UTC 
lsr (Linux Screen reader) development has been stalled and it has been unmaintained for a few years now. Maintainers don't have future development plan so i am closing the bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.