unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Matthew L Daniel <mdaniel@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: help-gnu-emacs@gnu.org, Reto <retohu@gmail.com>
Subject: Re: occasional pause (or stutter) on win32 emacs 23.0.95
Date: Thu, 10 Dec 2009 10:06:49 -0500	[thread overview]
Message-ID: <4B210E89.4080403@gmail.com> (raw)
In-Reply-To: <f7ccd24b0912100359u768387b2pcf55bd02b0d10a67@mail.gmail.com>

On 12/10/2009 6:59 AM, Juanma Barranquero wrote:
> On Wed, Dec 9, 2009 at 17:13, Matthew L Daniel<mdaniel@gmail.com>  wrote:
>
>> On the one hand, I'm sorry that blamed Emacs, but on the other hand since
>> the Windows version of Emacs uses MSYS, this is relevant.
>
> For the record, you don't need MSYS to build or run a MinGW build of Emacs.
>
>      Juanma

Yes, I was researching yesterday and it turns out I was wrong. The 
content of http://mingw.org/wiki/MSYS states that MSYS is _not_ the 
subsystem, as I erroneously assumed it was. I thought MinGW
was a collection of compilers which targeted the MSYS runtime. The
content of http://mingw.org/wiki/MinGW claims that its compilers
target the Microsoft runtimes.

Having said that, learning this just makes me _more_ confused. Now I 
wonder if perhaps the mingw-gcc outputs are somehow not using the 
Microsoft runtimes "correctly", leading to some kind of initialization 
delay. [yes, I know this has really digressed into a MinGW discussion, 
and for that I am sorry]

I want very much to use Microsoft's compilers to build Emacs, in order
to find out what's wrong. However, for right now I don't have the
intellectual bandwidth to chase that.

   Sorry for the confusion,
   -- /v\atthew




  reply	other threads:[~2009-12-10 15:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 20:31 occasional pause (or stutter) on win32 emacs 23.0.95 Matthew Daniel
2009-09-08 20:26 ` Matthew Daniel
2009-09-09 19:56   ` Tyler Smith
2009-09-09 20:12     ` Lennart Borgman
     [not found]     ` <mailman.6330.1252527201.2239.help-gnu-emacs@gnu.org>
2009-09-10 14:31       ` Elena
     [not found]   ` <mailman.6329.1252526196.2239.help-gnu-emacs@gnu.org>
2009-09-11 21:57     ` Vincent Goulet
2009-09-14 15:22       ` Matthew L Daniel
2009-11-17 10:09         ` Matthew L Daniel
     [not found]         ` <mailman.10878.1258452584.2239.help-gnu-emacs@gnu.org>
2009-12-08 10:28           ` Reto
2009-12-09 16:13             ` Matthew L Daniel
2009-12-10 10:34               ` Reto Hubmann
2009-12-10 11:59               ` Juanma Barranquero
2009-12-10 15:06                 ` Matthew L Daniel [this message]
2009-12-10 16:20                   ` Reto Hubmann
     [not found]                   ` <mailman.12668.1260462076.2239.help-gnu-emacs@gnu.org>
2009-12-23 11:47                     ` Brel
2009-12-24  0:15                       ` Jason Rumney
2009-12-29 17:27                         ` Reto
2010-01-04 10:11                           ` Brel
     [not found] <mailman.6253.1252454464.2239.help-gnu-emacs@gnu.org>
2009-09-09  6:51 ` Elena
2009-09-09 17:48   ` Matthew L Daniel
     [not found]     ` <mailman.6328.1252520235.2239.help-gnu-emacs@gnu.org>
2009-09-11 15:38       ` Livin Stephen
2009-09-11 15:52         ` Peter Dyballa
2009-09-09  7:27 ` Anselm Helbig

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=4B210E89.4080403@gmail.com \
    --to=mdaniel@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=retohu@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.
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).