let's remove q switch from emacspeak startup script

["T. V. Raman" <tv.raman.tv@xxxxxxxxxxx>]

emacspeak *must* start before loading any packages that need to
be speech-enabled, otherwise you'll get bizarre breakages.
>>>>> "Jarek" == Jarek Czekalski <jarekczek@xxxxxxxxxxx> writes:
    Jarek> I'd like to return to the subject of starting
    Jarek> emacspeak. I already was thinking of improving the way
    Jarek> Emacspeak starts up in "emacspeak intialization"
    Jarek> thread [1], but that time I thought the q switch is
    Jarek> obligatory and that Emacspeak *must* start before the
    Jarek> user init file. Now I doubt this is really a must.
    Jarek> 
    Jarek> Let's do some classification of startup methods:
    Jarek> 
    Jarek> A. From current emacspeak script, which is -q option
    Jarek> and launching emacspeak-setup.el and then user init
    Jarek> file with -l option B. From the top of user init file
    Jarek> C. From the bottom of user init file D. From command
    Jarek> line using only the -l switch
    Jarek> 
    Jarek> I believe many people favor the B method, because they
    Jarek> want to be able to use "customize" Emacs
    Jarek> facility. Raman, you use this method too, right?
    Jarek> 
    Jarek> Methods C and D are equivalent. Now the differences
    Jarek> between methods B and C/D are minimal. It's only about
    Jarek> which should be processed first: emacspeak-setup.el or
    Jarek> user init file.
    Jarek> 
    Jarek> If we modify the emacspeak script and just remove -q
    Jarek> switch as well as the workarounds for launching user
    Jarek> init file with the -l option - what negative effect
    Jarek> could it bring?
    Jarek> 
    Jarek> I can think only of Emacspeak specific commands that
    Jarek> we put inside the user init file. But these may be
    Jarek> easily wrapped inside a hook, for example
    Jarek> eval-after-load "emacspeak-setup".
    Jarek> 
    Jarek> After a good startup procedure is established, the
    Jarek> corresponding installation manual parts may need to be
    Jarek> adjusted. Please, let's do something with the wrong
    Jarek> emacspeak startup script.
    Jarek> 
    Jarek> Before starting this thread I searched the mailing
    Jarek> list, but couldn't find the explanation behind the
    Jarek> strange startup script.
    Jarek> 
    Jarek> One more thing, a note from emacspeak.sh:
    Jarek> 
    Jarek> # emacspeak - execute emacs with speech enhancements #
    Jarek> this file needs a maintainer, I,
    Jarek> (tv.raman.tv@xxxxxxxxxxx) am not presently maintaining
    Jarek> it. # AKA Use at your own risk, and if it breaks, you
    Jarek> get to keep both pieces. # Patches that are fully
    Jarek> tested always welcome.
    Jarek> 
    Jarek> The default script for launching emacspeak, suggested
    Jarek> by manual pages, has a note "use at your own risk",
    Jarek> "no maintainer". That's the proof that something's not
    Jarek> right.
    Jarek> 
    Jarek> Jarek
    Jarek> 
    Jarek> [1]
    Jarek> https://www.emacspeak.org/VCCS-archive/2013/msg00385.html
    Jarek> 
    Jarek> -----------------------------------------------------------------------------
    Jarek> To unsubscribe from the emacspeak list or change your
    Jarek> address on the emacspeak list send mail to
    Jarek> "emacspeak-request@xxxxxxxxxxx" with a subject of
    Jarek> "unsubscribe" or "help".

-- 
Best Regards,
--raman

-----------------------------------------------------------------------------
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".