[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Copy/paste issue.
From: |
Peter Dyballa |
Subject: |
Re: Copy/paste issue. |
Date: |
Sat, 31 Mar 2012 18:15:30 +0200 |
Am 31.3.2012 um 17:44 schrieb Silvio Levy:
> At the simplest level, cutting a file in half typically cuts it in the
> middle of a function. Even if the functions are short and it's easy to
> break between functions, the remaining code may depend on the omitted
> code, so the division introduces new errors that have to be debugged.
That's indeed a hard problem to solve. I tend to think of that and organise my
init file(s) in a way that things depending on some variable are close
together. And (do)commented! And I have a block at the beginning which is kind
of proven that it does not introduce errors – maybe a bit special. Another
obstacle, for me, is the support of different GNU Emacs versions and variants
(on Mac OS X one can have a real zoo) handled with if etc. Some are quite
large, but since it's merely kind of customisation I can comment out such
blocks.
Out-sourcing things into files should make bisecting rather easy. You can
switch their use off and on find the "culprit" file.
One learns from bisecting...
--
Greetings
Pete === -Q
==<__/% >>
_____________(_)____@_____________________________