all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: kmartino@pobox.com, Bernt Hansen <bernt@norang.ca>,
	nicholas.dokos@hp.com, emacs-orgmode@gnu.org,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: One org file, multiple exports, is it possible?
Date: Tue, 25 May 2010 12:52:15 -0400	[thread overview]
Message-ID: <9690.1274806335@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Thomas S. Dye" <tsd@tsdye.com> of "Tue, 25 May 2010 06:20:16 -1000." <2A73C8FD-9901-4C69-B02F-967198004270@tsdye.com>

Thomas S. Dye <tsd@tsdye.com> wrote:

> Thanks Bernt,
> 
> So, "broken custom settings" appear to be the cause of the unexpected
> behavior.  Two questions:
> 
> 1) Do programmers have a name for this situation, where custom
> settings seemed to work perfectly for a long time but then failed
> noticeably with the introduction of new, correct code into the .emacs?
> 

I don't think so.

> 2) Is there a useful strategy for finding the minimal .emacs that
> illustrates the failure?  I might have 100 customizations in the
> various starter kit configuration files.  If combinations of
> customizations are a possibility, I'm looking at quite a bit of random
> experimentation without some kind of strategy.
> 

Bisection is about the only reasonable strategy, short of oracular
guesswork. I have a single .emacs that's (mostly) a sequence of
(conditional) loads/requires of individual package config files. I just
comment out the whole thing, verify correct operation, and then
uncomment out the first/second half and try again. With 100 packages, 7
cycles will get you down to a single package and then you just do the
same thing within the package config file. Given a reproducer that you
can run in batch mode, this goes fairly quickly.

HTH,
Nick

  reply	other threads:[~2010-05-25 16:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22 23:46 One org file, multiple exports, is it possible? Karl Martino
2010-05-23  0:47 ` Karl Martino
2010-05-23  4:59 ` Carsten Dominik
2010-05-23 12:22   ` Karl Martino
2010-05-23 15:58     ` Eric Schulte
2010-05-23 16:17     ` Carsten Dominik
2010-05-23 16:31       ` Karl Martino
2010-05-23 18:49         ` Thomas S. Dye
2010-05-23 20:57           ` Carsten Dominik
2010-05-23 22:01             ` Thomas S. Dye
2010-05-24  5:20               ` Carsten Dominik
2010-05-24 16:36                 ` Thomas S. Dye
2010-05-25  3:38                 ` Thomas S. Dye
2010-05-25  3:50                   ` Bernt Hansen
2010-05-25 16:20                     ` Thomas S. Dye
2010-05-25 16:52                       ` Nick Dokos [this message]
2010-05-25 17:51                         ` Thomas S. Dye
2010-05-28  3:40                         ` Thomas S. Dye
2010-05-25 17:26                       ` Mark Elston
2010-05-25 17:53                         ` Thomas S. Dye
2010-05-26 18:42                     ` Thomas S. Dye
2010-05-26 21:37                       ` Nick Dokos
2010-05-26 22:28                         ` Thomas S. Dye
2010-05-27  1:40                           ` Nick Dokos

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9690.1274806335@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=bernt@norang.ca \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kmartino@pobox.com \
    --cc=tsd@tsdye.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.