From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: config problems and bisecting an org-mode configuration file Date: Mon, 05 Jun 2017 23:04:38 +0200 Message-ID: References: <874lvx8bum.fsf@skimble.plus.com> <87y3t75z7t.fsf@skimble.plus.com> <87d1aiz3n3.fsf@skimble.plus.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1496696725 28709 195.159.176.226 (5 Jun 2017 21:05:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 5 Jun 2017 21:05:25 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jun 05 23:05:20 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dHzBe-00073T-Hl for geh-help-gnu-emacs@m.gmane.org; Mon, 05 Jun 2017 23:05:18 +0200 Original-Received: from localhost ([::1]:35173 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dHzBj-0005fC-NH for geh-help-gnu-emacs@m.gmane.org; Mon, 05 Jun 2017 17:05:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39420) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dHzBE-0005ev-87 for help-gnu-emacs@gnu.org; Mon, 05 Jun 2017 17:04:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dHzB9-0007s0-Bs for help-gnu-emacs@gnu.org; Mon, 05 Jun 2017 17:04:52 -0400 Original-Received: from [195.159.176.226] (port=41385 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dHzB9-0007qF-58 for help-gnu-emacs@gnu.org; Mon, 05 Jun 2017 17:04:47 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dHzB1-00055p-T8 for help-gnu-emacs@gnu.org; Mon, 05 Jun 2017 23:04:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Original-Lines: 38 Original-X-Complaints-To: usenet@blaine.gmane.org Mail-Copies-To: never Cancel-Lock: sha1:mu8XeOIrASYtSre6xoKWOaG8c/g= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:113362 Archived-At: Sharon Kimble wrote: > And that's what I did, with very good support > form Drew giving me very explicit > instructions which helped resolve the problem > by showing me, eventually, where the problem > was. All kudos to Drew! This is his favorite method. I think he even got a name for it - "binary search", right? While there is no denying its advantages, with your situation, it seems you have a lot of configs and probably you should make the code more modular, so changes in one part is easy to pinpoint and have less or no impact on everything else. If you are using a module, say module M, you can create a file for configs for that module alone, say my-M.el, which has (require 'M) as the first line, and then load that file from .emacs. Incidentally, this doesn't prevent binary search, tho - it won't be perfectly binary anymore :) - as you can then just comment out the line(s) in .emacs that loads the module(s). If you byte-compile the code, the compiler will help you determine what code interferes with what other, and you can remedy that by moving around stuff and adding more pairs of `require' and `provide'. -- underground experts united http://user.it.uu.se/~embe8573