From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pascal J. Bourguignon" Newsgroups: gmane.emacs.help Subject: Re: c/c++ project management and debugging Date: Wed, 22 Dec 2010 14:35:56 +0100 Organization: Informatimago Message-ID: <8739pqudz7.fsf@kuiper.lan.informatimago.com> References: <4D0F4058.6050101@gmail.com> <038dfa58-3e80-4c49-bbd0-c1bbb16c41f1@j25g2000vbs.googlegroups.com> <87bp4ex0a4.fsf@kuiper.lan.informatimago.com> <7e99bd12-91df-4cc2-bfc9-576df4c5283b@i18g2000yqn.googlegroups.com> <87k4j2uohx.fsf@kuiper.lan.informatimago.com> <6d58027e-6ed1-41f6-8653-fbcd42236b68@w2g2000yqb.googlegroups.com> <87fwtqums7.fsf@kuiper.lan.informatimago.com> <86126496-de72-4e5c-9443-5cfce30f28ab@15g2000vbz.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1293025278 10050 80.91.229.12 (22 Dec 2010 13:41:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 22 Dec 2010 13:41:18 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 22 14:41:14 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PVOwI-0006zY-Mw for geh-help-gnu-emacs@m.gmane.org; Wed, 22 Dec 2010 14:41:10 +0100 Original-Received: from localhost ([127.0.0.1]:43107 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PVOwI-0001sq-4o for geh-help-gnu-emacs@m.gmane.org; Wed, 22 Dec 2010 08:41:10 -0500 Original-Path: usenet.stanford.edu!news.glorb.com!news2.glorb.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 33 Original-X-Trace: individual.net gGDLKS3nvctD85KhTPeRtQwJBKW5l9R/oeXcYrQgS8LWRLC7hu Cancel-Lock: sha1:MGE0ZWFkNTI2MjBiZDdjNzgzNDU4YTYwNDZjYTFlYzlkMzA5NzhmNg== sha1:6veehglQkjKRbU7WaGJX6h9FCLQ= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:183546 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:77787 Archived-At: Elena writes: > No need to bring in the bigger guns. It could just be some scheduled > activity by who-knows what package. If Emacs Lisp had both a tracing > and a profiling utility, I would have squashed the bug already. It has. trace-function and elp. >> This is not my experience.  What I observe, is that emacs has an uptime >> only limited by the uptime of the underlying system. > > "emacs -Q" is effective in deciding whether something comes from > Emacs' default behavior or from some package. Once you have decided > it must be some package, that's the hairy part where Emacs debugging > tools aren't up to the task. No, that's the easy part: you have all the sources available, you have an embedded debugger, tracer, profiler, documentation, editor, a while integrated lisp developping environment. > That's why I have said that users have > pushed Emacs beyond its capabilities: IDE, mail-reader... guys, here > we have just a simple text editor which doesn't pretend to by anything > else. No. emacs is a lisp machine, and like any computer, you stack on it an OS, a user interface, a shell, an editor, and all kinds of applications and utilities. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.