From: Eli Zaretskii <eliz@gnu.org>
To: oslsachem <oslsachem@gmail.com>
Cc: 8562@debbugs.gnu.org
Subject: bug#8562: Emacs 23.1 and later don't work in windows 98
Date: Fri, 28 Oct 2011 12:10:58 +0200 [thread overview]
Message-ID: <83y5w5a0jx.fsf@gnu.org> (raw)
In-Reply-To: <CADv-x1sEtCBnODHZ_+yFn9h-dRrNttmgThwFTExD6NF9_Gcg1w@mail.gmail.com>
> Date: Thu, 27 Oct 2011 00:46:01 +0200
> From: oslsachem <oslsachem@gmail.com>
> Cc: 8562@debbugs.gnu.org
>
> > Please give this a try, both with and without UNICOWS.DLL available,
> > and see if the results are good.
>
> As far as I can tell, the patched Emacs works perfectly when using
> emacs.exe (and runemacs.exe with unicows.dll).
Thanks, I installed the changes in the bzr repository. The next
pretest, due in a day or two, should work on Windows 9X.
> However, when using runemacs.exe without unicows.dll, the program
> doesn't show the error dialog window or the application window and the
> process stays hidden in the background instead of exiting gracefully.
See my other mail about this.
prev parent reply other threads:[~2011-10-28 10:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:55 bug#8562: Emacs 23.1 and later don't work in windows 98 oslsachem
2011-04-27 3:09 ` Eli Zaretskii
2011-05-06 1:38 ` oslsachem
2011-05-06 11:52 ` Eli Zaretskii
2011-05-06 15:28 ` Eli Zaretskii
2011-05-22 21:32 ` oslsachem
2011-05-23 13:43 ` Jason Rumney
2011-05-24 19:31 ` oslsachem
2011-05-23 17:39 ` Eli Zaretskii
2011-05-24 19:32 ` oslsachem
2011-05-24 20:37 ` Eli Zaretskii
2011-05-25 2:01 ` oslsachem
2011-05-25 4:28 ` Eli Zaretskii
2011-05-25 10:53 ` oslsachem
2011-05-25 16:44 ` Eli Zaretskii
2011-05-26 1:50 ` oslsachem
2011-05-27 14:04 ` Eli Zaretskii
2011-05-27 17:22 ` oslsachem
2011-05-27 18:17 ` Eli Zaretskii
2011-05-27 16:13 ` oslsachem
2011-05-27 17:15 ` Eli Zaretskii
2011-05-27 18:33 ` oslsachem
2011-05-27 20:51 ` Eli Zaretskii
2011-05-30 15:12 ` oslsachem
2011-05-30 18:43 ` Eli Zaretskii
2011-05-31 18:16 ` oslsachem
2011-05-31 21:02 ` Eli Zaretskii
2011-05-31 21:04 ` Eli Zaretskii
2011-06-02 23:41 ` oslsachem
2011-06-03 7:10 ` Eli Zaretskii
2011-06-03 8:29 ` Eli Zaretskii
2011-06-03 20:10 ` oslsachem
2011-06-03 20:51 ` oslsachem
2011-06-03 22:52 ` oslsachem
2011-06-04 7:11 ` Eli Zaretskii
2011-06-05 1:58 ` oslsachem
2011-06-05 3:07 ` Eli Zaretskii
2011-06-05 5:48 ` Eli Zaretskii
2011-06-05 22:32 ` oslsachem
2011-06-07 19:25 ` oslsachem
2011-06-07 20:32 ` Eli Zaretskii
2011-06-08 18:11 ` oslsachem
2011-06-08 20:36 ` Eli Zaretskii
2011-06-12 21:47 ` oslsachem
2011-10-01 11:06 ` Eli Zaretskii
2011-10-26 23:05 ` oslsachem
2011-10-01 11:03 ` Eli Zaretskii
2011-10-26 22:46 ` oslsachem
2011-10-27 14:53 ` Eli Zaretskii
[not found] ` <CADv-x1szHOjvVzg8xAYtZNE4iByugKeQz37SY+-dNVucioB70w@mail.gmail.com>
2011-10-28 10:21 ` Eli Zaretskii
2011-10-28 12:11 ` Eli Zaretskii
2011-10-29 22:24 ` oslsachem
2011-11-04 11:42 ` Eli Zaretskii
2011-11-04 20:59 ` oslsachem
2011-11-04 22:01 ` Eli Zaretskii
2011-10-28 10:10 ` Eli Zaretskii [this message]
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=83y5w5a0jx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8562@debbugs.gnu.org \
--cc=oslsachem@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).