From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Silvio Levy <levy@msri.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Copy/paste issue.
Date: Sat, 31 Mar 2012 18:15:30 +0200 [thread overview]
Message-ID: <5947D170-0A85-4525-8074-C9F86485E526@Web.DE> (raw)
In-Reply-To: <20120331154408.40E7F180CAB@neo.msri.org>
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
==<__/% >>
_____________(_)____@_____________________________
next prev parent reply other threads:[~2012-03-31 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 15:44 Copy/paste issue Silvio Levy
2012-03-31 16:03 ` Drew Adams
2012-03-31 16:15 ` Peter Dyballa [this message]
[not found] ` <mailman.205.1333209850.20052.help-gnu-emacs@gnu.org>
2012-05-07 4:46 ` David Combs
2012-05-07 6:09 ` Vladimir Murzin
-- strict thread matches above, loose matches on Subject: below --
2012-03-31 8:46 "Jérôme M. Berger"
2012-03-31 8:51 ` "Jérôme M. Berger"
2012-03-31 9:49 ` Peter Dyballa
2012-03-31 10:24 ` "Jérôme M. Berger"
2012-03-31 10:34 ` Eli Zaretskii
2012-03-31 13:47 ` XeCycle
2012-03-31 15:14 ` Drew Adams
2012-04-01 7:59 ` "Jérôme M. Berger"
[not found] ` <mailman.189.1333201685.20052.help-gnu-emacs@gnu.org>
2012-05-07 4:19 ` David Combs
2012-05-07 6:27 ` Drew Adams
2012-05-07 7:52 ` Yaoyuan
[not found] ` <mailman.730.1336372071.855.help-gnu-emacs@gnu.org>
2012-05-29 1:36 ` David Combs
[not found] ` <mailman.731.1336377127.855.help-gnu-emacs@gnu.org>
2012-05-29 1:40 ` David Combs
2012-05-29 13:53 ` Barry Margolin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5947D170-0A85-4525-8074-C9F86485E526@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=levy@msri.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).