unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: W32 version crashes on C-g
Date: Sat, 18 Mar 2006 07:00:03 +0100	[thread overview]
Message-ID: <f7ccd24b0603172200nc9e4656o3c18873dbcf987bd@mail.gmail.com> (raw)
In-Reply-To: <m3hd5w35ug.fsf@kfs-l.imdomain.dk>

On 3/18/06, Kim F. Storm <storm@cua.dk> wrote:

> I'm very sorry if I did sound ungreatful.

No, don't worry. What I meant is that my message tried to be helpful,
because I thought you already had the whole thing set up.

> I believe you.  I haven't had time to study them myself -- my
> interest is _not_ building Emacs on W32.  But if we expect people
> to be able to do it, the instructions really need improvement
> or at least a pointer to where you can find better instructions
> (even if the link is broken later on, the user will know that such
> instructions exist, and may search for them).

I think nt/INSTALL should be gradually refined. It already has a lot
of good stuff; what it is not, however, is a step-by-step guide. So at
this moment, anyone wanting to build on Emacs has to be brave, and
willing to invest a bit of time and also be able to track things down
by h(im|er)self. I have a little experience building on Emacs, and yet
I find so cumbersome setting up the building environment that I've
resorted to having everything needed on a build/ directory (tools,
.BAT scripts I use, etc.) so I just  zip it and move it to new
machines...

> That pointer should be in nt/INSTALL too.

Truth be told, I don't remember where did I get makeinfo, only that
Eli pointed it to me, and since then I've had it all zipped and moved
'round :(

> It seems other are already doing that -- with varying frequency (and stability).

Yes. I had forgotten about Lennart's page. My fault.

BTW, if you have extra free time ;-) you could take a look at the
"100% CPU on socket select" problem... :-)

--
                    /L/e/k/t/u

  reply	other threads:[~2006-03-18  6:00 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 10:41 W32 version crashes on C-g Kim F. Storm
2006-03-17 11:46 ` Eric Lilja
2006-03-17 12:07 ` Eli Zaretskii
2006-03-17 12:28   ` Kim F. Storm
2006-03-17 12:32 ` Juanma Barranquero
2006-03-17 14:04   ` Kim F. Storm
2006-03-17 14:20     ` Juanma Barranquero
2006-03-17 14:49       ` Kim F. Storm
2006-03-17 16:07         ` Jason Rumney
2006-03-17 16:08         ` Lennart Borgman
2006-03-18  1:13           ` Kim F. Storm
2006-03-18  7:51             ` Lennart Borgman
2006-03-18 11:29             ` Eli Zaretskii
2006-03-17 16:52         ` Juanma Barranquero
2006-03-17 17:06           ` Drew Adams
2006-03-17 18:00           ` Lennart Borgman
2006-03-17 23:27             ` Juanma Barranquero
2006-03-18  0:01               ` Lennart Borgman
2006-03-18  5:49                 ` Juanma Barranquero
2006-03-18  7:48                   ` Lennart Borgman
2006-03-18 12:46                     ` Juanma Barranquero
2006-03-17 18:30           ` Binaries for W32 (was: W32 version crashes on C-g) Reiner Steib
2006-03-17 18:42             ` Drew Adams
2006-03-17 18:56               ` Lennart Borgman
2006-03-17 18:58                 ` Drew Adams
2006-03-20 18:32                   ` Drew Adams
2006-03-21 10:29                     ` Juanma Barranquero
2006-03-22 15:16                       ` Mathias Dahl
2006-03-25 10:15                       ` Eli Zaretskii
2006-03-18  1:21           ` W32 version crashes on C-g Kim F. Storm
2006-03-18  6:00             ` Juanma Barranquero [this message]
2006-03-18 11:42               ` Eli Zaretskii
2006-03-18 12:45                 ` Juanma Barranquero
2006-03-18 15:42                   ` Eli Zaretskii
2006-03-18 16:55                     ` Juanma Barranquero
2006-03-18 17:59                       ` Eli Zaretskii
2006-03-18 20:38                         ` Lennart Borgman
2006-03-18 21:42                           ` Juanma Barranquero
2006-03-18 20:46                   ` Lennart Borgman
2006-03-19  1:32               ` Kim F. Storm
2006-03-21 10:35                 ` Juanma Barranquero
2006-03-21 12:43                   ` Kim F. Storm
2006-03-21 15:22                     ` Juanma Barranquero
2006-03-18 10:52         ` Eli Zaretskii
2006-03-19  1:44           ` Kim F. Storm
2006-03-18 16:23         ` Eli Zaretskii
2006-03-18 17:14           ` Eric Hanchrow
2006-03-18 17:15           ` Chong Yidong
2006-03-18 18:10             ` Eli Zaretskii
2006-03-18 18:59             ` Jason Rumney
2006-03-18 19:11               ` Chong Yidong
2006-03-18 22:38                 ` Eli Zaretskii
2006-03-19  0:46           ` Kim F. Storm
2006-03-18 16:27         ` Eric Hanchrow
2006-03-18 17:56           ` Eli Zaretskii
2006-03-18 16:29         ` Eric Hanchrow
2006-03-18 18:19           ` Eli Zaretskii
2006-03-18 19:04           ` Jason Rumney
2006-03-18 10:40     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2006-03-17 12:58 LENNART BORGMAN

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=f7ccd24b0603172200nc9e4656o3c18873dbcf987bd@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).