[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]

Re: no byte-compilation in windows release



I'm not disputing the usefulness of Wget. What if a user doesn't want it on their system?

I was suggesting Power Shell be used during installation only.
Haden

On 10/21/2013 6:31 PM, Jude DaShiell wrote:
Another reason I recommended wget for windows is because of wget-el
which gives a user of emacs at least access to wget inside of emacs
without the necessity to close down emacspeak and open up windows power
shell.

On Mon, 21 Oct 2013, Haden Pike wrote:

Personally, I wouldn't install anything which isn't absolutely necessary.  I'm
thinking use Windows Power Shell to download packages.
Haden

On 10/21/2013 6:10 AM, Jude DaShiell wrote:
Windows will need something analogous to the linux script program to be
turned on first by any bat file that compiles emacspeakwin.  Also, an
e-mail with a successful compile and install is valuable as well as an
e-mail with errors.  A reasonable going assumption will be that people
installing this kind of package for the first time will have none of the
prerequisite software so if a bat file can go get it and install it
first everybody probably gets that much closer to successful installs.
One package to get for windows maybe first if it's not on the computer
would probably be wget for windows since that can be used to download
any missing prerequisites later.

On Mon, 21 Oct 2013, Jarek Czekalski wrote:

After listening to voices in "ems-interactive-p, a bug in
call-interactively-p" thread [1], I would like to answer here.

W dniu 2013-10-12 00:05, Jarek Czekalski pisze:
I'll work on a script to do the compilation. Indeed it could be bundled
with
the installer. A one for windows, a batch file.
Currently I don't think it is a good idea. How to handle compilation
errors?
How to handle users reporting errors? Users are not developers and may
have
troubles communicating about compilation errors. I don't like the idea of
forcing a user to compile computer program.

Performance may be sacrificed. If compiled Emacspeak could be run by
computers
20 years ago, it can also be run now without compilation.

If someone else wants to spends his time on a *robust* compilation script,
please contribute it to the project. For me it is too much work and new
problems for too little benefit.

By the way. I am still not sure about the cause of the "cl-proclaim" error
when running compiled emacspeak. If I load "emacspeak.elc", I get an
error. No
error with "emacspeak.el", which surprisingly is called by the official
script. But since compilation is put aside, I don't find it necessary to
dig
that problem.

[1] https://www.emacspeak.org/VCCS-archive/2013/msg00431.html

Jarek

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



---------------------------------------------------------------------------
jude <jdashiel@xxxxxxxxxxx>
Avoid the Gates Of Hell, use Linux!

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


---------------------------------------------------------------------------
jude <jdashiel@xxxxxxxxxxx>
Avoid the Gates Of Hell, use Linux!


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



If you have questions about this archive or had problems using it, please send mail to:

priestdo@xxxxxxxxxxx No Soliciting!

Emacspeak List Archive | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | 1998 | Pre 1998

Emacspeak Files | Emacspeak Blog