unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: W32 version crashes on C-g
Date: Sat, 18 Mar 2006 17:42:50 +0200	[thread overview]
Message-ID: <uzmjnvjwl.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0603180445g6eefd3a1ubead963149d8e480@mail.gmail.com> (lekktu@gmail.com)

> Date: Sat, 18 Mar 2006 13:45:50 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: storm@cua.dk, emacs-devel@gnu.org
> 
> On 3/18/06, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > Please feel free to suggest such refinements.
> 
> You only have to take a look at Lennart's EmacsW32 pages to see which
> kinds of things aren't easy for beginners, and are not described in
> nt/INSTALL.

Well, I already read Lennart's pages and incorporated in nt/INSTALL
everything I thought was worthwhile.  So please suggest specific
refinements, if you think there's more to say.

> Or, to put it in another way: Kim can hardly be considered a newbie,
> and it's clear that he could have set up a working environment and
> compiled Emacs, given a little time. But he hadn't the time, he looked
> at nt/INSTALL and did not find what he needed. Whether that's a
> problem in contents or presentation, I don't know.

I didn't suggest to dismiss Kim's gripes.  I'm trying to establish
what should be added to or modified in nt/INSTALL.  I'm not arguing
that it is perfect and should not be changed.

Kim mentioned several additions, like detailed configure and build
instructions and a pointer to Lennart's site, which are already there.
I'm trying to figure out what is NOT there, or what should be reworded
to be more clear.

> > I find it very simple, perhaps because the first thing I do is
> > download GCC, Binutils, and every other ported GNU package (Coreutils,
> > Sed, Grep, Gawk, Make, Texinfo, Diffutils, and Patch) one needs for
> > decent development.
> 
> Perhaps. I've been developing on Windows for years and didn't need
> most of that, until I started hacking Emacs; so your definition of
> "decent development" and mine are dissimilar.

Do we all agree that instructions to set up a suitable development
environment is the _only_ thing that is currently missing?  Or does
something else Need Work (tm)?

  reply	other threads:[~2006-03-18 15:42 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
2006-03-18 11:42               ` Eli Zaretskii
2006-03-18 12:45                 ` Juanma Barranquero
2006-03-18 15:42                   ` Eli Zaretskii [this message]
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=uzmjnvjwl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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).