From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Vanderschel Newsgroups: gmane.emacs.help Subject: Re: byte-compile making erroneous *Compile Log* Date: Fri, 29 May 2009 22:50:52 +0000 (UTC) Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1243638873 31490 80.91.229.12 (29 May 2009 23:14:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 May 2009 23:14:33 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat May 30 01:14:30 2009 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.50) id 1MABHR-0005mw-T0 for geh-help-gnu-emacs@m.gmane.org; Sat, 30 May 2009 01:14:30 +0200 Original-Received: from localhost ([127.0.0.1]:33523 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MABHQ-0003tm-Hp for geh-help-gnu-emacs@m.gmane.org; Fri, 29 May 2009 19:14:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MAAv2-0007Ty-C4 for help-gnu-emacs@gnu.org; Fri, 29 May 2009 18:51:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MAAux-0007RE-QS for help-gnu-emacs@gnu.org; Fri, 29 May 2009 18:51:19 -0400 Original-Received: from [199.232.76.173] (port=60723 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MAAux-0007R3-AN for help-gnu-emacs@gnu.org; Fri, 29 May 2009 18:51:15 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:57505 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MAAuw-0000V9-Cg for help-gnu-emacs@gnu.org; Fri, 29 May 2009 18:51:14 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MAAul-0001gI-0j for help-gnu-emacs@gnu.org; Fri, 29 May 2009 22:51:04 +0000 Original-Received: from cpe-66-68-143-33.austin.res.rr.com ([66.68.143.33]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 May 2009 22:51:03 +0000 Original-Received: from DJV5 by cpe-66-68-143-33.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 May 2009 22:51:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 24 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 66.68.143.33 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.10) Gecko/2009042523 Ubuntu/9.04 (jaunty) Firefox/3.0.10 GTB5) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:64822 Archived-At: Drew Adams oracle.com> writes: DV wrote: > > My initialization is a bit too large to try to narrow it down > > by partial execution... > No, it's not too large. What you need to do (unless someone here has > a direct answer for your problem) is to look for the problem using > _binary_ search. Yes, I am familiar with binary search; and, in this case, it will be my last resort. My initialization file is over 3000 lines long, so successive halving still takes a while to get down to something specific. Such binary search works well when the problem is an execution bug, as the 'test' is very quick. However, in this case, testing whether the problem still exists at each stage is not at all trivial. That is why I am hoping that someone can help me come at this problem with better insight - which I believe is possible for this particular problem. > ... (Alternatively, you can use `eval-region'.) Indeed. That is, in fact, how I have normally done it. Too many times. :(