Re: Question about the the "-q" option used when launchingemacs+emacspeak

["James R. Van Zandt" <jrv@xxxxxxxxxxx>]

Mario -
     
I don't think it would be consistent with Debian policy:

     10.9. Environment variables

     A program must not depend on environment variables to get
     reasonable defaults.  (That's because these environment variables
     would have to be set in a system-wide configuration file like
     `/etc/profile', which is not supported by all shells.)

Besides, speech output already requires a lot of things to set up.
This would introduce yet another failure mode, for which the only
symptom is "no speech".

		- Jim Van Zandt



>Cc: Nath <nath.ml@xxxxxxxxxxx>,  emacspeak@xxxxxxxxxxx, jrv@xxxxxxxxxxx
>From: Mario Lang <mlang@xxxxxxxxxxx>
>Date: Sat, 31 May 2003 14:40:41 +0200
>Sender: Mario Lang <mlang@xxxxxxxxxxx>
>
>Tim Cross <tcross@xxxxxxxxxxx> writes:
>
>[...]
>
>>  >> or can I start emacs+emacspeak without this option ? Is it perhaps
>>  >> dangerous ?
>>  Mario> You can achieve the same thing by loading emacspeak-setup from
>>  Mario> your .emacs, at the very beginning of the file.
>>
>> Yes, that is correct. However, I'm finding that many linux
>> distributions now install local site files with default settings, plus
>> there are many emacs packages available for most distributions now
>> which put configuration and loading scripts in this local site
>> area. For example, debian comes with /etc/emacs/site-lisp.d and
>> /etc/emacs21/site-lisp.d - Mandrake comes with /etc/emacs/site-lisp.d
>> and I think redhat does as well. 
>>
>> The problem here is that this means additional packages installed via
>> the distribution package manager (rpm, apt-get etc) will be loaded
>> before your local .emacs file and therefore before your emacs startup
>> script. What I've done to get around this is created a global
>> emacspeak site loading file. Naturally, this is no good if you share
>> your computer with other users who run emacs and don't want emacspeak,
>
>Hmm, even this could be solved by checking an environment-variable.
>
>(when (string= (getenv "USE_EMACSPEAK") "YES")
>  ...)
>
>Come to think of it, that sounds like a very good thing to do for 
>distributions.  The launcher script could then be rewritten to set this
>variable, and just launch emacs.  The benefit?  Customize would start to
>be useable again, out of the box, without tweaks.
>
>Jim, what do you think of this?
>
>-- 
>CYa,
>  Mario | Debian Developer <URL:http://debian.org/>
>        | Get my public key via finger mlang@xxxxxxxxxxx
>        | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
>

-----------------------------------------------------------------------------
To unsubscribe from the emacspeak list or change your address on the
emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx" with a
subject of "unsubscribe" or "help"