From: jasonr@btinternet.com
Subject: Re: [peter@runestig.com: Re: emacs-cvs built on Windows XP crashes on Windows 2000]
Date: Thu, 5 Sep 2002 09:24:56 +0100 (BST) [thread overview]
Message-ID: <8119321.1031214296304.JavaMail.root@127.0.0.1> (raw)
I think it is right, but there should be another place
in the code where these variables are currently
being initialized (presumably at dump time).
That initialization should be removed to prevent
future confusion.
> from: Richard Stallman <rms@gnu.org>
> date: Thu, 05 Sep 2002 03:47:35
> to: emacs-devel@gnu.org
> subject: Re: [peter@runestig.com: Re: emacs-cvs built on Windows XP crashes on Windows 2000]
>
> Can someone who uses Windows see if this is right, and install it if so?
>
> ------- Start of forwarded message -------
> Envelope-to: rms@gnu.org
> Delivery-date: Wed, 04 Sep 2002 09:07:14 -0400
> To: bug-gnu-emacs@gnu.org
> Subject: Re: emacs-cvs built on Windows XP crashes on Windows 2000
> From: "Peter 'Luna' Runestig" <peter@runestig.com>
> In-Reply-To: <001301c25405$cc50eb20$64110b0a@datavis.se>
> Sender: bug-gnu-emacs-admin@gnu.org
> Date: 04 Sep 2002 15:05:43 0200
>
> This is a quick hack to make it roll again:
>
> diff -urN emacs-cvs.orig/src/emacs.c emacs-cvs/src/emacs.c
> - --- emacs-cvs.orig/src/emacs.c Wed Aug 28 08:28:30 2002
> emacs-cvs/src/emacs.c Wed Sep 4 14:38:07 2002
> @@ -1536,6 1536,19 @@
> keys_of_window ();
> }
>
> #ifdef HAVE_NTGUI
> {
> /* these must be initialized every run time */
> extern FARPROC track_mouse_event_fn;
> extern FARPROC get_menu_item_info;
> extern FARPROC set_menu_item_info;
> HMODULE user32 = GetModuleHandle ("user32.dll");
> track_mouse_event_fn = GetProcAddress (user32, "TrackMouseEvent");
> get_menu_item_info = GetProcAddress (user32, "GetMenuItemInfoA");
> set_menu_item_info = GetProcAddress (user32, "SetMenuItemInfoA");
> }
> #endif /* HAVE_NTGUI */
>
> if (!noninteractive)
> {
> #ifdef VMS
>
> Cheers,
> - - Peter
> - --
> Peter 'Luna' Runestig (fd. Altberg), Sweden <peter@runestig.com>
> PGP Key ID: 0xD07BBE13
> Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13
> AOL Instant Messenger Screenname: PRunestig
>
>
>
>
> _______________________________________________
> Bug-gnu-emacs mailing list
> Bug-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
> ------- End of forwarded message -------
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2002-09-05 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 8:24 jasonr [this message]
2002-09-06 4:01 ` [peter@runestig.com: Re: emacs-cvs built on Windows XP crashes on Windows 2000] Richard Stallman
2002-09-06 21:51 ` Jason Rumney
2002-09-07 10:29 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 2:47 Richard Stallman
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=8119321.1031214296304.JavaMail.root@127.0.0.1 \
--to=jasonr@btinternet.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).