From: "Ludwig, Mark" <ludwig.mark@siemens.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Emacs freezes every now and then on my windows 7 pc
Date: Fri, 3 Aug 2012 17:57:03 +0000 [thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1AA788EA0F@USCIMMBX002.net.plm.eds.com> (raw)
In-Reply-To: <874nokj8yf.fsf@wanadoo.es>
> From: Óscar Fuentes
>
> "Ludwig, Mark" <ludwig.mark@siemens.com> writes:
>
> [snip]
>
> > To the point about some unnamed developer destabilizing the source,
> > our industry overall has a very poor record of educating and training
> > new people. It's generally "baptism by fire" or "jumping in the deep
> > end."
>
> That's not the case currently going on Emacs. There are a few developers
> who are working on very delicate, complex (and I'll say controversial)
> areas. Others are improving platform-dependent code, which often results
> on breakage on some other platform because nobody has the resources for
> testing everywhere before committing the changes. All of them are
> knowledgeable and responsible people.
>
> It's business as usual, really.
Thanks for clarifying. I guess this is where working in industry has its advantages. My primary job is maintaining platform-specific code across Windows and several Unices, a mixture of 32-bit and 64-bit environments (LP64 and LLP64, just to add more fun). I have all supported platforms available at my fingertips, so can test each change simultaneously on all platforms -- and do.
It's rather unfortunate that the platforms are not readily available to the Emacs developers, because frequently it's quite interesting to see which compiler/linker on which platform warns about which subtle problem that's ignored on other platforms ... until run-time.
Cheers,
Mark
next prev parent reply other threads:[~2012-08-03 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 14:14 Emacs freezes every now and then on my windows 7 pc C K Kashyap
2012-06-24 14:22 ` Drew Adams
[not found] ` <mailman.3368.1340547787.855.help-gnu-emacs@gnu.org>
2012-08-02 20:05 ` jane.harvill
2012-08-02 20:14 ` Eli Zaretskii
2012-08-02 21:37 ` Tom Davey
2012-08-02 22:05 ` Jambunathan K
2012-08-02 23:23 ` Drew Adams
2012-08-03 6:36 ` Eli Zaretskii
2012-08-03 14:10 ` Drew Adams
2012-08-03 14:27 ` Eli Zaretskii
2012-08-03 14:39 ` Óscar Fuentes
2012-08-03 14:58 ` Ludwig, Mark
2012-08-03 15:23 ` Óscar Fuentes
2012-08-03 17:57 ` Ludwig, Mark [this message]
[not found] ` <mailman.6249.1344003031.855.help-gnu-emacs@gnu.org>
2012-08-04 2:53 ` Jason Rumney
2012-08-04 5:47 ` Drew Adams
2012-08-03 6:31 ` Eli Zaretskii
[not found] ` <mailman.6201.1343943457.855.help-gnu-emacs@gnu.org>
2012-08-03 10:00 ` Hilary
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=BC5672F8AD4C054BAF167C9801500D1AA788EA0F@USCIMMBX002.net.plm.eds.com \
--to=ludwig.mark@siemens.com \
--cc=help-gnu-emacs@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.
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).