From: Juanma Barranquero <lekktu@gmail.com>
Subject: FOR-RELEASE.W32
Date: Tue, 9 Aug 2005 11:14:44 +0200 [thread overview]
Message-ID: <f7ccd24b050809021477a979b7@mail.gmail.com> (raw)
As Richard has said that Emacs-on-Windows problems shouldn't delay the
release, Lennart and I have been thinking of adding a file
(tentatively named admin/FOR-RELEASE.W32) listing things that would be
nice to have before releasing a binary tarball for Windows.
Of course, there's no guarantee any of the listed things would be implemented...
Any objection/addition/change to name/intent/contents?
--
/L/e/k/t/u
This file contains task needed before the release on W32.
* TO BE DONE SHORTLY BEFORE RELEASE
* NEW FEATURES
* FATAL ERRORS
** Emacs crashes accessing JPEG images.
Emacs on Windows can crash when reading a JPEG image; the reason is
having two different versions of the file-handling run-time code, one
on the Emacs executable and the other on the image library, which can
happen when mixing a MSVC build of Emacs with a MinGW build of the
image libraries. The fix is straightforward and has already been
posted on the developers' list, but it is on the back burner waiting
for a legal comment by RMS or an alternate implementation (we're
speaking about 30 lines of code or so).
* BUGS
** make-network-process consumes excessive CPU.
TCP/IP server processes created with `make-network-process' consume
excessive CPU on some Windows environments. CPU time uses of 50%
and 100% have been observed on different Window XP configurations.
* DOCUMENTATION
** W32 specifics are not all documented.
\f
Local variables:
mode: outline
End:
next reply other threads:[~2005-08-09 9:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 9:14 Juanma Barranquero [this message]
2005-08-09 9:38 ` FOR-RELEASE.W32 David Kastrup
2005-08-09 9:55 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 10:02 ` FOR-RELEASE.W32 Jason Rumney
2005-08-09 10:19 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 10:55 ` FOR-RELEASE.W32 Jason Rumney
2005-08-09 11:04 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 10:03 ` FOR-RELEASE.W32 Lennart Borgman
2005-08-09 10:24 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 11:10 ` FOR-RELEASE.W32 Lennart Borgman
2005-08-09 11:16 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 11:32 ` FOR-RELEASE.W32 Jason Rumney
2005-08-09 12:12 ` FOR-RELEASE.W32 Lennart Borgman
2005-08-09 14:23 ` FOR-RELEASE.W32 Jason Rumney
2005-08-09 15:31 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 12:44 ` FOR-RELEASE.W32 Juanma Barranquero
2005-08-09 9:44 ` FOR-RELEASE.W32 Nick Roberts
2005-08-09 10:03 ` FOR-RELEASE.W32 Jason Rumney
2005-08-09 10:19 ` FOR-RELEASE.W32 Nick Roberts
2005-08-09 10:09 ` FOR-RELEASE.W32 Lennart Borgman
2005-08-09 10:15 ` FOR-RELEASE.W32 Juanma Barranquero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b050809021477a979b7@mail.gmail.com \
--to=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).