Article View: gnu.emacs.bug
Article #100053'M-x compile'
From: James Tuller
Date: Wed, 31 Jan 1990 05:43
Date: Wed, 31 Jan 1990 05:43
20 lines
1234 bytes
1234 bytes
Here is a deadly one: 'M-x compile' reports its usual O.K. message: "Compilation Finished at <date> <time>" except for one small problem: sometimes the compiler doesn't run! Pity the poor hacker: you find a bug and you edit your source code. You compile and run. Same bug. (Of course! You ran the old object!) "No that wasn't it. Let me try something else." "Still don't have it. Well let me scrap this whole procedure and see if it's still there." Pretty soon, there isn't much left of your code.... What is the return code checking on 'M-x compile?'
Technical Details
Message-ID:
<2751@cunixc.cc.columbia.edu>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!snorkelwacker!apple!rutgers!columbia!cunixc!cunixa.cc.columbia.edu!jtShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fb2f1,782a8260444076db,start X-Google-Attributes: gidfb2f1,public X-Google-ArrivalTime: 1990-01-31 09:33:48 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!snorkelwacker!apple!rutgers!columbia!cunixc!cunixa.cc.columbia.edu!jt From: jt@cunixa.cc.columbia.edu (James Tuller) Newsgroups: gnu.emacs.bug Subject: 'M-x compile' Summary: emacs 18.52.22 bug? Message-ID: <2751@cunixc.cc.columbia.edu> Date: 31 Jan 90 05:43:15 GMT Sender: news@cunixc.cc.columbia.edu Reply-To: jt@cunixa.cc.columbia.edu (James Tuller) Organization: Columbia University Lines: 20 Posted: Wed Jan 31 06:43:15 1990